{"slug": "all-roads-lead-to-metered-pricing", "title": "All roads lead to metered pricing", "summary": "Cursor, the AI code editor, is moving to metered pricing for its Auto plan, effective August 24, according to an email sent to subscribers. The change means most requests will draw at a higher rate than the current flat rate, following similar moves by GitHub Copilot and Anthropic. Enterprises are advised to consider the cost of switching providers and whether their configurations are portable.", "body_md": "*On sourcing: The August 24 change is known only from an email Cursor sent to subscribers. There’s no blog post and no changelog entry, and Cursor’s pricing docs still list Auto Cost as a flat rate. Everything below about Cursor comes from recipients posting the email to r/cursor and to X. Check Settings → Billing after the 24th.*\n\n**How it started and how it’s going**\n\n**How it started and how it’s going**\n\n**GitHub Copilot**\n\nUnlimited on a base model, then premium requests from June 2025, each model carrying a multiplier so one request could cost fifty times another. Then token billing on June 1, 2026, drawn on input, output and cached tokens at API rates. Annual plans are being retired.\n\n**Anthropic**\n\nDoesn’t reprice, restricts instead. Subscriptions get rate limits instead of higher rates: weekly caps arrived on Claude Code in August 2025. Enterprise gets no such cushion. It’s seat price plus usage at API rates, metered from the first token.\n\n**Cursor**\n\nHas repriced repeatedly, and this week’s email is the latest. Included usage for Cursor Models goes up. Auto stops being a flat rate. Cursor’s own wording is that most requests will draw at a higher rate than they do today.\n\n**Enterprises hit this first**\n\nProcurement runs on annual cycles. Pricing models now change quarterly. Copilot retiring annual plans is that collision made literal: the contract term outlived the pricing model it was signed under. A budget approved in Q1 2026 under premium-request maths was obsolete by June.\n\n**Five questions worth asking now**\n\nNot “are you ready for metered pricing.” Everyone is metered already (to some degree). The question is what it costs to leave.\n\nCan you point the agent at a different model or provider tomorrow, and at what surcharge?\n\nIf you bring your own key, do you still pay the vendor per token? Cursor charges Teams and Enterprise $0.25 per million tokens on third-party models, and that includes BYOK.\n\nIs your agent an extension or an editor? Cursor, Kiro and Windsurf are VS Code forks. Switching one means every developer switches IDE.\n\nDo your rules, skills, MCP configs and prompt libraries live in your repo, or in a vendor’s team marketplace?\n\nWhat happens to your prepaid credit balance if you leave?\n\n**Metered pricing was always coming**\n\nKilo doesn’t escape this. Gateway is pass-through at provider rates, which is API pricing. If Anthropic raises Opus rates tomorrow, Kilo users pay the difference.\n\nWhat Kilo does is charge nothing on top and keep the door open. 500+ models through one gateway at provider rates. Switch models when the economics change, without switching editors.\n\nArriving at metered pricing is fine. Arriving without options is the part worth avoiding.", "url": "https://wpnews.pro/news/all-roads-lead-to-metered-pricing", "canonical_source": "https://blog.kilo.ai/p/all-roads-lead-to-metered-pricing", "published_at": "2026-08-20 15:04:25+00:00", "updated_at": "2026-08-20 15:16:05.419926+00:00", "lang": "en", "topics": ["ai-policy", "ai-products", "ai-tools"], "entities": ["Cursor", "GitHub Copilot", "Anthropic", "Kilo", "Kiro", "Windsurf", "VS Code"], "alternates": {"html": "https://wpnews.pro/news/all-roads-lead-to-metered-pricing", "markdown": "https://wpnews.pro/news/all-roads-lead-to-metered-pricing.md", "text": "https://wpnews.pro/news/all-roads-lead-to-metered-pricing.txt", "jsonld": "https://wpnews.pro/news/all-roads-lead-to-metered-pricing.jsonld"}}