BetaREST

Telephony

One agent stack across the PyAI network.

Connect managed numbers to one Omni agent, with automatic routing, phone audio, call control and recording handled by PyAI.

Build with the API Read the docs

Price: $0.01/min
Endpoint: POST /v1/telephony/numbers
Scope: telephony:manage
Model id: -

One agent contract

Change the carrier. Keep the agent.

Your phone provider should be transport, not architecture. PyAI puts carrier-specific signaling, media and call control behind one contract, so the agent stays the same.

PyAI network

Primary routeRegional coverageBackup route

PyAI Telephony

Automatic routing, phone-audio conversion, recording and call control.

One Omni agent

The same voice, tools, knowledge and conversation policy on every route.

Managed numbers

United States and India today. India availability depends on regional inventory and required KYC approval.

Automatic routing

PyAI selects eligible primary and backup routes without changing your agent.

Phone controls included

Transfer
DTMF
Hold
Hang up

Point a number at an agent

Search a US area code, provision the number, and route it to your agent, all from the console.

Start in the console

What you get

Automatic routing without an agent rewrite

Use a managed number on the PyAI network. Regional and backup routes reach the same Omni agent contract.

Built for actual phone audio

Native 8 kHz G.711 and PCM handling, echo-aware interruptions, symmetric RTP recovery and regional failover keep network details out of your agent.

Call control and recording in one path

Transfer, touch-tones, hold and hang-up run in the telephony layer. Opt-in recording stays in PyAI's media path.

Capabilities

Managed numbers: US + India
Automatic network routing
Regional coverage
Backup routes where available
Two-region SIP ingress
Native 8 kHz G.711 + PCM
Transfer, DTMF, hold and hang up
Opt-in recording

The telephony edge runs as a two-instance bridge with two-region SIP ingress. Eligible markets use primary and backup routes without pretending any phone number can promise 100% uptime.

Start in minutes

cURL

# 1) Find a San Francisco number, 2) provision + route it to an agent
curl 'https://api.pyai.com/v1/telephony/available?area_code=415' \
  -H "Authorization: Bearer $PYAI_KEY"

curl https://api.pyai.com/v1/telephony/numbers \
  -H "Authorization: Bearer $PYAI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"phone_number":"+14155550123","agent_id":"front_desk"}'

FAQ

Which countries are supported?

Managed-number provisioning currently supports the United States and India. India numbers require available inventory and KYC approval. Canada, Australia and the United Kingdom are not yet self-serve managed-number markets.

How are calls routed?

PyAI selects eligible regional routes automatically. Coverage, number inventory and regulatory onboarding vary by country.

Are calls recorded for free?

Recording is opt-in and handled in PyAI's media path. Do not assume recording is lawful by default: configure the consent line, retention and regional requirements for each call. Check the current pricing page for any applicable storage or add-on charges.

Can the agent transfer to a human or send DTMF?

Yes. Managed Telephony executes transfers, touch-tones, hold and hang-up in the call transport, while the same Omni agent decides when each action should happen.

What happens if a network route fails?

The bridge runs multiple instances and eligible markets can use primary and backup regional routes. Route availability varies by number and market.

How is Telephony billed?

Connected minutes bill on a 1-minute pulse, on top of the call's Omni or Agent minutes. Check the pricing page for the current managed-telephony rate.

Build with Telephony today.

An instant sandbox key lets you test without billing. Create an account when you want saved projects, and fund a live key for production traffic.

Build with the API Launch an Agent

Agents is live in beta. Sandbox keys have daily limits and never touch billing.