Pricing details
The methodology behind the headline pricing: how typed thinks about per-tier volume, why the dashboard shows a single percent rather than per-axis numbers, and how the auto-top-up policy fits together. If you want to verify the math behind the prices, this is where it lives.
1. Headline pricing
Solo tiers
| Tier | Monthly | Annual | Positioning |
|---|---|---|---|
| Starter | $10 | $100 | Lighter than a typical Pro plan; on-ramp tier for evaluation |
| Pro | $20 | $200 | Same quality as frontier models |
| Max | $100 | $1,000 | Same quality as frontier models |
Annual is a 2-month discount on all three tiers. The positioning column describes the per-tier value prop; the underlying methodology and the reference-plan equivalence are documented in section 2 below.
"Same quality as frontier models, monthly billing, no rolling 5-hour windows."
Per-seat pricing (Team / Team Max)
Team is $25/seat/mo and Team Max is $100/seat/mo. Each is a per-seat subscription for shared work inside an org. Each seat carries the per-tier volume envelope of the matching solo tier: Team is Pro-equivalent per seat, Team Max is Max-equivalent per seat.
| Tier | Per-seat monthly | Volume envelope per seat | Billing period |
|---|---|---|---|
| Team | $25 / seat | Same as Pro | Monthly only |
| Team Max | $100 / seat | Same as Max | Monthly only |
How the seat math works. Our payment processor's volume pricing scheme bills the whole subscription at per_seat_unit_price * seat_count. Concretely:
- 3 seats on Team -> billed at $25 x 3 = $75 / month. The org-wide aggregate volume envelope is three times the per-seat envelope, shared across the seats in the org: one heavy member can spend more than 1/3 of the pool without anyone's individual usage being capped.
- 4 seats on Team Max -> billed at $100 x 4 = $400 / month. Aggregate envelope is four times the per-seat envelope, again shared org-wide.
Adding a seat mid-period prorates against the remaining days; removing a seat takes effect at the next renewal. The full per-seat price applies for the full period the seat is active. Top-up shapes ($5 / $10 / $20 / $50) are the same on Team / Team Max as on the solo tiers.
Hosted codebase indexing surface. Team and Team Max include hosted codebase indexing as an additional surface. You upload a source archive via the dashboard or POST /v1/codebases/{id}/files, we chunk and embed it, and queries from any seat in the org can retrieve relevant chunks at request time via the x-typed-codebase: <id> header. Storage and processing are kept inside our us-west-2 AWS region: source archives sit in S3 (SSE-S3 at rest), and chunk embeddings sit in our pgvector index on AWS RDS in the same region. Access is org-scoped: a codebase belonging to org A is invisible to a user in org B even with the codebase's UUID. On cancellation, codebases retain a 30-day grace that allows resubscription without re-upload; after the grace expires they hard-delete within 14 days. You can purge any codebase immediately at any time by emailing privacy@typed.cloud from the address on your account. Full terminology and cross-border-flow disclosure live in the privacy policy ยง3.3a.
Local context works everywhere: every Anthropic-API-compatible client reads files on your machine, on any tier. Hosted indexing is the additional convenience for orgs that want a shared, server-side index across seats; it is not a missing feature on solo tiers.
Why no Team annual?
Per-seat annual is deliberately deferred for V1. Per-seat annual on team SKUs adds proration and mid-year-seat-add complexity without obvious customer pull. We will revisit if Team customers ask. Solo Starter / Pro / Max annual still ship at the prices in the table above.
2. Equivalence to reference plans
The reference Pro / Max plans do not officially publish per-tier token quotas: the quotas are advertised in usage-window terms (5-hour rolling windows, weekly caps, etc.) rather than monthly token totals. So the equivalence below is estimated.
Methodology: we measure how many tokens a typical Pro / Max session typically consumes over the published usage windows, multiply out to a monthly figure, and pick typed envelopes that match within an order-of-magnitude grain. The intent is that a customer who maxed out a typical Pro plan under typical coding load will not max out typed Pro under the same load.
Shape caveat. typed's envelope is heavily skewed toward input tokens because realized coding-workflow traffic runs at that ratio once prompt caching and tool-loop context are factored in. The tradeoff: typed envelopes favor read-heavy workflows (refactoring, debugging, multi-file investigation) over output-heavy ones (large test-suite generation, multi-file scaffolding from scratch, heavy boilerplate emission). If your existing usage is dominated by output volume, your typed envelope may feel tighter than the headline equivalence suggests; bench against your shape before committing.
The estimate is approximate, not certified. If you find that typed Pro feels tighter than a typical Pro plan on your specific workflow, email support@typed.cloud with a description of the workflow. We collect this data to refine the envelopes over time.
Cache eligibility stretches the numbers further. Prompt caching cuts the effective cost of repeated input to a small fraction of the normal rate, and repeated input is most of any AI coding CLI's traffic (system prompt + tool definitions + recently-referenced files get re-sent on every turn). The monthly ceiling is what the gate compares against, so on cache-friendly workflows the effective working capacity is substantially higher than the headline suggests.
3. Auto-top-up at quota: optional, opt-in
Unlike subscription CLIs' 5-hour rolling windows and weekly caps, typed bills monthly. By default, requests past the envelope return HTTP 429 with a one-click top-up prompt: pick a $5/$10/$20/$50 denomination and continue. Enable auto-top-up in your dashboard and the next request past the envelope auto-charges your chosen denomination, emails you a receipt, and the session continues without prompting.
| Volume | Behavior |
|---|---|
| 0% - 80% | Normal. No banner, no friction. |
| 80% - 100% | In-app banner; email warning. |
| 100% and beyond, auto-top-up off (default) | HTTP 429 with a one-click top-up prompt: pick a denomination and continue. |
| 100% and beyond, auto-top-up on | Next request auto-charges your configured denomination; session continues; receipt emailed. |
Dashboard settings: toggle on/off, denomination, and an optional monthly ceiling that caps how much auto-top-up can charge in a calendar month.
4. Cache discount
Prompt caching is enabled on every paid tier and applied automatically. You do not need to set a flag or use a non-standard API shape. If your client sends repeated prefixes (most coding clients do, because they re-send the system prompt and recent context on every turn), the repeated prefix portion is charged at a small fraction of the normal input rate.
The discount is applied when your usage is metered, so cache-heavy work draws proportionally less of your monthly ceiling. We do not break out a separate "cached input" line in your usage view; you see the single percent-of-ceiling figure, and the effect of caching is that the same workload consumes less of it.
5. Billing structure: monthly vs subscription CLIs' 5-hour windows
Subscription AI CLIs bill against rolling 5-hour usage windows and weekly caps. typed bills monthly with auto-top-up at the envelope (see section 3 above).
Pick the shape that fits your work pattern:
- Steady daily usage: typed's monthly billing is friendlier: you do not lose unused capacity at the end of every 5-hour window.
- Bursty work (long sessions twice a week, idle the rest of the time): subscription CLIs' rolling windows may suit you: the window resets after each idle stretch.
Most coding work is closer to "steady daily" than "bursty," which is why typed defaults to monthly. If your work pattern fits the subscription CLIs' windows better, keep using your existing CLI for that workload. The two services interoperate via the same API shape.
6. Currency, taxes, and renewals
- All prices are in USD.
- VAT / GST / sales tax is added at checkout where applicable, based on your billing address. Our payment processor (Lemonsqueezy) acts as Merchant of Record and remits tax for you.
- Subscriptions renew automatically on the same day each month (monthly plans) or each year (annual plans).
- Cancellation takes effect at the next renewal. The remainder of your paid period is served normally. See the migrate guide section 5 and terms of service for the full sales-final policy.
7. Open questions
If anything on this page is ambiguous, or if you want the methodology behind a specific decision explained in more detail, email support@typed.cloud. We will answer and, if the question is shared by other customers, update this page so the answer is public.
Last updated 2026-07-XX.