From API keyto first call
Quick starts for SMS, phone verification and price-a-number, the full REST reference, the MCP server for agents, the Switch API, and how to connect your switch over SIP or SMPP.
What most people build first
Each quick start is a copy-paste request with the response you get back. Run it with a test key and nothing is delivered or charged to your live balance.
Send an SMS
One POST with a bearer token and a strategy, and we pick the route.
POST /comms/smsQuick start Verify a phone number
Send a one-time code by SMS or voice call, then check what the user typed.
POST /verify/start · /verify/checkQuick start Read a code aloud
Call a number and speak a passcode in one of six languages, then hang up.
POST /comms/voice-otpQuick start Price a number
What every listed route charges for one number, cheapest first. No key needed.
GET /routes/price-numberQuick start Three ways in, one account
REST API reference
Every endpoint, generated from the live API with its fields, access rule and rate limit.
- SMS, bulk SMS and voice calls
- Verify API and voice OTP
- Phone numbers: search, buy, IVR
- Marketplace routes and price-a-number
- Webhooks, errors and idempotency
- Building an app with sub-accounts
MCP server for agents
33 tools on one hosted endpoint: 15 to find, buy, send and verify, and 18 to run a Switch.
- Hosted Streamable HTTP endpoint, nothing to install
- Claude, Cursor or any MCP client
- Route search, purchase and Smart Routing
- SMS, calls and voice passcodes
- Phone verification by SMS or voice
- Balance, charges and x402 top-ups
Switch API reference
Run a wholesale switch from code: suppliers in, customers out, the margin in between.
- Customers, suppliers and IP ACLs
- Route groups, dialplans and failover
- Sell decks and supplier cost decks
- Invoices, credit notes and AR aging
- Payables, counterparties and netting
- Analytics, fraud and self-service portals
- Authentication and scopesAPI keys, test keys and what each scope allows
- Quick startsSMS, Verify, voice OTP and price-a-number
- Every endpointGenerated from the live API
- WebhooksSigned events, delivery log and resend
- Errors and conventionsThe envelope, pagination and safe retries
- Rate limitsPer credential, generated from the API
- Building an appSub-accounts, SIP credentials and numbers
- API changelogWhat changed in the API, and when
- MCP toolsAll 33 tools and their parameters
- x402 top-upsLet an agent fund its own balance in USDC
- Switch routingRoute groups, dialplans and failover
- Switch portalsMagic-link customer and supplier portals
Four protocols, pick what your stack speaks
Voice trunking
Point your switch at the addresses below and authenticate by IP (no registration needed) or per-route username and password, issued instantly on the dashboard Interconnections page.
SMS binds
Buy an SMS route and your bind credentials and host arrive on the Interconnections page, with a one-click bind test. Throughput follows the capacity your route contracts for.
HTTP API
Every platform function over HTTPS, with scoped API keys, signed webhooks and test keys.
For agents
33 tools your agent calls by name, on one hosted endpoint.
Send SIP to 5.9.65.215:5060, failing over to 94.130.218.11:5060, over UDP or TCP. Codecs are G.711 and G.729. Credentials and your IP allow-list are issued per purchase, and an IP change reaches the edge in about 30 seconds. If your switch cannot register with a username and password, use IP authentication: it needs no registration at all. The full SIP profile is in the REST API reference.
Which of our addresses to allow
When we send calls to a switch, it has to allow the address the calls come from. Which one depends on what you set up, not on who owns the switch: if the switch belongs to a carrier you buy from, ask them to allow it.