[ LANE FOR MCPS ]

Build MCPs
agents find.

 

Confirm runs a read-only analysis: how agents sign in to your MCP today, what identity Lane can attach to every call, and which tools should sit behind it. You leave with the values to point your auth at Lane. Pricing and billing are drafted alongside it, and that half is coming soon. Nothing goes live, you review every draft first.

01[ ]
[ Lane is your identity provider ]

Agents create their own accounts, with no manual provisioning.

You cannot meter, check out, or settle against a user you cannot name. Point your MCP's auth at Lane and every session starts with a tenant in your user table instead of a paywall.

Lane
auth
MCP server
every tool call attributed to a tenant
CLI
same account, same memory, no second login
Agent
arrives known, so nothing is re-asked
Website
one identity all the way to checkout

One identity, every surface the agent arrives from

Before, a paywall built for humans

After, the agent signs its user in

Auth is the unlock. Once the tenant exists, pricing and billing are policy on top of a user you already know, and adoption starts in-session instead of in a meeting

02[ ]
[ Three jobs Lane runs, in order ]

Auth, pricing, and billing.

Your MCP already has traffic it cannot name. Identity makes the user real, pricing makes the work quotable, and billing collects against both.

Live sign-in events
Agent signed in with Lane
now

a tenant you own, from the very first call

01 Auth for agents

A tenant, a card on file, and a customer

Point your MCP's auth at Lane. The agent signs its user up mid-session and a tenant lands in your table, with no manual provisioning.

Draft pricing13 tools, 4 priced
web.search$0.05 / call
flows.extract$18–$60, estimate
report.generate% of outcome
audit.runquote

drafts only, publish when ready

02 Pricing for agents

Charge like Uber, not prepaid credits

Lane drafts a price per tool from what that tool does. Flat, metered, estimate, or by outcome, so nobody tops up a wallet mid-job to keep going.

The hold
AUTHORIZEthe brief opens a hold$50.00
EXTENDscope grew to 20 sites$180.00
SETTLEnever more than the hold$173.40

never more than the hold, never a top-up

03 Billing for agents

Holds that grow with the job

Authorize $50, the scope grows, the hold extends to $180, and $173.40 settles. Never more than the hold.

03[ ]
[ Value-based pricing ]

Credits are the arcade model. Charge for the work instead.

With a tenant and a price in place, the agent can pay the way the job actually runs.

One run, 12 tool calls
Prepaid credits
$12.00 spent5 calls never served

The balance empties mid-run, so the agent gives up and tries another tool

Authorization hold
$7.40 captured$4.60 releasedof a $12.00 hold

Authorized once at the ceiling, then settled at the value delivered

Same run. Credits spend the whole balance and stop at call 7, the hold finishes all 12 and charges $7.40

When free credits run out, agents do not surface a payment link, they try the next tool. It changes what a trial is: a trial on Lane is an authorization nobody captured yet, so converting a user is capturing it rather than asking them to start paying.

04[ ]
[ Delayed authorization ]Coming soon

Charge like Uber, not like an arcade.

Reserve first, settle at actual value, and when the job grows mid-flight, the hold grows with it.

The hold

AUTHORIZE

$0

The hold opens

SEO redesign, one site, the gas-station move: reserve first, settle later.

WORK

0/20 sites

Scope grows

The brief turns out to be 20 websites, not one. Nobody stops to buy credits.

EXTEND

$50$0

The hold grows with it

You added stops, the authorization extends mid-ride. The work never pauses.

SETTLE

$0.00

Actual value captures

Never more than the hold. The receipt shows the meter, stage by stage.

Imagine buying ride credits to add a stop to an Uber. You don't, the hold extends and the ride keeps moving. Credits are an arcade; holds are how card networks already price work that grows. Price the work, not the credits, when a prosumer wants to keep paying for your intelligence, your top-up UX shouldn't be the ceiling.

05[ ]

Know the agents using your MCP
and the users behind them.

Point your MCP's auth at Lane and every call arrives carrying a signed identity, agent class and risk band. You set the bar for who gets in.

Get started nowRead-only scan, drafts only, nothing goes live until you publish it