agent → meter → price → policy → settle
Agent-native billing for APIs, MCP servers, and data licensors.
Metering, pricing, and policy — on any payment rail.
If you sell software that AI agents consume — an API, an MCP server, a data feed — Corridor meters that usage per-agent, prices it with your rules, enforces your policies, and settles on the rail that fits you: Corridor can run the whole money path, or plug into the Stripe billing you already have.
agt_4hx9k2
calls your API / MCP tool
Corridor
Settled
+$1.00 · agt_4hx9k2
on your payment rail
the problem
Your software has new customers. They aren't human.
AI agents are starting to call APIs, MCP servers, and data sources on their own. The billing stack behind those surfaces still assumes a person with a seat and a credit card.
can't attribute
One key, a thousand agents
A single customer's API key now fans out to fleets of agents. Their usage arrives as one anonymous blob — you can't see which agent did what, or invoice anyone for it.
can't price
Pricing built for seats
Per-seat plans and monthly tiers don't price what agents actually consume: tool calls, queries, rows of licensed data. The unit of usage changed; the price list didn't.
can't govern
No guardrails at machine speed
An agent stuck in a retry loop can burn a month of quota before lunch. Humans notice when spend runs away; agents need limits enforced before the work happens, not on the invoice.
how it works
From agent call to money settled
Agents call your product; your product calls Corridor. One engine handles metering, pricing, and policy — and the rail that pays you plugs in behind it.
- 01identify
Every request carries an agent identity
Not just an API key. Each call is attributed to the specific agent that made it — identity is first-class, so usage, spend, and limits are per-agent from the first event.
agt_4hx9k2 · not api_key_prod_77
- 02meter
The event is recorded against that agent
A tool call, a query, a row of licensed data — captured as a canonical metered event, the same shape on every payment rail.
- 03price
Your rules turn usage into amounts
Per-call, tiered, unit-based — pricing is declarative and versioned, so you can see exactly which rule priced any event.
- 04policy
Guardrails run before the work happens
Spend caps, rate limits, allow-lists — enforced at authorize time, at machine speed. The agent proceeds only if the answer is yes.
- 05settle
Money moves on a pluggable rail
Authorized events are captured and settled on the rail that fits you — Stripe Connect when Corridor runs your money path, or Stripe's Machine Payments Protocol (MPP) when billing stays on your own Stripe account. The engine doesn't change.
two segments
Two ways to run Corridor
Two distinct products, by design — pick the one that matches how you bill today. The engine is the same; the rail underneath differs.
Greenfield
full-stackWe run the whole money path — you get paid, agents get metered.
You're shipping something new for agents and don't want to build a billing stack first. Corridor handles metering, pricing, policy, and the money path end to end.
- Rail
- Stripe Connect
- Commercial model
- take rate
Stripe-native
metering-onlyAlready on Stripe? Add agent-native metering without changing your rail.
Your billing already runs on Stripe and stays there. Corridor adds the per-agent metering, pricing, and policy layer, and reports usage into the rail you keep.
- Rail
- Stripe MPP
- Commercial model
- flat SaaS + per-event
get in early
Join the waitlist
Corridor is onboarding design partners. Tell us where agents touch your product — an API, an MCP server, a data set — and we'll be in touch.
Opens your mail client — or write to leovaloroberto@gmail.com.