Pricing
- Pricing model
- BYOK tokens only
- Entry price (/seat/mo)
- $0/seat/mo
- Token markup
- No
- The flat subscription is the most honest deal here, but read the limits. - Every subscription harness enforces a rolling usage window in vendor-specific units, not tokens. - Heavy agentic use burns those windows far faster than chat; then you wait or move to metered billing. - Credits are worse for planning: Windsurf, Devin and Amp price in units the vendor defines. - The vendor can re-price the credit-to-token conversion when model prices change, and you find out afterwards. - Copilot's premium-request multipliers have the same shape. - For a defensible quarterly number, use a per-seat subscription or your own provider key. - BYOK looks cheapest but moves the variance onto your API bill rather than removing it. - A harness that re-reads a large file every turn costs multiples of one that caches aggressively. - At team scale, meter BYOK per repo for a fortnight and check for prompt caching before extrapolating.
Price is one group of 3 fields out of 26. Everything else, features, limits, portability, how well any of it works for agents, is on the full coding agents compared: claude code vs codex cli vs cursor vs the rest comparison.