Give your AI agents a voice, a number, and an inbox.

Phone calls. SMS. Email. One CLI binary. No dashboard needed. Built for autonomous agents.

View docs →

$spix call make --campaign outbound-sales --to +15551234567

Dialing +1 (555) 123-4567...

Ringing...

Call connected

call_id=call_8x7kQ duration=2m14s cost=22cr

Your agent thinks. It plans. It decides.
Then it hits a wall.

No Voice

Making a phone call requires chaining SIP trunks, STT, TTS, answering machine detection, and sub-second latency management. Your agent can't do that alone.

No SMS

A2P 10DLC registration, carrier filtering, opt-out compliance, and delivery receipt tracking are operational nightmares for script-level agents.

No Inbox

Parsing MIME, managing thread histories, handling attachments, and routing across custom domains breaks the flow of agent cognitive loops.

Agents that can't communicate are agents that can't close. Spix gives them a phone, a texting line, and an inbox.

Agents are entering the real world. They need to talk to it.

The next wave of AI isn't about better prompts or longer context windows. It's about agents that act in the physical world: scheduling appointments, closing deals, resolving support tickets, coordinating logistics.

Every one of those actions ends with a human on the other side of a phone call, a text message, or an email. If your agent can't reach people, it's stuck in a sandbox.

90%

of customer interactions still happen over phone, SMS, or email

agent frameworks ship with communications infrastructure

How it works

01 / Install

$curl -sf https://spix.dev/install | sh

Downloading spix-v1.2.0-darwin-arm64...

Extracting to /usr/local/bin...

Spix installed.

02 / Provision

$spix provision number --country US

Searching available inventory...

Allocated: +1 (415) 555-0199
Capabilities: Voice, SMS
Status: Active

03 / Communicate

$spix sms send \

> --to +15551234567 \

> --body "Agent task complete."

Message queued

msg_id=msg_92jKLm

Built for agents,
not humans.

GUIs are anti-patterns for autonomous systems. Spix exposes a CLI, REST API, and MCP server — designed to be executed by code, not clicked by mice.

CLI-first architecture
MCP-native integration
Structured output --json everywhere
Safe testing with --dry-run

$spix inbox read --limit 1 --json

{  "data": [    {      "id": "msg_7xL9q",      "channel": "sms",      "from": "+15559998888",      "body": "Yes, proceed with order.",      "intent_score": 0.98,      "timestamp": "2026-03-11T10:31:00Z"    }  ],  "meta": { "unread": 0 }}

Calls. Texts. Emails.
All from `spix`

As agents move from research tools to real-world participants, they need to talk to people. Schedule appointments. Confirm orders. Follow up on leads. Spix handles the infrastructure so your agents handle the conversations.