Integrations

Your tools, callable from the call.

Thirty systems an assistant reads and writes mid-sentence. Plus your frameworks, and the PBX you already run.

POST /v2/ai/assistantstools attach in the same request
{
  "name": "front_desk",
  "tools": [
    { "type": "integration", "provider": "salesforce" },
    { "type": "integration", "provider": "calendly" },
    { "type": "mcp_server", "url": "https://mcp.yourco.com" },
    { "type": "webhook", "url": "https://api.yourco.com/lookup" },
    { "type": "transfer" },
    { "type": "send_sms" }
  ]
}
// t+118 ms: the tool call executes in the same PoP as the media plane

Thirty systems, one line each in the assistant config.

OAuth once. Then the assistant reads and writes by voice.

How a tool call fits in a turn

The tool runs where the call is.

Elsewhere a tool call is an internet round trip. Here it's one building.

one turn, with a tool callfra-pop-2
  1. t+0PSTN in
  2. t+40STTGPU, same rack
  3. t+118tool call · salesforce.lookup(phone)your Function, same PoP
  4. t+156LLMGPU, same rack
  5. t+338TTSGPU, same rack
  6. t+460audio out

x-hops-to-gpu: 0
x-public-internet-transits: 0

Five ways to add a tool

integration30 catalog tools, OAuth once
mcp_serveryour MCP server, any tools
webhookany HTTPS endpoint
client_sidedrive your web UI from the call
built_intransfer, handoff, sms, dtmf, refer

Attach a tool. Make a call. Watch it act.

No code in Mission Control, or one POST by API.

FAQ

Nothing. Tools come with Voice AI at $0.05 a minute. You pay the minute, not the connector.