Give your AI agent a phone number.

An API that provisions real numbers for AI agents — SMS, call plumbing, webhooks, and bridges into your voice stack.

No spam. Unsubscribe anytime.

Example request

POST /v1/numbers
Authorization: Bearer sk_live_…

{
  "region": "US",
  "capabilities": ["sms", "voice"]
}

// 201 Created
{
  "id": "num_8f2a",
  "e164": "+14155550123",
  "webhook_url": "https://api.you.com/agent/hooks"
}

How it works

Three steps from API key to a line your agent can text and answer.

  1. 01

    Provision a number via API

    Create a number with the regions and capabilities you need. Attach webhooks for SMS and voice events.

  2. 02

    Connect your stack

    Point webhooks at your server, or terminate media on SIP or a WebSocket stream into your agent runtime.

  3. 03

    Your agent sends texts and takes calls

    Outbound SMS and calls use the same number. Inbound traffic hits your logic — not a bundled black-box assistant.

API sketch

Provision, send SMS, and handle an inbound call webhook. Names and fields may change before launch.

# 1. Provision a number
curl -X POST https://api.numberforagents.com/v1/numbers \
  -H "Authorization: Bearer $NFA_TOKEN" \
  -d '{"region":"US","capabilities":["sms","voice"]}'

# 2. Send an SMS from that number
curl -X POST https://api.numberforagents.com/v1/messages \
  -H "Authorization: Bearer $NFA_TOKEN" \
  -d '{
    "from": "+14155550123",
    "to": "+14155559876",
    "body": "Your appointment is confirmed for 3pm."
  }'

# 3. Inbound call webhook (your server)
POST /agent/voice/inbound
{
  "type": "call.started",
  "call_id": "call_91bc",
  "from": "+14155559876",
  "to": "+14155550123",
  "media": {
    "websocket_url": "wss://stream.numberforagents.com/…"
  }
}

# Respond with instructions for your voice pipeline
{
  "action": "connect_media",
  "sip_uri": "sip:agent@your-voice.example"
}

Features

Telecom primitives for agents. You own the conversation layer.

Number provisioning

Search and buy numbers through a single REST API. One agent, one line, or a pool.

SMS in / out

Send and receive texts with delivery receipts and threaded conversation IDs.

Call plumbing in / out

Originate and receive calls with clear events for ring, answer, and hangup.

Webhooks

Signed HTTP callbacks for SMS and voice state changes your worker can trust.

SIP trunking

Hand off audio to your PBX, CPaaS, or custom SIP endpoint.

WebSocket media streams

Stream audio to your app for STT, TTS, and model turns in real time.

Inbox, voicemail, call logs

Operator-friendly views and exports while your agent stays the source of truth.

Bring your own voice stack

Use your model, Bland, Vapi, Retell, or anything that speaks SIP or WebSocket.

Plumbing, not a platform.

We do not ship a bundled voice AI. You get numbers, protocols, and events — built API-first for developers who already have an agent.

  • No bundled assistant
  • API-first
  • Built for developers

Pricing

Simple per-number pricing. Waitlist members lock in early pricing.

Details at launch. Join below to reserve your spot.

FAQ

Common questions about agent phone lines and the API.

  • What is a phone number for an AI agent?

    It is a real telephone number assigned to your agent so people can text or call it. Your code owns the logic: the API provisions the number and delivers events to your webhooks or media bridges.

  • How does the agent answer calls?

    When someone calls your number, we send your server a webhook and can connect the call to your stack over SIP or a WebSocket media stream. Your application decides what to say and when to transfer or hang up.

  • Do you provide the voice AI?

    No. We provide telecom plumbing: numbers, SMS, and call routing. You bring your own model, orchestration, or a provider such as Bland, Vapi, or Retell.

  • Can I bring my own carrier numbers?

    Porting and BYOC are on the roadmap. Early waitlist members will help us prioritize regions and carriers. Tell us what you need when you sign up.

  • Which countries will you support?

    We plan to launch with US and Canada numbers first, then expand based on waitlist demand. International SMS and voice have separate compliance rules; we will publish a country matrix before general availability.

  • Is this for OTP or account verification?

    No. Numbers for Agents is for product-facing agent lines: support, scheduling, outbound campaigns you control, and voice assistants you build. We do not support verification-bypass use cases.

  • When is launch?

    We are in private development. Join the waitlist for API access, docs previews, and early pricing. We email invite waves in signup order when capacity allows.

Guides: Give your agent a number, SMS API explained, Voice call plumbing.

Join the waitlist

Get API access and early pricing when we open the beta.