The Pi coding agent (pi.dev, and its coding-first fork oh-my-pi) is free, open-source software — your entire cost is the LLM provider behind it. On metered keys, heavy Pi use lands in the standard agent band: roughly $150–250/month for agent-most-days work, and the per-task cost is genuinely unpredictable — the same-sized task can cost $9 or $31 depending on how much the agent explores. The fixes, in order of effort: cap exploration per task, route routine turns to a flash-class model and reserve the strong model for hard reasoning, or move the whole thing to a flat monthly plan so the number is fixed regardless of how curious the agent gets.
Agent cost is not a function of task size — it is a function of the path the agent takes. A task where Pi reads three files and edits one is cheap; the same task where it explores the codebase, retries a failing test, and re-reads context costs 3x, on identical pricing. Per-token billing converts the agent's curiosity directly into invoice variance.
That variance is why 'can I invoice clients for this' is the right question. Metered keys make LLM cost a random variable per project; a flat plan makes it a line item.
| Setup | Monthly cost at ~30 hrs/week | Predictability |
|---|---|---|
| Frontier model, direct key (Anthropic/OpenAI) | $200–500+ | None — task variance and rate-limit backoffs included |
| Cheap open-model key (DeepSeek direct) | $15–60 | Better, but one model family for everything |
| Self-routed: strong + flash model, two keys | $50–150 | Good — you maintain the routing config |
| Flat-rate routed plan (Standard Compute) | $19–249 fixed | Exact — the plan price is the cost; budget is the constraint |
Metered figures: the standard agent cost band (~$13/active day) scaled to heavy use; Pi's multi-provider config makes self-routing unusually easy.
Free agent, expensive habit: because Pi is good enough to live in, the failure mode is quietly doubling API spend and then rationing the tool you chose for productivity. Fixed pricing removes the rationing instinct, but a flat plan's budget is real — a 30-hour week on pure frontier models needs a mid tier, not the $19 entry point.
Pi and oh-my-pi both point at Standard Compute with one config entry: base URL https://api.stdcmpt.com/v1, model standardcompute, flat plans $19–249/mo. Smart routing does the strong-vs-flash split per request automatically, Anthropic-family models are in the pool without a separate Anthropic key, and the invoice is the same number every month — which is the actual fix for the $9-vs-$31 problem.
Yes — Pi (pi.dev, by badlogic) and the oh-my-pi fork are open-source; you bring an LLM provider key. All cost discussions about Pi are really about the provider behind it.
Flash-class models (DeepSeek flash, GLM 5.3-flash) handle routine Pi turns well and cost an order of magnitude less than frontier models. The practical setup is flash by default with a strong model for hard reasoning — via Pi's own multi-provider config or a routed endpoint that decides per request.
Direct keys give you one provider's rate-limit regime; when it backs off, your session stalls. Options: request higher limits, add fallback providers in your config, or run through an endpoint that pools and reroutes — flat-rate gateways absorb 429s as routing decisions instead of session deaths.