Niches · Phone calling & voice transport
Place an outbound call from code and bridge it to the agent
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
One API call creates the call and returns a call id; the answered call connects audio to the agent both ways; a retried create after a timeout does not ring the person twice (idempotency key, command id or a documented list-then-retry); destination and spend limits are documented.
Measured, for our own tests: on a 10-call test no destination rings twice and every connected call carries two-way audio. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: call this number and connect it to my agent
, have the AI call me
, dial out and stream the audio
, ring the customer back
Does the job, with a limit 14
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| 46elks Voice API E 46elks AB | POST /calls returns an id and llms.txt says Realtime Voice works on outgoing calls, but no idempotency key exists and the llms.txt advice is to check call history before retrying. No spend or destination limits found. source |
| Bandwidth Voice API + MCP BB Bandwidth Inc. | POST /calls returns a callId and the answer BXML can start a bidirectional stream; over-limit creates get a 429 with a named reason or queue. No idempotency key in the Voice OpenAPI spec, and no destination or spend controls found. source |
| didlogic Voice API D DID Logic PTE. LTD. | POST /api/v1/click2call with a_type stream connects your WebSocket first, then dials and bridges, returning a call id; /api/v1/call_price prices a destination first. No idempotency key, and the stream protocol is undocumented. source |
| Exotel Voice API + MCP E Exotel Techcom Private Limited | Legs API start_stream attaches a bidirectional stream to an answered leg, and the v3 call API returns a call id. No idempotency key or spend limit found, and trial accounts must whitelist numbers (listing notes). source |
| Infobip Calls API + MCP B Infobip Ltd | Create call returns a call id and the answered leg can be joined to a WEBSOCKET leg, but there is no idempotency key, so a retried create can dial twice; no destination or spend limits in the pages read. source |
| jambonz D FirstFive8, Inc. | REST create call takes from, to and an application or call_hook and returns a call sid, but needs your own SIP carrier, and no idempotency key exists, so a retried create can dial twice. source |
| LiveKit Telephony BB LiveKit Incorporated | CreateSIPParticipant dials through an outbound trunk from another carrier and wait_until_answered returns on answer, but no idempotency key exists, LiveKit numbers cannot dial out, and acc-22 lost parts of words on outbound TTS. source |
| Plivo Voice API B Plivo Inc. | The Calls API creates a call whose answer XML starts the bidirectional stream, but there is no idempotency key, outbound CPS is 1 a second on new accounts, and abandoned or very short calls above thresholds carry surcharges. source |
| SignalWire Voice API B SignalWire, Inc. | The REST Calling API dials with a SWML url and returns a call id, but there is no idempotency key, and acc-14 had a call placed twice with no audio. source |
| Sinch Voice API + MCP B Sinch AB (publ) | POST /v2/projects/{projectId}/calls creates a call that can dial a stream, and v2 writes take an Idempotency-Key honoured for 10 minutes, so a retry does not ring twice. Still preview, and trial accounts dial verified numbers one at a time (listing notes). source |
| Telnyx Voice API + MCP BB Telnyx LLC | Dial takes stream_url and the bidirectional settings so the answered call streams both ways, and command_id guards retried call commands; acc-37 and acc-39 run outbound agents on Telnyx. Destination and spend limits were not found, and command_id on the creating dial is not confirmed. source |
| Twilio Programmable Voice API + MCP A Twilio Inc. | The Calls resource creates a call whose TwiML connects a stream, but there is no idempotency key (check the Calls list before retrying), the default is 1 call a second, trial calls reach only verified numbers, and acc-48 connected with no audio either way. source |
| Vonage Voice API + MCP C Vonage Holdings Corp. | POST /v1/calls creates a call whose NCCO connects the websocket, but no idempotency key or spend controls were found in the pages read. source |
| Voximplant C Voximplant, Inc. | StartScenarios starts a session that places a PSTN call and bridges it to the agent, per the outbound examples, but no idempotency key is documented and expensive destinations sit behind a support-lifted block (listing notes). source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| DIDWW Voice and Number Management API B DIDWW Ireland Limited | No call-create resource; outbound calls are placed by the customer's SIP system through an Outbound Trunk, which needs a separate access application. source |
What stops agents finishing
- no idempotency key on call create, so a retry can dial twice (acc-14)
- outbound needs a separate carrier trunk on SIP-only listings (LiveKit, jambonz, DIDWW)
- trial accounts dial only verified numbers in the sign-up country
- outbound trunk or high-cost destinations gated behind a business application or support ticket
Around it
Before: crm.find-record, scheduling.find-free-slot. After: voice-agents.outbound-campaign, voice-agents.agent-places-call, voice-calling.record-and-retrieve.
Where this comes from
Weight 14 of 100 in Phone calling & voice transport: 7 of 49 accounts (double-triggered SignalWire call, outbound calls with no audio, faded outbound TTS over SIP, a toll-fraud guard request, personal and accessibility apps that phone people); the Twilio starter repos also took an outbound-call pull request and two how-to issues
The same as data: /api/v1/use-cases/voice-calling.place-outbound-call.json, or the MCP tool get_use_case with id voice-calling.place-outbound-call. Other jobs in this category: /api/v1/niches?category=voice-calling.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.