🔌

CUSTOM APIS

Connect any REST endpoint — your agents call YOUR tools

The Tool Bridge lets you register any HTTP endpoint as a tool your agents can call. Internal pricing engines, inventory systems, compliance checkers, ML model endpoints — if it has an API, your agents can use it during deliberation.

WHAT AGENTS SEE

Whatever your API returns. You define the tool: name, base_url, auth, description. Agents call it when relevant to the question. Council handles the request, timeout, error handling.

LIVE EXAMPLE

Council deliberates: "Should we accept this insurance claim?" Agents call 3 internal APIs.

→
POLICY-01:GET /api/insurance/policy/POL-2847 → coverage: fire+flood, excess: €500

Policy covers the claimed event. Excess is €500 — claimant's responsibility.

→
FRAUD-01:POST /api/ml/fraud-score → { claim_id: "CLM-9921" } → score: 0.12

Fraud score 0.12 — low risk. No red flags in pattern analysis.

→
HISTORY-01:GET /api/insurance/claims/history?policy=POL-2847 → 1 claim in 5 years

Clean history. One small claim 3 years ago, properly documented.

◈ Synthesis:

RECOMMENDATION: Approve claim CLM-9921. Policy covers the event. Fraud risk is low (0.12). Clean claims history. Apply €500 excess. Estimated payout: €12,400.

GET CONNECTED

1

Register your API as a tool

In ecosystem settings → Tools → Add HTTP Tool.

{"name": "insurance_api", "type": "http", "base_url": "https://api.internal/insurance", "auth": "Bearer $API_TOKEN", "timeout": 10}
2

Describe what it does

Clear tool description so agents know WHEN to call it, not just how.

3

Set agent permissions

Each agent's ## Tools section lists which tools they can call. Least privilege.

4

Monitor tool usage

Every tool call is logged: which agent, what params, response time, result summary.

▸ CONNECT YOUR APIS
EXPLORE MORE
◎Partners◉Showcase→Waitlist