Inkbox
Give every AI agent an identity: email, phone, iMessage, internet address, and A2A.
If you're building agents that need to be reached like teammates—email, phone, iMessage—Inkbox is the most coherent way to get there without duct-taping five APIs. The zero-knowledge vault, per-identity filtering, and brokered A2A are genuinely useful differentiators. But watch SMS/voice overages and shared iMessage caps; for outbound-only notifications, Twilio or SendGrid might still be lighter.
Verified 5d ago · liveness 81/100 · cite: rightaichoice.com/tools/inkbox
- Developers building AI agents that need multi-channel communication (email, phone, SMS, iMessage)
- Teams deploying production agent fleets requiring persistent identity and inbound connectivity
- Startups running agent fleets with dedicated phone/iMessage numbers and A2A handoffs
- Solo hobbyists experimenting with agent communication on the free tier
- Users looking for a standalone email or phone service without agent integration
- Teams that only need outbound notifications and don't require inbound communication
- Projects that need fully on-premise identity management (Inkbox is cloud-based)
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Inkbox if you only need outbound notifications without inbound communication, or if your SMS/voice volume is high enough that $0.03 overage per message/minute would spiral.
SMS/MMS overage is $0.03 per message beyond your plan allowance, which adds up fast if you're doing high-volume texting.
Inkbox's free tier (3 identities, email, tunnel, shared iMessage) is generous for experiments. At $30/mo Developer you get a phone number and 10 identities—cheaper than assembling Twilio+SendGrid+ngrok. For fleets, $200/mo Startup (100 identities, 9 phone numbers, 1 dedicated iMessage) beats per-API costs. Enterprise is custom.
In short
Inkbox — Give every AI agent an identity: email, phone, iMessage, internet address, and A2A. Best for Developers building AI agents that need multi-channel communication (email, phone, SMS, iMessage), Teams deploying production agent fleets requiring persistent identity and inbound connectivity, Startups running agent fleets with dedicated phone/iMessage numbers and A2A handoffs. Free to start; paid plans from $30/mo.
What's new in Inkbox
Checked 3 days agoAcross the latest 10 updates: 7 feature updates, 2 changelog entries and 1 news mention.
Python SDK retries dropped connections
Python SDK 0.6.4 retries on connection reset before request send, without resending in-progress requests.
Onboarding skill guides agents through setup
New bundled onboarding skill walks agents through identity checks, channel readiness, consent, call handling, and recurring triage.
Share SMS opt-in with a scan or tap
Inkbox Console now shows QR code or opens pre-filled text message for START opt-in to an agent's phone number.
Agent2Agent and group iMessage from MCP clients
MCP toolset discovers agents, manages async A2A tasks, starts/continues dedicated-line group iMessage conversations.
Full lifecycle for email drafts
Create, edit, send email drafts with attachments, duplication, deletion, retry-safe sending across all SDKs.
Simpler dedicated iMessage line type
Dedicated lines no longer require choosing inbound/outbound role; SDK 0.6.0 removes selector and capability args.
Share iMessage contact card automatically
Dedicated iMessage lines now auto-share agent name and photo; configurable via console, SDKs, CLI.
Remove iMessage tapbacks
Agents can remove reactions via console, API, SDKs, CLI, MCP, using reaction ID from message history.
Forward incoming calls to phone number or SIP address
Set identity's incoming-call action to forward all inbound calls; inspect attempts separately from final status.
Why agent-to-agent on Inkbox is brokered, not peer-to-peer
Inkbox implements A2A spec but as agent endpoint; explains brokered network design rationale.
What people actually say about Inkbox — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
14 mentions across 2 sources (Hacker News, Lemmy) · researched Jul 3, 2026.
- +Unified identity model across email, phone, and messaging.
- +Zero-knowledge vault for secrets – Inkbox never sees plaintext.
- +Agent self-signup capability for automated provisioning.
- +Real-time audio streaming for phone calls.
- +Plugins for popular agent frameworks like Hermes and Claude Code.
- −Very limited community feedback makes reliability unknown.
- −Name clashes with other products cause search confusion.
- −No public data on uptime or latency guarantees.
- −Pricing per SMS/MMS ($0.03) could add up at scale.
- −iMessage support requires opt-in – not fully open.
- • SMS/MMS at $0.03 per message
- • Call minutes at $0.03 per minute
Viability Score
How well maintained and how widely used is Inkbox? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: September 2026
How we score →Key Features
- Agent identities with globally unique handles
- Real email inbox (send/receive, threads, search)
- Public tunnel URL for inbound HTTP, WebSocket, raw TCP
- Real phone numbers with voice calls and SMS/MMS
- iMessage support: shared and dedicated numbers
- Outbound iMessage group chats (2-8 recipients) with media
- Inkbox Voice AI (beta) with contact_scoped and yolo authority modes
- Reachability lookup for iMessage, SMS, RCS
- Contact memory with cited history
- MBOX, EML, ZIP mail imports into inboxes
- Zero-knowledge encrypted vault for credentials
- Per-identity whitelist/blacklist filtering
- IMAP/SMTP access for external mail apps
- Agent self-signup without human account
- Agent2Agent (A2A) brokered and enabled by default
About Inkbox
Inkbox is an identity and communication layer for AI agents. Instead of stitching together Twilio, SendGrid, and other point solutions, you provision a single persistent identity per agent. Each identity bundles a globally unique handle, a real email inbox, a stable public tunnel URL for inbound HTTP, WebSocket, and raw TCP, and—optionally—a real phone number with voice and SMS/MMS. It also includes an Agent2Agent (A2A) channel, so agents can reach each other directly, plus org-level contacts, notes, and a zero-knowledge encrypted credential vault. Built for developers shipping production agents, Inkbox replaces the need to wire together multiple communication APIs with one abstraction. Backed by Y Combinator. Recent releases expand the platform. Inkbox Voice AI (beta) now offers zero-setup voice calls with contact_scoped and yolo authority modes, per-call voicemail control, and mode inheritance. MCP clients can connect directly to an identity, and agents can look up reachability across iMessage, SMS, and RCS to pick the best channel before sending. You can import MBOX/EML/ZIP archives into an inbox, and every plan includes IMAP/SMTP access for attaching a standard mail app. Self-serve dedicated iMessage numbers are live, and agents can start outbound group chats (2–8 recipients), send media and effects, and read history. Contact memory automatically derives concise memories from a contact's email, SMS, iMessage, and call history, with cited source correspondence. Agent2Agent is now brokered by default, letting agents contact one another without exposing endpoints, and a support agent via A2A lets your agent ask Inkbox's own support agent questions. Invitation links let you bring in customer agents with one link, and A2A directories are now public and org-based. For developers running multi-channel agents, Inkbox is a more unified alternative to stitching together separate communication APIs. Its shared iMessage router requires recipients to initiate
Behind the Verdict
Inkbox is the rare tool that makes agent identity feel like a solved problem. Instead of wiring up Twilio for SMS, SendGrid for email, and a tunnel service for inbound HTTP, you get one API that handles all of it—plus iMessage, which is notoriously painful to access legitimately. For teams running multiple agents, the per-agent identity model is a huge time-saver; you can even let the agent sign itself up using a prompt, which is a neat touch. What makes it stand out is the A2A channel. Most agent communication tools stop at human-to-agent; Inkbox lets agents talk to each other natively, with brokering so you don't expose endpoints. That's a big deal if you're building a fleet that needs to hand off work. The support agent via A2A is a clever way to get help without leaving your terminal. Where it bites: costs can creep up. SMS/MMS overages are $0.03 per message, and call minutes $0.03 per minute. If you're doing high-volume notifications, those add up fast. The shared iMessage router has caps on recipients and requires them to initiate—so if you need to cold-start conversations, you'll need a dedicated iMessage line, which only comes with the Startup plan or higher. Also, the free tier is limited to 3 identities and 1 GiB per mailbox, so if you have a bigger fleet, you'll be paying quickly. Compared to alternatives, Inkbox is the most integrated option. Twilio gives you granular control but forces you to build everything yourself. SendGrid is fine for email but doesn't do phone. With Inkbox, you get email, phone, iMessage, tunnel, and A2A in one package. The downside is that you're locked into their platform, and you miss the fine-grained control power users might want. In practice, we'd reach for Inkbox when you have agents that need to be reachable like a
Researching Inkbox? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Inkbox actually fits — and what changes day-one when you adopt it.
You want to give your agent an email, phone, and SMS so customers can reach it, and it can follow up.
Outcome: On the Free tier, you create an identity, get an @inkboxmail.com email, a tunnel URL, and shared iMessage. Your agent answers email and iMessage, and you test inbound HTTP via the tunnel. Upgrade to Developer when you need a phone number.
You need 5+ agents each with their own mailbox, phone number, and iMessage presence, plus A2A handoffs.
Outcome: On Startup, you provision 100 identities, attach 9 phone numbers, and enable a dedicated iMessage line. Your agents share contacts, notes, and vault secrets scoped per agent, and hand off tasks via A2A without a human in the loop.
Use Cases
- Customer support agent that handles email, phone, and SMS with full conversation history across channels.
- Outbound sales agent that texts appointment reminders and follows up via email.
- Automated phone operator using Inkbox Voice AI to answer calls and take actions like texting or emailing mid-call.
- Developer tool agent that receives webhook callbacks on a public tunnel and responds via email.
- Agent that manages secrets (API keys, SSH keys) in the zero-knowledge vault and uses them to authenticate to third-party services.
- Team of agents (e.g., engineering, GTM, ops) each with their own mailbox, phone number, and iMessage presence, as used by Vendo.
Limitations
- Phone numbers require paid plans (1 on Developer $30/mo, 9 on Startup $200/mo). iMessage caps on shared router limit messages and unique recipients per plan (e.g., Free: 2,000 messages, 3 recipients).
- Unused allowances do not roll over.
- Overage charges apply for SMS/MMS ($0.03/msg) and call minutes ($0.03/min).
- Custom email domains require domain ownership.
- Free tier includes no phone numbers and limited iMessage.
- Mailbox storage caps apply; sends over cap are refused (inbound always accepted).
as of 2026-08-21
Verification history
We have re-verified Inkbox 7 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 7 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Inkbox tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0/month
Ideal for
Solo developers exploring agent communication with 3 identities, email, tunnel, and shared iMessage—no phone numbers.
What this tier adds
Starting tier: 3 identities, 1 GiB mail per mailbox, shared iMessage (2,000 msgs/3 recipients), no phone numbers, no custom domains.
Developer
$30/month
Ideal for
Developers running agents in production with a dedicated phone number and up to 10 identities for testing small deployments.
What this tier adds
Adds: 10 identities (up from 3), 1 dedicated phone number, 2 GiB mail, 300 SMS/MMS and 30 call minutes per month, 10 custom email domains, removes email footer watermark.
Startup
$200/month
Ideal for
Startups running agent fleets needing 100 identities, 9 phone numbers, and a dedicated iMessage line for outbound starts.
What this tier adds
Adds: 100 identities, 9 phone numbers, 1 dedicated iMessage line (iMessage/RCS/SMS/MMS, outbound starts), 100 custom email domains, up to 100,000 iMessages/100 recipients via shared router.
Enterprise
Custom
Ideal for
Teams with custom requirements needing higher rate limits, more identities, phone numbers, seats, and dedicated iMessage infrastructure.
What this tier adds
Custom: volume pricing, custom allowances, higher API rate limits, dedicated iMessage infrastructure, dedicated support and white glove onboarding.
Where the pricing makes sense
The company stage and team size where Inkbox's pricing actually pencils out — and where peers do it cheaper.
Inkbox's free tier (3 identities, email, tunnel, shared iMessage) is generous for experiments. At $30/mo Developer you get a phone number and 10 identities—cheaper than assembling Twilio+SendGrid+ngrok. For fleets, $200/mo Startup (100 identities, 9 phone numbers, 1 dedicated iMessage) beats per-API costs. Enterprise is custom.
Setup time & first value
How long it actually takes to get something useful out of Inkbox — broken out by persona, not the marketing-page minute.
Solo dev: create an identity via CLI/SDK in about 5 minutes; send your first email and call in under 20 minutes. Startup team: provisioning 100 identities and attaching phone numbers takes a few hours, including 10DLC registration if you need your own SMS sender. Agent self-signup lets your agent set itself up in minutes.
Switching to or from Inkbox
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From Twilio + SendGrid + ngrok: Replace separate APIs with Inkbox's unified identity; import your contacts and route channels through one SDK.
- ↗To Twilio/SendGrid: If you only need outbound SMS/email, move your logic to Twilio's API and SendGrid's email API—costs may be lower for high volume.
Integrations
Resources & Guides
Tutorials & Learning
Official links
Tools that pair well with Inkbox
Common stack mates teams adopt alongside Inkbox, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Inkbox vs Spider Cloud
Inkbox and Spider Cloud solve completely different problems. If your AI agents need to send/receive emails, SMS, iMessage, or handle phone calls with persistent identity, Inkbox is your only plug-and-play option. If your agents need to crawl the web at scale for RAG data, Spider Cloud delivers faster and cheaper with its Rust engine. Choose based on need—communication vs. data ingestion.
Inkbox vs Presto Voice
Presto Voice and Inkbox serve completely different purposes: Presto Voice is a specialized drive-thru voice AI for QSR chains, focusing on order automation and upselling, while Inkbox is a developer-oriented identity layer for AI agents needing multi-channel communication. Choose Presto Voice if you operate a QSR drive-thru and want to boost revenue and efficiency; choose Inkbox if you are building AI agents that need email, phone, or iMessage capabilities.
Inkbox vs Temporal Ai
Choose Temporal AI if your priority is building fault-tolerant, long-running workflows or AI agents that survive crashes and need orchestration. Choose Inkbox if your agents need a persistent identity with email, phone, and iMessage communication channels. They solve different problems; consider using both together for a reliable, communicative agent.
Alternatives to Inkbox
View allPopular in Agent Memory & Runtimes
Frequently Asked Questions
Used Inkbox? Help shape our editorial sentiment research.