Custom APIs

Custom APIs let you turn any HTTP endpoint into a tool an agent can call. This is the bridge between TOBYBOT and your internal systems — CRMs, databases behind a service, internal automation, or third-party APIs.

Registering a Custom API

Describe the endpoint — its URL, method, parameters, and authentication — and TOBYBOT exposes it as a callable tool:

GET /api/custom-apis    # manage custom API tools

Each registered API becomes available to agents that are granted the matching tool category. The planner decides when to call it and supplies the arguments based on the task.

Authentication

Custom APIs can carry their own credentials (such as a bearer token or API key header) so the agent authenticates to your service without exposing secrets in prompts.

Trust boundary

A custom API gives agents the ability to call your services. Scope each registration to the minimum it needs, and prefer read-only endpoints unless write access is required.

Custom APIs vs. MCP

  • Use a custom API for a single endpoint you control and want to expose quickly.
  • Use an MCP server when a richer set of tools and resources is already packaged behind the protocol.

Removing a Custom API

On the Tools page, open the custom API to edit it and click Delete, then confirm when asked whether to remove it. The same button removes a custom MCP server.

Delete is only offered to people who can edit the connector. In a team, it is not shown for a team connector you do not own. If the removal is refused, the reason is shown and the connector stays in place.

Next Steps