Tool Gateway

The Tool Gateway lets your agents take actions in external systems (send an email via Gmail, open a GitHub issue, post a Slack message, create a Jira ticket) without you handling OAuth flows or storing secrets in agent code. You connect a provider account once, bind the toolkit to an agent, and the gateway resolves credentials at execution time.

Capabilities

Tool Catalog

Browse toolkits and discover available tools.

Connected Accounts

Authorize providers with managed OAuth.

Bindings

Grant agents access to specific toolkits.

Executing Tools

Run tools synchronously, async, or in batches.

Triggers & Webhooks

Automate tools on external events.

Workspace Groups

Control which tools are available where.

MCP

Integrate Model Context Protocol servers.

Available toolkits

Toolkit	Provider
`GMAIL`	Google
`GOOGLE_SHEETS`	Google
`SLACK`	Slack
`GITHUB`	GitHub
`JIRA`	Atlassian
`WHATSAPP`	Meta

How it works

Connect a provider account via OAuth. Credentials are stored encrypted and never returned by the API.
Bind the toolkit to an agent, linking it to the connected account.
Discover available tools in scope.
Execute tools. The gateway resolves credentials automatically based on the agent’s bindings.

SDK access

Python
TypeScript
curl

from hexel import Hexel

client = Hexel(api_key="YOUR_API_KEY")
toolkits = client.tools.list_toolkits()

import { Hexel } from "hexel-sdk";

const client = new Hexel({ apiKey: "YOUR_API_KEY" });
const toolkits = await client.orchestrator.tools.list();

curl https://api.hexelstudio.com/tools/v1/toolkits \
  -H "Authorization: Bearer $TOKEN"

Errors

Tool Gateway returns a JSON error body: { "error": { "code": "<CODE>", "message": "<human_message>" } }.

HTTP	`code`	When
`400`	`INVALID_REQUEST`	Missing or invalid fields (e.g. `tool_slug is required`).
`403`	—	Not permitted, or the tool isn’t allowed by a workspace group.
`404`	—	Tool, toolkit, connected account, or binding doesn’t exist.
`409`	—	Idempotency conflict — the same key was reused with different parameters.
`429`	—	Rate limit exceeded.

Rate limits

Tool execution is rate-limited at multiple levels: per organization, per toolkit, and per connected account. Provider-side limits also apply per tool. Exceeding any level returns 429. Specific values depend on your plan and the provider — see the Console.

Transient provider failures may fail fast and recover automatically, so a retry shortly after a 5xx from a provider often succeeds.

Security

Concern	How it’s handled
Credentials	Connected-account credentials are encrypted at rest and never returned by the API. The gateway resolves them automatically at execution time.
Authorization	Operations require RBAC permissions; available tools can be constrained per workspace with workspace groups.
Scoping	Connected accounts, bindings, and executions are scoped to your organization, workspace, and environment.

Next steps

Start with the Tool Catalog to see what is available.

Billing & Usage

Support

Capabilities

Tool Catalog

Connected Accounts

Bindings

Executing Tools

Triggers & Webhooks

Workspace Groups

MCP

Available toolkits

How it works

SDK access

Errors

Rate limits

Security

Next steps

​Capabilities

Tool Catalog

Connected Accounts

Bindings

Executing Tools

Triggers & Webhooks

Workspace Groups

MCP

​Available toolkits

​How it works

​SDK access

​Errors

​Rate limits

​Security

​Next steps

Capabilities

Available toolkits

How it works

SDK access

Errors

Rate limits

Security

Next steps