Launching today

Spix
Give your AI agents a voice, a number, and an inbox.
2 followers
Give your AI agents a voice, a number, and an inbox.
2 followers
Spix is the first communications platform built for AI agents, not humans. No dashboard, no drag-and-drop builders, just a single CLI binary that lets any agent make phone calls, send SMS, and send email with one command. What makes it different: - CLI-first: works with OpenClaw, Claude Code, Codex, and any agent framework - Flags-first: zero interactive prompts, fully scriptable - Built-in AI voice calls with STT + TTS + LLM orchestration - Credit-based billing — pay only for what agents use






Hey Product Hunt! I'm Michael, the builder behind Spix.
I use OpenClaw to run AI agents that handle real work for me, research, scheduling, outreach. But every time an agent needed to actually call me with an update, text a contact, or receive an email on my behalf, I hit a wall. I'd have to manually set up forwarding, copy-paste between dashboards, and babysit the whole process. The agent could think and plan, but it couldn't communicate.
That's the gap Spix fills. It's a single CLI binary that gives any AI agent phone calls, SMS, and email as native capabilities. No web dashboard. No drag-and-drop flows. Just spix call start or spix sms send and it works.
But here's the bigger picture: agent-to-human communication is going to dwarf human-to-human communication. Not because humans will talk less, but because agents need to reach people, businesses, and systems that aren't connected to the AI-first world yet. Your doctor's office doesn't have an API. Your landlord doesn't check Slack. The local permit office doesn't accept webhooks. For agents to be truly useful, they need to pick up a phone, send a text, and write an email, the same channels humans already use.
That's what Spix enables. Every command is fully expressible as flags (no interactive prompts), everything returns structured JSON, and it ships with a built-in MCP server so Claude Code, OpenClaw, Codex, and any agent framework can use it natively.
I'd love to hear how you're thinking about giving your agents real-world communication abilities. Happy to answer any questions!
You make a very interesting point about the doctor’s office not having webhooks and landlords not checking slack; I’m curious about how Spix converts to real impact for everyday users who aren’t necessarily as tech savvy; what additional infrastructure would they need to maximize Spix considering that cli, computer use etc are still mostly used by early adopters.