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,888 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.

How does metered agent tool billing work?

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.

Who collects the money?

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.

How do agents connect to Locus Pro?

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.

How do platform teams get started with Locus Pro?

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.

How is Locus Pro different from Pay With Locus?

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.

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,888 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.

How does metered agent tool billing work?

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.

Who collects the money?

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.

How do agents connect to Locus Pro?

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.

How do platform teams get started with Locus Pro?

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.

How is Locus Pro different from Pay With Locus?

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.

Locus Pro

One agent tool catalog for you or your platform.

Start free in minutes with MCP, API and SDK access, or choose a self-serve Enterprise plan for team members, customer billing and advanced controls. Both use one catalog: 57 reviewed tool providers and 3,888 catalog listings once marketplace and live-quoted tiers are counted.

Start personal Contact us for custom plans Read the quickstart

Enterprise workspaces

Platform billing for products that meter and resell AI capabilities.

Every plan includes API keys, the server SDK and browser OAuth connections. Enterprise adds per-user balances, customer pricing, an embedded widget and payout controls.

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 CLI · Codex · Grok · one command

# Claude Code CLI/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.

Locus Pro · Enterprise use cases

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.

The money flow

Your useruser_842pays your price

117 credits

▶

Your productacme-platformkeeps the margin

metered call

▶

Locustavily/searchburn + ledger row

base $0.09

▶

ProviderTavilywholesale

tavily/search · user_842−117burn

apollo/people/match · user_2c7−480502 burn

apollo/people/match · user_2c7+480refund

Every burn is a ledger row with the full price breakdown, filterable by user, tool, and your own attribution metadata.

Locus Pro Enterprise · How it works

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.

Locus Pro pricing

Start free. Grow at your pace.

Unlimited agent connections and API / SDK access on every plan. Choose your monthly credits and workspace features. Enterprise is self-serve, with no invitation required.

Free

$0 / month

Pay only for the tools you use

Explore tools and connect your own agents, with no monthly commitment.

Personal workspace
Buy credits when you need them
No included monthly allowance

Start free

Plus

$20 / month

$30 in included monthly usage credits

A monthly credit allowance for the tools your agents use regularly.

Same personal workspace features as Free
More credits than your monthly subscription price
A fresh allowance each billing period

Choose Plus

Enterprise

$200 / month

$30 in included monthly usage credits

Run a shared workspace and manage how your customers use and pay for tools.

Team members and shared access
Advanced analytics
Customer pricing and billing
Bring your own keys and custom endpoints
Volume benefits

Choose Enterprise

Enterprise Plus

$1,000 / month

$1,100 in included monthly usage credits

The same Enterprise features, with a larger allowance for higher monthly usage.

All team, analytics and customer billing features
Bring your own keys, custom endpoints and volume benefits
More credits than your monthly subscription price

Choose Enterprise Plus

Included in every plan

Unlimited agent connections
API and SDK access
Tool catalog and workflows
Spend controls

Enterprise Custom

Beyond Enterprise Plus

Larger usage commitments, tailored support and procurement needs. Let’s find the right agreement for your team.

Included credits expire at the end of each billing period and are used before purchased credits. Top-ups are separate. Upgrades are prorated after successful payment; downgrades and cancellation take effect at renewal. Existing subscriptions and signed agreements keep their terms until you explicitly switch. Tool prices are shown before use.

Pay With Locus · For developers

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.

$0/ month

Open Pay With Locus →

Build vs. Locus

Metering is the product. Don't rebuild it.

Usage ledger, funding flows, provider contracts, markup, authorization, refunds, and customer attribution — each row is documented behavior. Platforms that need the embedded version start with enterprise platform billing.

Comparing building agent-tool billing yourself with using Locus
Capability	Build it yourself	Use Locus
Usage ledger	Reconstruct spend by joining provider dashboards and invoices after the fact.	Every call returns its charge with the remaining balance and lands in a call-level ledger. Charge math →
Top-ups & funding	Build balance top-up, auto-recharge, and payout flows on your own billing stack.	Wholesale top-ups, auto-recharge, end-user top-ups, and payouts with hosted checkout available. Funding & billing →
Provider contracts	Open and maintain a separate account, key, and subscription at each provider.	One connection covers the catalog — no per-provider accounts, plans, or keys. The catalog →
Catalog operations	Integrate and version each provider API individually as the set grows.	Offer an opt-in set of services at base prices you mark up per endpoint. API directory →
Markup & margin	Meter usage yourself to compute margin between provider cost and customer price.	Set default and per-endpoint markup; 100% of the configured margin is yours. Pricing math →
Authorization	Enforce budgets, scopes, and approvals in front of every call you proxy.	Balance, credential scope, and policy are checked before execution; uncovered calls return 402. Authentication & scopes →
Refunds & failures	Reconcile failed calls and provider credits vendor by vendor.	Calls rejected before upstream acceptance release held credits automatically, with status to reconcile. Refunds & ledger →
Customer attribution	Tag and join raw usage to the customer or workspace that caused it.	Customer and workspace context travels through authorization, execution, and the usage record. Agent connections →

FAQ

Frequently asked questions

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.

Quickstart Credits & pricing The catalog SDK reference Connect an agent Browse the catalog AI agent tools overview Enterprise platform billing Guide to agentic payments