Fetching from the wire…
Public story · 2026-09-11 · high
Raycast says agent tasks cost more than a flat rate can cover, so heavy users now pay per credit instead of a fixed monthly fee.
Why now: Raycast switched its pricing model on September 10, one day after a similar approach showed up on Hacker News.
Raycast switched off flat-rate AI access on September 10. Multi-step agent tasks cost more to run than a flat subscription can subsidize, the company said in announcing the change, so anyone doing heavier agent work now pays for what they use instead of a fixed monthly fee.
The new system runs on credits. 500 for $10, 3,000 for $20, and a new $50 Max tier with 7,500 credits, per Raycast's announcement.
Any paid plan can also connect a personal Claude or ChatGPT subscription, and usage through that connection doesn't touch the credit balance at all.
The timing lines up with a smaller launch one day earlier. Type.com's Show HN post described a pricing model built the same way: every prompt bills against the user's own subscription, and the company takes no margin on tokens.
Both products reached for the same fix. Agentic tasks don't cost a predictable amount. A single request might be one API call or twenty, depending on how many steps the agent decides it needs, and a flat monthly price has no way to account for that spread. Metering by credit, or routing the bill straight to a subscription the user already pays for, moves that variance off the company's books.
For smaller SaaS teams building on Claude or GPT, this is the model that scales without a large token budget: don't eat inference costs, pass them through. Users will start comparing whose subscription they're burning through when they hit an agent button, not just which app has the better feature set.
Each link below shares sources, entities, or timing with this story.
chenxiachan/thoughtdag reached 136 points and 61 comments on Show HN with one rule: on an infinite canvas of question/answer nodes, only wired upstream nodes get sent to the model. Shows token counts per request before you send, lets you branch, merge, prune, and rebuild the g...
Company A did it. Then B. Then the survey data caught up. Something structural is breaking. Three independent moves in early July all point the same direction. OpenAI started token-based credit metering for ChatGPT Workspace agents on July 6. Microsoft made an E5 license a pre...
Version 2026.8.1 shipped September 1 with contributions from 933 developers across more than 16,000 pull requests, roughly half of every PR ever merged into the project, after a seven-week cycle against a usual pace of 106 releases in 230 days. The install flow now auto-detect...
On August 25, Ninjō AI shipped AI sales agents for Instagram and WhatsApp built and managed through MCP from Claude Code, ChatGPT and Codex; coolplugz shipped a Claude Code orchestrator pulling context from Jira, GitHub, Notion and Slack; Diet Claude shipped a usage meter for...
Darius Monsef posted OzBrain on August 21, a shared knowledge layer Claude, ChatGPT, Cursor and coding agents read from and write to via API or SDK, with humans reviewing the same corpus through a web UI. His framing is blunt: "I don't care what the 17th thing on my bug backlo...
An r/SaaS post details a concrete cross-model workflow: ask ChatGPT how a real developer would fix the bug, have it write the plan into bugfix.md, hand that file to Claude to implement, then ask Claude for a deep review. Anecdotal, single source. What's interesting is that the...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.