Locus Pro

npx add-mcp 'https://api.paywithlocus.com/api/credits/mcp'

Locus Pro

One prepaid balance for 3,811 catalog services exposing 15,977 pay-per-use endpoints.

Every agent runs on paid APIs. Some ship in your product. Others work inside your company on GTM, coding, or research. Either way, each provider they call means an account, a card on file, and a monthly tier priced for a human who buys predictably. Agents don't buy predictably. They spend task by task, and the cost of a task is decided at runtime by which tools get called and how often.

Locus Pro gives you one prepaid balance and one call contract for 3,811 catalog services exposing 15,977 pay-per-use endpoints. That includes 3,284 callable Parse APIs with 15,204 endpoints. Top up by card, route calls through Locus, and see what every task actually costs. Locus manages provider access and per-call settlement behind one balance, so you do not manage separate provider credentials, cards, or provider invoices. Pre-success non-streaming failures release their reservations; accepted streams follow the documented streaming settlement rules.

The meter works two ways. A personal account shows what your agents spend and lets you control their tools. An enterprise workspace can also turn the meter into usage-based billing: each user gets a balance, tops up by card, and sees it in your product through the SDK. You set a markup over base price, and the spread is your revenue. A task enriches three leads, the user's balance drops from $10.00 to $9.97, and you know your cost and your margin on that work.

Businesses don't run power plants to get electricity. They buy metered power. Your team shouldn't hold a dozen vendor contracts to use APIs. Locus Pro is the access layer and the meter: an OpenRouter for any API.

What teams use it for

1. Simple billing: pay for every API your product uses from one prepaid balance. No per-provider accounts, no cards on file, and no separate provider invoices at month end.
2. One procurement, many APIs: clearing a vendor through procurement takes weeks, and ten providers means ten reviews. Locus is one vendor and one contract. Once it clears, the catalog is available to configure.
3. Internal agents: run agents for GTM, coding, support, or research? Point them at Locus and they get the data access they need. Every enabled API works from a compatible MCP client or agent framework through OAuth or a scoped service credential.
4. Prototyping: want to test a workflow that needs paid data? Don't buy a subscription to find out. The prototype pays for the calls it makes and nothing else.
5. Cost telemetry: most teams can't say what a feature or a customer costs them in API spend. Locus meters every call and records who it was for, so the ledger answers that directly.
6. Usage-based billing: charging users for what they use normally means months of billing work. Locus already meters every call at your price, keeps a balance per user, and handles top-ups. It becomes configuration, not a project.

All six use the same metering foundation. Start with a personal agent, or use an enterprise workspace when you need server APIs, end-user billing, and team controls.

Choose your path

Self-serve from \$0. Enable tools, add prepaid credits, and connect an interactive MCP client through browser OAuth. One active OAuth-connected client is included; Plus and Unlimited add active-client capacity. Add tenant API keys, server SDKs, end-user balances, markup, the billing widget, analytics, team roles, and scoped credentials for unattended agents. Connect a personal agent or make an enterprise server call. How credits map to dollars and the exact charge math. 3,334 direct services with 15,499 endpoints, plus 475 live-quoted and 2 system-managed services. Connect Claude, Cursor, Codex, or OpenAI through OAuth or a scoped service credential.

What you get

Personal accounts use the default 1 credit = \$0.001 denomination. Enterprise workspaces can choose a denomination, fund wholesale, or let end users top up. Set one global markup, override per endpoint. The spread over base price accrues to you. One call shape for all 15,977 endpoints. The charge and remaining balance ride back on the response. Search and call permitted endpoints from an OAuth-capable interactive MCP client, or use scoped service authentication from a compatible headless client. Pin favorites as dedicated tools. Balance and top-up button in your product with a few lines of React. Personal accounts see agent usage. Enterprise workspaces add an append-only, attributable ledger down to each end user and tag.

How it works

Personal

Sign up with email or an available external provider. The account starts at exactly \$0; it has no tenant API keys or free credits. Enable the required endpoints under **Tools**, then fund usage under **Credits**. Personal top-ups do not receive enterprise volume bonuses. Add the hosted MCP URL under **Connections** and approve the browser flow. The client stores and refreshes its OAuth tokens.

Platform and enterprise

Join an evaluation or enterprise workspace, then create server credentials under **API Keys**. Keep `lcr_…` secret keys on your trusted server. Enable the APIs you want and set a global or endpoint markup. Base prices remain visible; live-quoted endpoints report their charge at execution. Top up the wholesale pool, configure auto-recharge, allocate credits to end users, or let users buy credits through the widget. Your server or scoped agent calls Locus. The response reports the charge and remaining balance; failed upstream calls release their reservation.

Enterprise fund flows

Enterprise workspaces can fund calls three ways, depending on who collects from the end user. Personal accounts use the simpler Credits checkout described in the quickstart.

1. You buy wholesale and spend it yourself

Top up the pool by card, call APIs from your backend, and Locus pays the provider on each call. This is the whole story for internal tools, batch jobs, and agents whose costs you absorb.

2. You bill your users on your own Stripe

Your users pay through your Stripe account at your price, and you remain responsible for that customer relationship. You fund the wholesale pool and allocate credits to users as their plans require. When a user makes a call, Locus returns the markup portion to your wholesale pool, so its net drawdown is only the base cost. You already collected that cash margin through your own Stripe account, so it never becomes a Locus payable balance. Stripe handles payouts from your Stripe balance to your bank on your normal schedule; there is no separate Locus margin payout to claim.

3. Locus-hosted checkout funds user balances

Users top up their own balance through Locus-hosted checkout, opened from the widget or from a URL your server creates. Locus processes the top-up without exposing card data to your application. Calls burn at your price while Locus pays the base, and the spread accrues as earnings. Configure the payout destination under Funding & billing → Payouts; your responsibilities to end users, including pricing, support, taxes, refunds, and disputes, remain governed by your agreement and the Locus terms.

Two enterprise call modes

The same catalog serves two call modes, and the only wire-level difference is whether the call carries an end-user id.

	Pooled	Per-end-user
Auth	Secret key	Secret key + X-Locus-End-User, or an end-user token
Whose balance burns	Your wholesale pool	The end-user's account
Price charged	Base price (no markup)	Your effective price (base + markup)
Who funds it	You (wholesale top-up + auto-recharge)	The end-user (Stripe) or you (allocate from pool)
Typical use	Internal agents, flat-rate plans	Usage-based products, the widget

Info

The catalog, SDK, MCP tools, and ledger behave identically in both modes. Prototype pooled, then add end-user billing when you're ready to charge. Nothing gets re-integrated.

Next steps

Make your first metered call now. Stripe top-ups, auto-recharge, payouts, refunds. Understand personal usage and enterprise spend.