Skip to main content
Add your own service to Locus so agents can discover and call it alongside the hosted catalog. Custom APIs use the same access controls, activity history, and customer billing as other tools. For example, expose an inventory lookup as custom-inventory/check-stock so a connected agent can check availability before recommending an item. Custom APIs must be enabled for your enterprise workspace. They use your provider account and credential, so that provider’s usage and data-handling terms still apply.
Creating or changing providers and actions requires a workspace owner with recent MFA or passkey verification and the catalog:write and credentials:manage scopes.

​
Add a provider

Open Agent tools → Custom APIs and enter:
  • A name, stable slug, description, and public HTTPS base URL.
  • The authentication method: bearer token, custom header, query parameter, or none.
  • Any rate, concurrency, or timeout limits your service needs.
Saved credentials stay private. The base URL must not contain credentials, query parameters, or a fragment.

​
Add actions

Create an action manually or import an OpenAPI 3.0 or 3.1 JSON or YAML document. Supported actions use GET, POST, PUT, PATCH, or DELETE with JSON-shaped inputs. For each action, review the path, input schema, example, provider cost, and customer markup. New actions start disabled; enable them after review. OpenAPI import explains any unsupported operations. You can select up to 50 compatible actions per save from a document containing up to 250 operations.

​
Set pricing

Set a provider cost for each action, then optionally add percentage or flat markup for customers. Both modes produce receipts and activity records.

​
Let agents use the action

Enabled actions appear in the catalog and MCP discovery. Agents use the returned slug like any other tool. Servers can call the standard route:
Reuse the idempotency key for retries. If an action changes data and times out, check the upstream state before starting a new request: the provider may have completed it.

​
Manage access

Disable an action to stop future discovery and execution. Deleting a provider removes its actions and credential from future use; existing receipts and activity remain. See the API reference for schema limits, import formats, and traffic controls.

Connect an agent

Give an agent scoped access to your enabled actions.

Activity and analytics

Track who called your service and what it cost.