How it works
1
Discover registered tools
Fetch the public JSON catalog. It lists registered
provider/endpoint slugs and catalog metadata; per-agent enablement is enforced when a tool is called.2
Quote the exact request
Send the intended body to the sibling
/quote route. Quoting validates and prices the request without dispatching provider work.3
Call the tool
Use the registered slug, a stable idempotency key for safe same-route retries, and the quoted price when you need a hard price lock.
4
Collect the result
A normal call returns the provider response in
data. A call that needs human approval returns a durable result path to poll after approval.Discover the catalog
GET /api/wrapped returns the registered execution slugs plus display metadata. Add ?provider=<namespace> to request one namespace:
Pricing
Prices are tool- and request-specific. A total can include provider usage plus a fixed Locus fee, percentage pricing, or a Locus-inclusive rate. Locus resolves the total to six USDC decimal places, rounding up, and applies a minimum charge of $0.001; a zero upstream price does not necessarily make a call free. The quote response contains the authoritative total in both the body andX-Locus-Cost-Usd header:
X-Locus-Expected-Cost-Usd with the quoted value. A mismatch returns 409 PRICE_CHANGED before provider dispatch and includes the new price.
Billing and retry safety
Legacy Agent Platform tool calls use a buffered request-response flow:- Locus resolves the charge and deducts the quoted amount from available promo credits or agent allowance before provider dispatch.
X-Locus-Retry-Safe: trueguarantees that no provider request was dispatched. Do not infer retry safety from an HTTP status alone.- If provider execution fails, Locus records the failure and attempts to restore the pre-call deduction. A wallet-to-treasury charge is not queued on that error path.
- After a successful provider response, promo-credit calls remain debited and wallet-backed calls queue the USDC transfer. A later settlement-queue failure does not make the provider operation safe to repeat; Locus returns the stored result for reconciliation.
/api/wrapped/<provider>/<endpoint> routes return buffered results. The Locus Pro SSE capture rules do not apply to them.
Human approval
A call above the agent’s approval threshold returns202 with an approval_url, api_call_id, and result_path. Approval starts the stored execution automatically, but the caller must collect the result from result_path or replay the original request with the same Idempotency-Key.
202; active execution returns 409 with Retry-After: 2; denial returns 403; and a terminal call returns its stored success or error response.
Manage tools in the dashboard
Open Services → Agent tools in the dashboard to search by provider, capability, source, or category. Locus-managed tools default to enabled. Provider- and tool-level toggles restrict execution immediately; a disabled tool returns403.
The same directory includes official listings from Parse, Merit Systems, MPP, and Orthogonal, plus an Add custom tool action. Those listings do not imply that every external service is enabled through the Locus-managed /api/wrapped registry.
Next steps
Use agent tools
Authentication, discovery, quoting, calls, approvals, and retries.
Agent tool catalog
All 49 namespaces with canonical generated references.
MPP (HTTP 402)
Pay inline on Tempo without a Locus wallet.