The problem sounded almost comically mundane when Ray Liao first described it. His artificial intelligence agents—software programs built to handle customer service, schedule calls, send follow-ups—could execute all sorts of sophisticated tasks. But they couldn't maintain a conversation across platforms. An agent might email a customer from one address, then call from a generic number that bore no connection to the original exchange. Switch to text message? The customer had no idea they were still talking to the same entity.
Identity continuity, it turns out, matters even when the entity isn't human.
Liao's three-person startup, Inkbox, emerged from Y Combinator with a platform that treats agent identity as infrastructure—giving each autonomous program its own email address, phone number, iMessage capability, and stable web address. The San Francisco company launched the service on July 8, positioning it as what Liao calls an "identity and communication layer" for the next generation of automated workers.
The pitch is straightforward, almost pedestrian. Yet it addresses a genuine friction point that emerged as companies started deploying agents in customer-facing roles. These programs need to interact with real people over the channels humans actually use. And those interactions need to persist.
When Bots Need Business Cards
Consider the scenario Inkbox is solving for: A support agent receives an email complaint, responds via text message with a tracking update, then follows up three days later with a phone call to confirm resolution. The customer should recognize it as the same entity throughout—not three separate, anonymous touchpoints from different systems.
That's harder to orchestrate than it sounds. Most companies cobble together separate APIs for email (perhaps Nylas or SendGrid), telephony (Twilio, typically), and messaging—then try to stitch them into a coherent identity. Inkbox bundles the whole stack.
Each identity gets a unique handle and what amounts to a full communications suite. The mailbox handles threaded email with attachments, reply-all, forwarding, and open tracking. As of mid-July, the platform added IMAP and SMTP access—a nod toward developers who want to plug in standard email clients. Phone capability includes inbound and outbound calls with real-time audio over WebSocket, automatic transcription, and SMS/MMS messaging.
Perhaps more telling: iMessage support. Agents can chat one-on-one using either a shared router or a dedicated number, complete with tapbacks, read receipts, typing indicators, and media. The service falls back to SMS or RCS when iMessage isn't available—a detail that suggests the company is thinking carefully about how agents fit into consumer communication patterns, not just enterprise workflows.
Beyond messaging, each identity receives a stable hostname that routes inbound HTTP, WebSocket, and raw TCP traffic directly to the agent. It's infrastructure that gives these programs a web-reachable address without requiring a public IP or firewall changes. The kind of plumbing that sounds boring until you need it.
The Self-Registration Question
The most technically ambitious—and philosophically interesting—feature is agent self-signup. Inkbox detailed it in an April 4 blog post, describing an API that lets an agent create its own provisional identity and resources. But the capabilities are constrained. The agent can only send email to the supervising human until that person receives a verification email and explicitly claims the agent, migrating it into a real workspace.
It's a subtle safeguard, but one that reflects broader industry anxiety about autonomous agents operating without human oversight. The feature walks a line: automate the setup process, but don't let agents run unsupervised.
Liao, who holds a PhD in computer science from MIT and previously cofounded Empallo, built Inkbox with Dima Vremenko and Alex Wilcox. Wilcox brings a master's in computer science from Northeastern and a background in machine learning and networking. The team is small—three people—but they're shipping features at a pace that suggests urgency. IMAP/SMTP support and a hosted voice agent mode both arrived within the same week in July.
What It Costs to Give a Bot an Identity
Inkbox's pricing tiers reveal something about how the company expects customers to deploy these agents. The free tier includes three identities with email, a public URL, and shared iMessage access. Mailbox storage caps at 1 GB, with limits of 2,000 iMessages and three unique recipients per organization per month. Enough to experiment, not enough to run a real operation.
The Developer plan runs $30 monthly for 10 identities, one dedicated phone number with calls and SMS/MMS, 2 GB mailbox storage, and up to 10 custom email domains. The iMessage cap jumps to 10,000 messages and 10 unique recipients per month.
At $200 monthly, the Startup tier provides 100 identities, nine dedicated phone numbers, one dedicated iMessage number, and 100 custom email domains. Organizations can send up to 100,000 iMessages monthly. Those numbers suggest Inkbox expects customers to deploy fleets of agents, not just one or two.
Enterprise pricing is custom. Overage rates run $0.03 per SMS/MMS and $0.03 per call minute—standard telco economics passed through to the customer.
The Competitive Landscape, Such As It Is
Inkbox enters a market still finding its contours. Vapi raised a $50 million Series B in mid-2026 focused specifically on voice AI infrastructure for phone calls. Twilio provides SMS, MMS, and voice APIs but doesn't offer unified agent identity. Nylas offers Agent Accounts, providing app-owned mailboxes without OAuth—a feature that competes directly with Inkbox's email capability. Resend offers inbound email parsing via webhooks for transactional use cases.
What distinguishes Inkbox is less the individual pieces than the bundling. A single identity spanning email, phone, iMessage, and web-reachable addresses, with shared organizational resources like contacts and a credential vault. The approach treats agent identity as infrastructure rather than a collection of separate APIs that developers assemble themselves.
The company open-sourced its telephony stack in early 2024, describing it as a HIPAA-eligible Twilio alternative built on Asterisk and AWS Chime. That infrastructure now powers the platform's phone and messaging features—an unusual move for a startup still finding product-market fit, but one that signals technical confidence.
Early Signals
Vendo, an early customer, runs a team of five agents on Inkbox, according to a company blog post from late July. Each agent has its own email, iMessage access, phone line, and webhook configuration. The case study is light on specifics—how much volume those agents handle, what tasks they're automating—but it suggests teams are deploying Inkbox for both internal automation and customer-facing operations.
Maritime, another company in the ecosystem, announced an integration called "OpenClaw with identity" that uses Inkbox to give each agent its own phone number and email. The announcement included an access code for early users, hinting at partnerships forming around the platform.
Several technical limitations remain visible. iMessage conversations are currently one-to-one; group iMessage isn't supported. Group MMS is in beta. The platform uses rate limits per identity and delivery webhooks to manage throughput, with caps tied to plan tiers. These constraints suggest Inkbox is still scaling infrastructure to meet demand, or perhaps being cautious about abuse vectors.
The broader agent ecosystem is moving quickly. Multiple projects are embedding agents into iMessage and other consumer channels, indicating demand for agent-to-human communication that feels native rather than obviously automated. Companies like Prelude, which raised $20 million earlier this year for trust and onboarding infrastructure in the "AI age," suggest that identity and verification for agents will become a competitive battleground.
The Plumbing No One Thinks About Until It Breaks
Inkbox also ships a zero-knowledge Vault for storing credentials with client-side encryption—the company never sees the plaintext. It supports login secrets with TOTP two-factor authentication, API keys, SSH keys, and other credential types. Agents can generate TOTP codes through the SDK and manage key rotation. An org-wide Contacts directory provides reverse lookup by email or phone, with vCard import and export. Notes stores searchable long-form text that agents can access based on granted permissions.
These features read like infrastructure footnotes, the kind of unglamorous capabilities that matter enormously when you're trying to run agents in production. How does an agent securely store the API key it needs to access your CRM? How does it look up a contact's phone number without exposing the entire company directory? Inkbox's answer is to bundle these utilities into the platform rather than forcing developers to build them separately.
The company ships TypeScript and Python SDKs with what it calls "Skills"—packaged documentation that teaches coding agents how to use the platform. There's a Claude Code plugin that bundles these skills, and a command-line interface available via npm for managing identities, email, phone, vault, and voice configuration. Webhooks are signed per identity for verification.
For developers accustomed to stitching together Twilio for calls, SendGrid for email, and custom infrastructure for everything else, Inkbox's value proposition is integration convenience. Whether that's enough to build a venture-scale business remains an open question. The market for agent infrastructure is still nascent. Customer acquisition costs could be brutal if enterprises default to building this layer themselves rather than buying it.
But there's something clarifying about Inkbox's focus. The company isn't trying to build the agents themselves, or the large language models that power them, or the orchestration layer that decides what tasks to assign. It's building the plumbing that lets agents participate in the communication channels humans already use. Phone numbers. Email addresses. iMessage threads.
The platform is live at inkbox.ai, with documentation and SDKs available for developers who want to give their agents something they've never had before: a persistent identity that follows them across every conversation.
