Every tool call,
metered and ready to bill.

Locus Pro Enterprise embeds one API catalog into your agent platform with call-level usage metering, per-customer attribution, prepaid balances, markup, spend controls, and billing collection — so every tool your users' agents call becomes accountable revenue.

Talk to the team See the billing loop

live billing routehandled by Locus Pro

✓ Customer identified✓ Usage metered✓ Billing record ready

Billing collectionCustomer balancesCall-level analyticsOne API catalog

The billing system between the agent and the API.

01Identify

Attach the customer and workspace to the request.

02Authorize

Check balance and controls before provider execution.

03Meter

Record the successful call with its usage basis.

04Collect

Connect the ledger to your customer billing flow.

usage_event.createdACCEPTED

{
  "customer_id": "acme_workspace",
  "tool": "company_enrichment",
  "provider": "catalog_routed",
  "units": 1,
  "status": "success",
  "trace_id": "lcx_8f39a2"
}

Customer balanceAuthorized before executionFunding state stays attached to usage.

Usage ledgerOne record per tool callFilter by customer, tool, status, or trace.

CollectionFits your billing flowUse your stack or a hosted funding experience.

See what every customer is using—and why.

USAGE OVERVIEWCustomer tool activity

Last 30 days⌄

Successful callsHealthy

AttributionComplete

Ledger statusCurrent

Calls by customerResearchEnrichmentMedia

CustomerTop capabilityFundingUsage state

Acme workspaceCompany intelligenceAvailableRecorded

Northstar AIDocument extractionAvailableRecorded

Meridian LabsDeep researchReviewControlled

Make your agent platform useful for more than basic web search.

Search & research

Primary sources, live web data, and deep research

Company intelligence

Firmographics, people data, and enrichment

Finance & markets

Filings, fundamentals, and market context

Documents

Extraction, conversion, OCR, and structured output

Voice & media

Speech, audio, images, and generated media

Verification

Identity, email, risk, and data quality checks

Ship the capability. Keep the commercial controls.

Talk to the team

01 / IDENTITY

Every request keeps its customer context.

Pass workspace and user metadata once, then trace it through the full tool call.

customer_id workspace_id trace_id

02 / CONTROL

Balances and policies sit before execution.

Authorize usage before provider work begins and reject calls that fall outside the rules.

balance capability_scope status

03 / RECONCILIATION

Failures do not become accounting mysteries.

Use call status and trace detail to understand execution, holds, and released usage.

provider_status usage_state ledger_record

Billing is the product. Don't rebuild it.

Metering, attribution, top-ups, markup, and controls are table stakes for an agent platform — and months of ledger, billing, and policy work to build well. Locus Pro ships them behind one integration.

Pricing math Catalog reference SDK reference Compare plans

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 →

Built around the way your product works.

How the product works, what it costs, and where the catalog lives — in your team's words, not ours.

How Locus Pro billing works Browse the agent tool catalog AI agent tools overview

What does Locus meter?

Locus records each tool call with the customer, workspace, tool, provider, status, and usage detail needed to reconcile it. Your application keeps a call-level ledger instead of trying to reconstruct usage from provider dashboards later.

How is usage attributed to the right customer?

Your server passes the customer or workspace context with the request. Locus carries that identity through authorization, execution, and the resulting usage record so product, finance, and support teams are looking at the same event.

How does billing collection work?

Platforms can connect tool usage to their existing customer billing flow or work with Locus on a hosted funding experience. Customer balances and authorization checks keep collection connected to the usage that created it.

Can we control which tools customers can use?

Yes. Platform teams can scope credentials, choose which capabilities are available, apply customer-level balances and controls, and keep tenant secrets on trusted servers rather than exposing them to an agent runtime.

Can customers see their own usage?

The same attributed ledger can power customer-facing balances, usage history, and tool-call reporting inside your product. Locus also gives your team a consolidated view across customers and providers.

How do we get started?

Talk to the Locus team about your agent architecture, catalog needs, customer identity model, and billing flow. We will map the integration around the way your product already works.

Give users more tools. Turn every call into accountable usage.