about
Why agent-native billing, and why now
Corridor exists because the unit of software consumption changed — from a person with a seat to an agent with a task — and the billing layer underneath didn't.
01
Agents started transacting
AI agents now call APIs, MCP servers, and licensed data sources autonomously — software consuming software, at machine speed, on someone's dime.
02
MCP standardized the doorway
The Model Context Protocol gave agents a common way to discover and call tools. The calling side got infrastructure; the provider side — metering, pricing, governing that traffic — did not.
03
Billing still assumes a human
Seats, monthly tiers, one key per customer. None of it can answer: which agent did this, what should it cost, and should it have been allowed?
How it's built
Spec-first: every subsystem — the ledger, agent identity, the authorize-then-capture lifecycle, both rail adapters — is written down as a spec before it is code, and the invariants in those specs run as runtime assertions and property tests. Billing infrastructure earns trust with receipts, so the engineering discipline is the product strategy.
Corridor is built by Leo Roberto and Cooper Stillick — engineers building the billing layer they kept having to rebuild, this time for customers that aren't human.
Onboarding design partners now — providers with real agent traffic get the engine, and shape it.
Join the waitlist