The catalog

The catalog is the curated set of pay-per-use APIs that agents reach through Locus Pro. Ordinary provider entries start disabled, and you enable only the endpoints an agent may use. System-managed capability routes follow their own availability controls. Personal accounts manage ordinary entries under Tools and pay the listed price. Enterprise workspaces use Agent tools and can set end-user markup over Locus’s base price.

The catalog is account-specific and always live. Personal users should read Tools in the dashboard. Enterprise integrations can use the catalog endpoint for providers, endpoints, base prices, and effective end-user prices. Do not hard-code the directory snapshot.

Browse every API and pricing status

The full directory: 3,811 services, 15,977 endpoints, and current pricing status.

Browse Parse APIs

All 3,290 Parse listings and 15,204 endpoints, grouped into 24 categories and kept in marketplace order.

What the catalog is not

The catalog is a directory of metered callable services, not a general account-integration platform. Many direct services use provider credentials managed by Locus. Live-quoted MPP and x402 services instead use their native payment rails, and service behavior is not guaranteed to be stateless. Account-to-account OAuth integrations (Slack, Gmail, HubSpot, and similar) are out of scope; keep those on your existing integration platform. To expose your own JSON-over-HTTPS service, create a Custom API.

Most endpoints have a stable or request-calculable price. Response-priced endpoints settle after measuring the result. Live-quoted entries get their price from the external service at execution time.

Search and availability

Use POST /api/credits/catalog/search in a management UI. It includes disabled and temporarily unavailable entries so you can configure them. Use POST /api/credits/tools/search or MCP discovery for executable tools; these return only enabled, allowed, and currently available endpoints. enabled is your policy choice. availability is current platform readiness. An unavailable endpoint returns a retryable 503 before dispatch and does not charge.

Enterprise: read the live catalog

GET /api/credits/catalog returns every provider with its endpoints, and because the call is authenticated as you, your effective prices:

curl "$LOCUS_API/api/credits/catalog" \
  -H "Authorization: Bearer $LOCUS_SECRET_KEY"

{
  "success": true,
  "providers": [
    {
      "provider": "coingecko",
      "name": "CoinGecko",
      "endpoints": [
        {
          "slug": "coingecko/simple-price",
          "method": "POST",
          "dynamic": false,
          "enabled": true,
          "markupBps": 3000,
          "flatMarkupUsdc": "0",
          "baseUsdc": "0.06",
          "chargedUsdc": "0.078",
          "marginUsdc": "0.018"
        }
      ]
    }
  ]
}

Body-priced endpoints (for example tavily/search, whose price depends on search depth) report "dynamic": true with null base, charged, and margin values instead.

Field	Meaning
`slug`	The `provider/endpoint` you pass to a call
`method`	Upstream HTTP method
`dynamic`	`true` when price depends on request fields, response usage, or a live quote
`enabled`	Whether your tenant permits this endpoint
`availability`	Current platform readiness: `available`, `temporarily_unavailable`, or `unknown`
`markupBps`, `flatMarkupUsdc`	Your effective markup after override resolution
`baseUsdc`	Base price for trusted management callers (dashboard session or secret key)
`chargedUsdc`, `marginUsdc`	Your price and the margin you keep
`estimatedCost`	Optional human-readable price hint, present when the provider spec supplies one

End-user authentication never receives baseUsdc.

Enterprise: enable, disable, and price by API

Toggle an endpoint or a whole provider and set its markup in one call. An entry with no configuration is disabled, and a burn against a disabled endpoint returns 403 with an “enable it in your dashboard” message. Enable what you want individually or in bulk from the dashboard; an enabled entry with no explicit pricing falls back to your tenant default markup.

curl -X PUT "$LOCUS_API/api/credits/catalog/tavily/search" \
  -H "Authorization: Bearer $LOCUS_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "enabled": true, "markupBps": 2500, "flatMarkupUsdc": "0.001" }'

curl -X PUT "$LOCUS_API/api/credits/catalog/suno" \
  -H "Authorization: Bearer $LOCUS_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "enabled": false }'

Enable or disable several provider rows atomically with PUT /api/credits/catalog/bulk (up to 50 providers per request):

curl -X PUT "$LOCUS_API/api/credits/catalog/bulk" \
  -H "Authorization: Bearer $LOCUS_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "providers": ["tavily", "openai"], "enabled": false }'

The bulk value is the complete enablement answer for every endpoint under each named provider. Each batch resets endpoint-level enablement overrides to inherit the provider value, while preserving endpoint-level markupBps and flatMarkupUsdc overrides. Requests containing more than 50 providers must be split into batches; each batch commits independently. Pricing fields resolve independently: an endpoint’s non-null markupBps or flatMarkupUsdc overrides the provider value, then falls through to the tenant default. Missing values fall through; they do not mean zero. A later endpoint-specific enable or disable can override the inherited provider value again.

Route by capability

The system-managed router provider adds two variable-cost endpoints:

router/web-search searches several eligible engines in parallel, deduplicates URLs, fuses rankings, and preserves per-result provider provenance.
router/web-research can select an exact structured catalog source for the requested outcome, or fall back to multi-provider search.

These are virtual routes over existing catalog entries, so the directory totals do not count them as additional upstream services. You choose the eligible providers, search breadth, result limit, and optional aggregate credit ceiling. You pay the sum of successful underlying calls; preview is free and failed calls use the normal refund path. Read Capability routing for request shapes, previews, receipts, and routing controls.

Enterprise: read the end-user catalog

GET /api/credits/me/catalog is the browser-safe catalog for an authenticated end-user token. It applies both tenant enablement and that user’s provider/endpoint policy, then returns stable IDs, presentation metadata, and only the tenant’s final price.

