Building Overclock because my own AI agent's token bill got out of control — launching tomorrow, AMA
Hey everyone — I'm Taylor, solo builder of Overclock.
Quick backstory: I was running AI coding agents (Cline, Claude Code, etc.) for real, sustained work, and watched my token bill spiral in a way that made usage genuinely stressful to predict. Long tool-call loops, retries, a heavy agent day — none of that maps cleanly to "value delivered," but metered billing charges you for it anyway.
So I built the flat-rate alternative I wanted for myself: instead of paying per token, you pay for a fixed number of concurrent "runners" ($15/29/49 per month for 1/2/4) and can run them as hard as you want, all day, for one price. No meter, no surprise bill.
To be upfront: this isn't a frontier-model tier — it's a fast, capable model aimed squarely at agent tool-calling loops, not "give me the smartest possible answer." If that's not your use case, it's probably not the right fit, and I'd rather say that here than oversell it.
We launch on Product Hunt tomorrow (Sept 3) at 12:01 AM PT. Between now and then I'd genuinely love to hear:
If you're running agents in parallel already — is the token-bill pain something you've actually felt, or is flat concurrency pricing solving a problem you don't have?
Anything that'd make you trust (or not trust) a flat-rate reseller vs. going direct to a provider?
Happy to answer anything about how it works under the hood too. Thanks for reading this far.

Replies