The meter tracks the buyer: usage for developers, commitments for enterprise
Pricing structure tracks who's buying, not the compute underneath. Of the 30 pure-usage vendors in the corpus, 27 (90%) sell to developers; of the 27 vendors with annual commitments, all 27 (100%) target enterprise. The same vendor often runs both meters at once — chosen by who signs.
What's happening — and why
What's happening: across the corpus, the billable structure lines up with the buyer's procurement habits. Developers get clean pay-as-you-go meters; enterprises get annual commitments with overage. It's so consistent that the structure on offer signals the segment a vendor expects you to be.
Why: developers want to start instantly and pay for what they use; enterprise procurement wants a committed contract with a negotiated discount and a predictable floor. So vendors fit the meter to the buyer — Together's on-demand H100 for developers ($5.49/hr) versus its reserved 7–30-day commit ($4.99/hr) for enterprise is the archetype: identical compute, two meters, picked by who's signing.
How it works
Evidence over time
8 supporting · 3 counter — hover or tap a point for detail, click to jump to the row.
Evidence
| Company | Date | What happened |
|---|---|---|
| DeepSeek | Mar 2025 | Pure per-token API sold to developers — no commitment, no seat; the canonical developer-buyer / pure-usage pairing. |
| Modal | Sep 2025 | Per-second compute, self-serve to developers; commitments and Marketplace billing appear only at the Enterprise tier. |
| Fireworks AI | Mar 2025 | Pure-usage per-token developer API; enterprise adds dedicated deployments and committed-use rates. |
| Together AI | Sep 2024 | On-demand H100 self-serve for developers ($5.49/hr) vs reserved 7–30 day commit ($4.99/hr) for enterprise — usage for devs, commit for enterprise on the same product. |
| Anyscale | Nov 2025 | Pure-usage ACU credits for self-serve developers; annual commits + BYOC + Marketplace billing for enterprise. |
| Glean | May 2026 | Enterprise-only buyer: seats + pooled FlexCredits sold on annual commitment — no developer self-serve PAYG surface. |
| Harvey | May 2026 | Enterprise legal buyer: per-seat annual contracts, sales-led — the opposite end of the spectrum from a developer PAYG meter. |
| Vercel | Sep 2025 | Self-serve usage metering for developers on Pro; Enterprise layers annual commitments on the same metered units. |
Counterexamples
- Cursor (Anysphere) · Feb 2026 — Sells usage-style credit pools to individual developers AND prosumers via flat seat tiers — usage logic applied to a non-developer, seat-anchored buyer.
- Intercom · Mar 2024 — Enterprise-ish buyer, yet prices on per-resolution outcome rather than an annual commitment — outcome unit breaks the commit-for-enterprise rule.
- Anthropic · May 2026 — Pure-usage API but explicitly has_commits:false — a frontier vendor large enough to skip the enterprise-commit convention while still selling to enterprise.
For buyers
The structure you're offered signals the segment a vendor has slotted you into. As a developer on a pure-usage rate, don't expect a committed discount until you cross into enterprise sales. As an enterprise, expect an annual commit with overage rather than a clean PAYG meter — and when a vendor offers both, the commit trades a lower unit rate for a volume floor, so model the breakeven before signing.
For vendors
Offer the meter your target buyer's procurement expects: self-serve PAYG to win developers, an annual commit with overage (and often marketplace billing) to win enterprise. Running both on one product lets you land developers and expand into procurement — but keep the unit consistent across them so the upgrade path stays legible.
Outlook — what to watch
Expect the split to harden as agentic products add usage meters for developers and enterprise tiers add commits on top. The exceptions point to where it bends: a frontier vendor large enough to skip commits (Anthropic, has_commits:false), a prosumer product applying usage logic to seats (Cursor), or an outcome unit that replaces the commit entirely (Intercom).
Bottom line
The meter tracks the buyer: 90% of pure-usage vendors sell to developers, 100% of vendors with commitments target enterprise. Structure fits procurement, not compute — so the price shape on offer tells you which buyer a vendor thinks you are.
FAQ
Does AI pricing structure depend on who the buyer is?
Strongly. In the corpus, 90% of pure-usage vendors sell to developers and 100% of vendors with annual commitments target enterprise — the billable structure fits the buyer's procurement habits more than the underlying compute.
Why do developers get usage pricing and enterprises get commitments?
Developers want to start instantly and pay for what they use; enterprise procurement wants a committed contract with a negotiated discount and a predictable spend floor. Vendors fit the meter to each.
Can one vendor offer both usage and commitment pricing?
Yes — it's common. Together AI sells on-demand H100s to developers and reserved committed rates to enterprise on the same product; Modal, Anyscale, Fireworks and Vercel do similar. The commit usually trades a lower unit rate for a volume floor.
What are the exceptions to the meter-tracks-buyer rule?
It's a correlation, not a law: Anthropic sells to enterprise on a pure-usage API with no commitments, Cursor applies usage-style credit pools to seat-anchored prosumers, and Intercom prices an enterprise-ish product per outcome instead of on a commit.