curl "$LOCUS_API/api/credits/me/catalog?provider=openai&limit=25" \
  -H "Authorization: Bearer $END_USER_TOKEN"

{
  "success": true,
  "version": "2026-08-14",
  "providers": [
    {
      "id": "openai",
      "slug": "openai",
      "displayName": "OpenAI",
      "category": "AI / LLM",
      "description": "OpenAI APIs available through Locus.",
      "enabled": true,
      "logoUrl": "https://platform.paywithlocus.com/endpoint-logos/openai-logo.png?v=1",
      "endpoints": [
        {
          "id": "openai/chat",
          "slug": "openai/chat",
          "displayName": "Chat Completions",
          "description": "Generate text with OpenAI models.",
          "enabled": true,
          "price": { "state": "dynamic" }
        }
      ]
    }
  ],
  "nextCursor": null
}

The price state is one of exact, dynamic, or unavailable. Exact money values are decimal strings. The endpoint never returns base cost, markup, margin, tenant/account identifiers, provider credentials, payout data, or internal pricing fields. Provider and endpoint IDs stay stable when names, logos, or prices change. Pagination uses an opaque cursor; pass it back unchanged. limit defaults to 50 and accepts 1–100. Filter by an exact provider slug or a case-insensitive exact category (category values include the separator, e.g. AI / LLM). The catalog version rides in the response body, and responses carry Cache-Control: private, no-store, so policy changes are visible on the next request.

Response-priced endpoints

Some endpoints authorize a known maximum, then settle against measured response usage. Locus reserves the ceiling, captures the measured charge, and releases the rest. Markup applies to the measured base. See response-priced endpoints.

Live-quoted endpoints

Part of the catalog has no static base price. These entries show "dynamic": true with a null base in the enterprise catalog API and render as “Priced live per call” in the dashboard and generated docs. The upstream’s live price sets the charge at call time. Personal users see the resulting credit debit under Usage; enterprise calls also receive X-Locus-Credits-Charged and the usual baseUsdc/amountUsdc ledger fields, with configured markup applied over the live base. Two safeguards to use:

For x402, call MCP estimate_cost with preflight_external_quote: true when you need a no-payment quote.
Pass an explicit max_charge_credits ceiling when executing a live-priced call. Locus declines a higher quote before dispatch and charges nothing.

Calling a live-quoted endpoint

Each live-quoted provider exposes a single call endpoint that forwards your request to the upstream service. For MPP services (mpp-* slugs), three optional control fields shape the forwarded request; everything else in the body passes through unchanged:

_path: the upstream API path on the service host, e.g. /createTask. Defaults to the service root.
_method: the upstream HTTP verb, GET or POST (default POST).
_query: query-string parameters for GET-shaped endpoints, as a flat object of string/number/boolean values (or arrays of them). Percent-encoded onto the path.

x402 resources (x402-* slugs) run against the exact method and path discovered in their contract; the control fields are rejected there, and the body is forwarded as-is.

# The body (minus the _ controls) is forwarded to <service host>/createTask verbatim.
curl -i -X POST "$LOCUS_API/api/wrapped/credits/mpp-twocaptcha/call" \
  -H "Authorization: Bearer $LOCUS_SECRET_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"_path":"/createTask","task":{"type":"ImageToTextTask","body":"iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mP8z8BQDwAEhQGAhKmMIQAAAABJRU5ErkJggg=="}}' # body: your base64-encoded image (sample: a 1x1 PNG)

A GET-shaped MPP endpoint takes its parameters through _query (use an exact path from the service’s linked docs):

{ "_method": "GET", "_path": "/search", "_query": { "q": "coffee" } }

The response body is the raw upstream response; the credit charge and remaining balance ride in the X-Locus-Credits-* headers. Via MCP, agents discover the control fields on the endpoint’s input schema and call execute.

Enterprise: generated workspace docs

Every tenant gets a live Markdown catalog scoped to what they’ve enabled, with credit and dollar prices, ready to hand to an agent:

# Index of your enabled APIs
curl "$LOCUS_API/api/credits/md" \
  -H "Authorization: Bearer $LOCUS_SECRET_KEY"

# One provider, with parameters and a runnable curl example
curl "$LOCUS_API/api/credits/md?provider=tavily" \
  -H "Authorization: Bearer $LOCUS_SECRET_KEY"

The generated pages are tenant-facing: they authenticate with your secret key and include your base costs and markup, so keep them server-side rather than handing the URL to end-users.

Set your markup

Global default plus per-endpoint overrides.

Connect an agent

Expose the whole catalog as agent tools.

Custom APIs

Add your own JSON-over-HTTPS services.

Getting started

Funding & billing

Catalog

Agents

Developer tools

Testing

Categories

Browse every API and pricing status

Browse Parse APIs

What the catalog is not

Search and availability

Enterprise: read the live catalog

Enterprise: enable, disable, and price by API

Route by capability

Enterprise: read the end-user catalog

Response-priced endpoints

Live-quoted endpoints

Calling a live-quoted endpoint

Enterprise: generated workspace docs

Set your markup

Connect an agent

Custom APIs

​Categories

Browse every API and pricing status

Browse Parse APIs

​What the catalog is not

​Search and availability

​Enterprise: read the live catalog

​Enterprise: enable, disable, and price by API

​Route by capability

​Enterprise: read the end-user catalog

​Response-priced endpoints

​Live-quoted endpoints

​Calling a live-quoted endpoint

​Enterprise: generated workspace docs

Set your markup

Connect an agent

Custom APIs

Categories

What the catalog is not

Search and availability

Enterprise: read the live catalog

Enterprise: enable, disable, and price by API

Route by capability

Enterprise: read the end-user catalog

Response-priced endpoints

Live-quoted endpoints

Calling a live-quoted endpoint

Enterprise: generated workspace docs