Pricing is the last part of an API to become machine-readable. Endpoints got OpenAPI in 2011. Events got AsyncAPI. Workflows got Arazzo. What something costs stayed a marketing page with a three-column table and a “Contact Sales” button.
7,410 providers on the network now publish a structured plans-and-pricing artifact, conforming to the API Commons Plans specification. That makes it one of the most widely-published artifact types in the catalog.
What is actually in one
Take Stripe. Its plans profile defines 9 plans — named ones include Payments — Standard, Radar for Fraud Teams, Billing — Pay Monthly, Billing — Pay As You Go, and Tax — Complete — and the artifact records the shape of the pricing model itself: Stripe is product-priced rather than tiered, with each product carrying its own per-transaction or per-month rate, and interchange-plus available to high-volume merchants.
Below the plan level, each entry is a structured line item:
name: tx_domestic
label: Domestic card transaction
price: 2.9% + $0.30
metric: transaction
type: metered
timeFrame: usage
geo: US
limit: -1
Then tx_international at +1.5%, then currency conversion. Geography-scoped, metric-scoped, with a limit field where -1 means unmetered.
That is a pricing page a program can read.
Why this matters more than it used to
Three consumers need this, and only one of them is a human.
FinOps tooling needs to model spend before the invoice arrives, which means resolving a call volume against a rate card without a person transcribing it.
Procurement needs to compare vendors on equivalent terms. Comparing a per-seat plan to a per-transaction plan to a tiered-with-overage plan is a spreadsheet exercise that structured entries collapse into a query.
Agents need it most and are worst served by prose. An agent that can call an API but cannot determine what the call costs is an agent operating without a budget. type: metered and timeFrame: usage are the difference between a bounded operation and an open one.
What it does not fix
A structured plan is a description, not a guarantee. The artifact records what a provider publishes; it does not verify the rate you will actually be billed, and enterprise pricing — the tier where the real money moves — remains “contact us” in structured form just as it was in prose. Roughly the entire enterprise band of the catalog resolves to a negotiated number that no artifact can carry.
The gain is narrower and still substantial: for the self-serve and usage-based majority, the rate card stopped being a screenshot.
Takeaway
7,410 providers now describe their pricing in a form a program can consume, down to metric, geography and time frame. The API economy spent fifteen years making the call machine-readable and left the price in a marketing table. That is finally closing.
Browse the catalog at apis.io.