How it works
Ordinary provider tools start turned off. Turn on the ones you want, and agents can find and call them. Before every call, Locus checks that the tool is on, available, and allowed for the calling credential. Open Agent tools in your enterprise workspace. Catalog lists every tool, Enabled shows what your agents can call, and Tool Packs groups related providers, such as GTM enrichment or web research, so you can turn them on together. Self-serve accounts use Tools.Find and enable a tool
1
Search the catalog
Search by the task or provider in Agent tools.
2
Review the endpoint
Check its inputs, price, and availability. A tool whose cost depends on
the request shows the range it can charge in credits.
3
Enable access
Enable the endpoints your agent needs. Some built-in Recipes are
system-managed. The More actions menu can turn every tool on or off,
or keep only known vendors on.
- Tool or Recipe? Use a direct tool when a specific provider or operation matters. Use a Recipe for a complete outcome, such as an enriched record or a cited answer.
- Reliability: tools with at least 20 calls in the last 7 days show a success rate and latency in search results.
- Size: the catalog has 17,900+ tools, and Locus has reviewed 75 of its providers. Availability and prices change, so configure integrations from your workspace’s live catalog.
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 calls billed to your customers, add a percentage markup, a flat markup, or both. Calls billed to your workspace pool pay the base price. Each price uses the most specific setting available. See Credits and pricing for worked examples. When an agent needs a tool that is off, it can ask for it, and an owner or admin approves or denies the request. See Tool access requests.Limit keys to a tool set
A tool set is a named list of tools with its own on and off switches. Bind a key or connected app to a set, and it can call only the tools turned on in that set. Every key uses Main unless you bind it to another set. See Tool sets.Use the catalog from code
The API reference covers each of these in full.Read the live catalog
Your server can read the workspace’s current providers, endpoints, enablement, and effective prices with a secret key. Agents find tools through their own tool search or MCP discovery.Show customers their tools
With an end-user token, your app can show one customer the tools available to them and their final prices. Your base cost and margin stay private.Give an agent workspace-specific docs
Locus generates Markdown docs for the tools your workspace has enabled. They include base costs and markup, so use them only in trusted server workflows.Understand variable prices
Most tools have a fixed price per call. Two kinds don’t:Response-priced endpoints
Locus reserves a maximum before the call, charges for the usage the response reports, and releases the rest. Your markup applies to the measured base.Live-quoted endpoints
Some external services show Priced live per call: the service quotes a price when the call runs. Set a hard credit ceiling on the call, and Locus declines it without charging if the quote is higher. See How a call is charged for the full picture.Next steps
Custom APIs bring your own HTTP services into the same discovery and access controls. Account integrations such as Gmail or Slack OAuth connections stay 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.