HTTP Call (infrastructure)

What it is

The HTTP Call is the native tool type underneath every custom HTTP tool you create. Each configured endpoint (URL, method, auth, parameters) is registered internally as an HTTP Call instance — and the agent invokes each by the technical name you defined.

You don’t add “HTTP Call” directly from the native tools menu. It exists under a different flow: creating a custom HTTP tool.

Where you actually configure

Creating and configuring HTTP tools happens under Tools in the side menu:

Tools → Active → + New Custom Tool

Once created, the tool appears under OTHER TOOLS when you click + Add Tool in any agent in the organization.

Detailed creation flow in Custom HTTP Tools.

When to use

Whenever the agent needs to talk to an external system not covered by Composio integrations or other native tools:

• Your company’s internal API (proprietary CRM, ERP, billing system).
• Custom automation webhook (Zapier, Make, n8n) you want the agent to trigger.
• Public service without a ready integration (any REST API).
• Calculation or processing that lives in a backend of yours.

How the agent invokes

Each HTTP tool you configure appears to the model with:

• the technical name you defined;
• the description you wrote;
• the parameter list it accepts.

The agent decides to call a specific HTTP tool when the user’s question matches the tool’s description. Description quality and parameter naming are what most influences this behavior.

When called, SquadOS builds the HTTP request on the server, injects credentials (if configured), sends it, receives the response, and returns the result to the agent.

Why this tool appears in this list

http_api is technically a native tool because it shares the same internal infrastructure as the others (registration, validation, execution). But from a usage standpoint, the configuration path is completely different — you don’t go to the native tools menu and click “HTTP Call”. You go to Tools → + New Custom Tool and configure the endpoint.

Limitations and notes

• Detailed configuration is in another doc. See Custom HTTP Tools for URL, method, auth, body template, and parameters.
• Credentials stay on the server. Tokens and secrets are stored encrypted — the model never receives the secret, only the call result.
• Test before publishing. Each HTTP tool has a test in the form itself; it’s only considered configured (green) after a successful test.
• Available scopes: HTTP tools are created at the organization scope and any agent can enable them. There is no per-agent creation scope.