Locus Pro
One agent tool catalog for you or your platform.
Start a personal account in minutes with MCP and pay-as-you-go agent tools, or work with Locus on a separately provisioned enterprise workspace for teams, metering, controls, and contracted pricing. Both use one catalog: 57 reviewed tool providers and 3,906 catalog listings once marketplace and live-quoted tiers are counted.
Enterprise workspaces
Platform billing for products that meter and resell AI capabilities.
The server SDK, tenant keys, per-user balances, markup, embedded widget, and payout controls are enterprise features. Personal accounts use Tools, Credits, and browser-OAuth Connections in the Locus Pro dashboard.
You resell AI capability
Your product wraps models, search, scraping, or enrichment. You need to charge for it per use without building a ledger, a metering pipeline, and a top-up flow first.
You bill per end user
Usage has to be attributed to the customer who caused it, not pooled across the workspace, so each user carries their own balance and their own limits.
You need spend under control
Agents call at machine frequency. Balances are checked before the call, not reconciled after it, so a runaway loop returns 402 rather than an invoice.
# Claude Code/plugin marketplace add locus-technologies/locus-pro-plugin/plugin install locus@locus # Codex: codex plugin marketplace add locus-technologies/locus-pro-plugin# codex plugin add locus@locus# Grok: grok plugin install locus-technologies/locus-pro-plugin --trust# Installs the Locus skills and MCP server together; OAuth in the browser.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.
Every burn is a ledger row with the full price breakdown, filterable by user, tool, and your own attribution metadata.
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.
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.
Frequently asked questions
Locus Pro gives AI agents one connection and one balance for a broad catalog of paid APIs and proprietary data sources: 57 reviewed providers and 3,906 catalog services in total once marketplace and live-quoted tiers are included. Agents can discover capabilities by outcome and use them without separate provider accounts, subscriptions, or API keys. Enterprise workspaces add per-user balances, markup, managed credentials, widgets, organizational controls, and contracted economics.
Every tool call burns prepaid credits at its effective price. Personal accounts pay the displayed tool price; enterprise workspaces can add markup for their end users. The quoted charge and remaining balance return with the response, and an underfunded call returns HTTP 402 before provider execution. Non-streaming failures and streams rejected before upstream acceptance release held credits automatically; an accepted stream remains charged if the client later disconnects. Each burn is recorded for usage review.
Enterprise platforms can buy credits wholesale for internal agents or absorbed costs, bill users through their own Stripe account while Locus draws down the base cost, or use Locus-hosted Stripe Checkout for end-user top-ups. With hosted checkout, eligible margin accrues for payout to the configured bank account or USDC address. Locus is not a party to the platform’s agreement with its end users.
Personal accounts add the hosted MCP URL to a supported client and approve access through browser OAuth. That one connection lets the agent search the catalog and use supported providers without configuring their API keys individually. Enterprise teams can use the same interactive OAuth flow, an lcac_ service credential scoped to a bundle of catalog tools for an unattended runtime, or a tenant secret on a trusted server. Tenant secrets never belong in an agent or MCP client.
Platform deployments are configured around the product’s catalog needs, end-user funding flow, usage attribution, controls, and reporting requirements. Talk to the Locus team to map the integration and rollout.
Locus Pro is the prepaid-credit product: personal accounts connect MCP clients with OAuth, while enterprise workspaces add per-user metering and platform billing. Pay With Locus is the on-chain product: a non-custodial USDC wallet on Base that an agent funds and spends under policy. They share an agent-tool catalog but use different account and payment models.
Read the details before you commit
The charge math, the credential model, and the full catalog with current prices or live pricing status are all documented.