Find the right tool
1
Search the catalog
Search by the task or provider in Agent tools.
2
Review the endpoint
Check its inputs, price, and availability.
3
Enable access
Enable the endpoints your agent needs. Ordinary provider endpoints start
disabled; some built-in Recipes are system-managed.
API directory
Browse the full catalog by provider.
Parse APIs
Browse Parse services by category.
Control access and pricing
Enable an endpoint or a whole provider. For customer-billed calls, set a percentage markup, a flat markup, or both. Pricing falls back from endpoint settings to provider settings to your workspace default. For example, enable a search tool and add a 25% markup:Read the live catalog
Use a tenant secret key to get the workspace’s current providers, endpoints, enablement, and effective prices:POST /api/credits/catalog/search to find entries including disabled tools. For agent execution, use POST /api/credits/tools/search or MCP discovery.
Show customers their tools
UseGET /api/credits/me/catalog with an end-user token to show that customer’s available tools and final prices. It applies workspace enablement and the user’s access policy while keeping your base cost and margin private.
This is useful when your app lets customers browse available capabilities before spending credits. The API reference covers filtering, pagination, and response fields.
Understand variable prices
Response-priced endpoints
Some tools reserve a maximum before execution, then settle against measured usage and release the unused amount. Your markup applies to the measured base. See response-priced endpoints.Live-quoted endpoints
Some external services show Priced live per call. Their price comes from the service at execution time. Ask the agent to inspect the current quote and set a hardmax_charge_credits ceiling before running them.
For x402 services, MCP estimate_cost supports a no-payment quote with preflight_external_quote: true. If a quote exceeds the execution ceiling, Locus declines the call without charging.
Agents discover the current request format through each endpoint’s schema. See the API reference for direct-call formats.
Give an agent workspace-specific docs
Locus generates Markdown for the tools your workspace has enabled:provider for the enabled catalog index. These authenticated docs include base costs and markup, so keep them in trusted server workflows. Never expose your secret key to an agent runtime or end user.
Add your own service
Custom APIs bring your HTTP services into the same discovery and access controls. Account integrations such as Gmail or Slack OAuth connections remain with your existing integration platform.Connect an agent
Let agents discover and call your enabled tools.
Set customer pricing
Set a default markup and override it where needed.