Build MCPs
agents find.

Auth and billing for your MCP. Agents sign themselves up and pay for the work.

Set up auth and billing
Set up your MCP
$ npm install @getonlane/mcp-auth$ npx @getonlane/mcp-auth setup https://acme.com/mcp --name="Acme shop"

Or paste the prompt into your coding agent and it does the whole integration.

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
CLI
Agent
Website

Before, a paywall built for humans

After, the agent signs its user in

02[ ]
[ The ideal flow ]

The agent signs its own user up, mid-task.

No provisioning queue, no sales call, no handoff to a browser. The agent asks for the tool it wants, and the answer tells it how to become someone you can bill.

  1. 01

    The agent asks for a tool it cannot use yet

    It arrives with a Lane identity and no account on your server. Today this is where the job stops.

  2. 02

    Your server answers with the way in

    The refusal names the one step that fixes it, so the agent gets something it can act on instead of a link written for a human.

  3. 03

    The agent opens the account itself

    One call, in the same session. Lane vouches for who the user is and for what they are allowed to spend.

  4. 04

    The call it wanted runs

    The user is real in your table now, so the work is priced, metered, and settled against someone you can name.

03[ ]
[ 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 with 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.

04[ ]
[ 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