// 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.
COMPOSITION
Pick the job. The tools and the primitives light up.
Eight assistants built on the tools above. Pick one and the blocks it runs on light up, the create call writes itself with the integrations attached, the meter prices it. Or click any single block: every primitive sells alone.
Loading...
One request. Tools attached. You pay the minute, not the connector.
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
t+0PSTN in
t+40STTGPU, same rack
t+118tool call · salesforce.lookup(phone)your Function, same PoP
t+156LLMGPU, same rack
t+338TTSGPU, same rack
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
Frameworks, MCP and CLI
Bring yours. The stack underneath doesn't change.
Each one runs on the Telnyx product named above it.