Locus agent tools are now live on MPP. Try them at Agent tools live on MPP: mpp.sh/services
Sell your AI featuresby the call.
Personal accounts include one browser-OAuth connection at $0; paid plans add connections, and enabled tool usage is billed separately. Enterprise workspaces add prepaid end-user balances, markup, controls, and platform billing across tools from 3352 providers.
Already a Locus Pro customer? Sign in →
Prefer a wallet-first, non-custodial flow? Pay With Locus →
import { LocusCredits } from '@withlocus/credits'; const credits = new LocusCredits(process.env.LOCUS_CREDITS_SECRET_KEY); // lcr_... const res = await credits.callJson( 'tavily/search', { query: 'agent-native billing' }, { user: 'user_123' },); res.data; // raw Tavily JSON — drop-in with the provider SDK shaperes.cost.credits; // "117" ← exact decimal string, charged at YOUR priceres.cost.balance; // "1883" ← exact decimal-string remaining balancePersonal MCP connections use browser OAuth, so tenant secrets never enter a client. Enterprise server calls return exact cost headers and can apply per-user pricing.
You buy at our price. You sell at yours.
Locus charges you a base price for every tool call. You add a markup and charge your user the total. Bill through your own Stripe, or let eligible hosted-checkout margin accrue for payout through Locus. Move the markup below to watch one real call reprice.
| What Locus charges you | $0.0900 |
|---|---|
| Your markup, at | + $0.0270 |
| What your user pays | $0.1170 |
A bar split in two: $0.0900 is the base price Locus bills you and $0.0270 is the margin you keep, at a 30 percent markup.
Sets your default markup, which any endpoint can override. The receipt, the bar and the monthly totals beside it all update as you move it.
You keep $0.0270 every time this call runs. Over a month of them:
| 10,000 calls | $270 |
|---|---|
| 100,000 calls | $2,700 |
| 1,000,000 calls | $27,000 |
Volumes are here for scale, not a forecast. What you keep per call is whatever markup you set, on every endpoint you enable.
- Every call is a ledger row
- Filterable by user, by tool, or by the attribution metadata you stamp on the call.
- Per-endpoint overrides
- The slider sets your default. Any endpoint can carry its own markup, and the price previews before it goes live.
- You keep the whole margin
- Collect the difference through your own billing flow, or let eligible Locus-hosted checkout margin accrue for payout.
3847 listings. One agent tool catalog.
16034 agent tools: 15539 cataloged operations across 3352 reviewed and marketplace providers, plus 495 live-quoted MPP and x402 tools. Ordinary provider tools start off: choose what you want to offer, see the Locus base price or pricing basis, and set your markup before users discover them. The capability router is labeled as system-managed when available.
Browse agent tools →24 featured providers · 16034 agent tools
Choose tools deliberately
Ordinary provider tools stay unavailable until you enable them. Enable a provider at once or choose individual tools; the individual tool setting always wins. The capability router is system-managed when available.
Base prices before you commit
Each tool shows an exact base price or a live pricing basis. Set a default markup, override it per tool, and preview the price your users will pay before it goes live.
One credential, every provider
Your users never open a Tavily account or manage an OpenAI key. One Locus key reaches everything you have enabled, and the customer relationship stays yours.
How enterprise platform billing works.
Credits allocate, burn and settle on their own, so one prepaid balance takes the place of the provider accounts and the invoicing you would otherwise run yourself.
Pick your catalog and prices
Enable agent tools from the curated catalog with each current base price or live pricing basis visible. Set a default markup and per-tool overrides; exact effective prices preview when the base is known.
Your users hold credits
Fund your wholesale pool and allocate credits in your own denomination. Bill on your own Stripe at retail, or let users top up by card through the embedded widget.
Every call meters itself
Agents and apps burn credits at your price; the cost and remaining balance ride back in the response headers. An underfunded call returns 402 before anything happens.
Every burn is traceable
Calls rejected before provider execution or streaming acceptance release their held credits automatically. Each completed burn is a ledger row you can filter by user, tool, or the attribution metadata you set.
Four things platforms build with it.
Pick a use case to see the mechanics: usage-billed research tools, metered inference, priced MCP tools, or the embedded balance widget.
Explore Locus Pro →Every burn is a ledger row with the full price breakdown, filterable by user, tool, and your own attribution metadata.
Built for scale, metered to the call.
16034 callable endpoints: 15539 direct catalog endpoints across 3352 providers, plus 495 live-quoted MPP and x402 endpoints.
Metering now
Never overdrawn
Burns are atomic against the balance. An underfunded call is refused before any money moves.
Release held credits
Non-streaming failures and streams rejected before upstream acceptance release held credits automatically. An accepted stream remains charged if the client later disconnects.
Idempotent by construction
Every burn requires an idempotency key; retries replay the original outcome instead of double-charging your users.
The whole rate card.
Start personally with no required subscription, or choose an operator-provisioned enterprise workspace with contracted economics and controls.
One active OAuth-connected client is included. Add prepaid credits and pay the displayed tool price as you use it—no monthly tool commitment and no volume tiers.
Included
1 active OAuth-connected client
$0 / month
Plus
3 active OAuth-connected clients
$20 / month
Unlimited
Unlimited active OAuth-connected clients
$200 / month
A 12-month production agreement. The monthly platform fee is the greater of the $5,000 minimum or the marginal fee on provider cost; any unused minimum does not carry forward. No per-user or per-key fees.
Implementation pilot
An 8-week paid pilot validates the integration, economics, controls, and launch plan before production credentials are issued. Provider usage and payment-processing costs are separate.
$15,000
one-time
Platform fee
The monthly platform fee is the greater of the $5,000 minimum or the marginal fee on provider cost: 5% of the first $100k, 4% of the next $400k, and 3% above $500k.
5% → 3%
marginal
Hosted endpoint prices
Existing hosted per-call WAPI prices do not change. Their embedded Locus component is disclosed and credited dollar-for-dollar, so it is never charged twice.
$0
change to per-call prices
Your markup
Set a default markup and per-endpoint overrides. Collect the margin in your own billing flow, or let eligible Locus-hosted checkout margin accrue for payout.
100%
of the margin is yours
Pay per use. Nothing else.
There is no subscription and no minimum. Fund a wallet with USDC and authorize each tool's quoted price or usage basis; see how pricing works.
Agents spend at machine frequency
A runaway loop can burn a month of margin before anyone opens a dashboard, so the limit has to hold before the call rather than surface on the invoice. Locus Pro checks the balance and the end user’s policy on every request, against a budget per user, a ceiling on any single charge and a cap on calls per loop, then returns 402 instead of spending past it.
Every burn lands as a ledger row stamped with your own attribution metadata, so you can trace what a run cost back to the user or the job that caused it.
Agents execute freely. The limits hold.
Agent-native tools built on Locus.
Full-stack deployment, via API.
Spin up Railway apps, provision databases, and manage full deployments entirely through API calls. Your agent ships code without touching a dashboard.
- Deploy from any git repo
- Provision databases + services
- Manage environments via API
- Billed per operation to your wallet
Agent-native checkout.
A Stripe-style checkout SDK built for AI. Accept payments in your product and route funds directly into your own Locus wallet, wallet to wallet.
- Drop-in SDK integration
- Funds land in your Locus wallet
- Spending controls apply automatically
- One session for humans and agents
Your AI co-founder.
An AI co-founder that turns an idea into a running internet business over text — brand, storefront, ads, and customer email handled for you, powered by Locus payment infrastructure.
- Idea to live business from a single chat
- Website, ads, and customer email run for you
- Anything customer-facing waits for your approval
- Built and powered by Locus infrastructure
These features are live now.
Build with Locus, Checkout with Locus, and the full agent tool catalog are available in the app.
Frequently asked questions
Locus is billing and payment infrastructure for AI agents. Locus Pro gives personal accounts pay-as-you-go agent tools and gives enterprise platforms prepaid end-user balances, metering, and markup. Pay With Locus provides non-custodial smart wallets on Base with spending controls and audit trails.
With Locus Pro, agents connect through browser OAuth or an authorized enterprise credential and spend prepaid credits on tools from the shared catalog. With Pay With Locus, an agent uses a scoped API key and spends USDC from its smart wallet under policy. Both return the tool response and record the charge for review.
Not for Locus Pro: personal accounts buy prepaid credits through Stripe, and enterprise funding follows the configured billing flow. Pay With Locus uses USDC on Base; its dashboard includes a Coinbase onramp for funding the non-custodial wallet.
A Locus wallet is an ERC-4337 smart contract wallet on Base. It's non-custodial (you control it), supports session keys for agent access, and enforces programmable spending rules. Think of it as a corporate card for your AI agent.
Prices vary by provider, endpoint, and request. Some tools have a fixed per-call price; token, page, and generation-based tools use a published pricing basis or live quote. The catalog and authorization flow show the applicable price, estimate, or charging basis before execution.
Locus checks available funds and configured limits before execution. Locus Pro returns HTTP 402 when a credit balance cannot cover a tool call; enterprise workspaces can also apply end-user policies. Pay With Locus enforces wallet and session budgets plus policy-group limits, and can require approval above a threshold.
No. Pay With Locus can require approval above a threshold while allowing transactions inside your configured budgets to run autonomously. Locus Pro tools draw only from prepaid credits and are rejected before execution when the balance or an enterprise end-user policy does not allow the charge.
Locus Pro uses revocable browser OAuth for interactive MCP clients and endpoint-scoped credentials for unattended enterprise services; tenant secrets stay on trusted servers. Pay With Locus manages private keys in AWS KMS, uses scoped session keys, and checks transactions against policy before execution. Both products keep an activity trail.