WillItSurvive
YC Summer 2026 · United States

Inkbox

Identity and comms layer giving AI agents email, phone, iMessage, and a vault.

Protection under test
Assessed 26 July 2026 · Evidence as of 26 July 2026
Something worth protecting exists and is being tested right now.
On the recordSince 26 July 2026 · Checkable from September 2026 · Every call on the record Checkpoint: Y Combinator S26 Demo Day, which will show funding and investor interest
The call

Inkbox is a three-person team betting that agents will need a stitched identity layer before Twilio, Auth0, or the labs build one themselves.

Inkbox is a small company building plumbing that lets AI agents send messages through email, text, iMessage, and other channels while verifying who they are. The problem is that connecting these channels together is straightforward technical work, not something that is hard to copy. Twilio, Visa, Mastercard, and other big companies already have all the pieces and the financial reason to stitch this together themselves, while Anthropic and OpenAI could fold agent-communication directly into their AI systems. The one thing that could matter is whether the three founders have deep experience in telecom compliance and carrier relationships (which would be genuinely hard to build from scratch) or whether they are just linking existing tools together, which anyone could do. Also, Inkbox depends on Apple's iMessage relay working, but Apple has shut down similar workarounds before, so that advantage could disappear anytime.

Why
01
AI pressure: Anthropic, OpenAI, Google bundling agent identity/auth into MCP or A2A frameworks. If labs bake identity and messaging into their own agent protocols, Inkbox's relay layer becomes a thin, skippable add-on. Could AI do the core job? Yes, likely.
02
Bigger players: Twilio, plus Auth0, Okta, Visa TAP, and Mastercard Agent Pay. Visa's TAP and Mastercard's Agent Pay already give agents network-backed identity, and Twilio can bundle similar plumbing into its existing CPaaS platform. Could a giant copy it? Yes, easily.
03
What protects it. Being first to stitch email, phone, iMessage, and a credential vault into one SDK, and already living inside Claude Code and OpenCode before bigger players bother.
What would change this call
Twilio or Auth0 announces a native agent-identity or agent-communications feature within 12 months. Would show incumbents absorbing Inkbox's core use case without needing to acquire it.
Anthropic, OpenAI or Google bundles agent-identity/auth natively into MCP or A2A frameworks. Would show frontier labs commoditizing the relay layer Inkbox depends on.
Apple restricts or shuts down unauthorized iMessage relay access used by Inkbox. Would remove a key product feature Inkbox does not control.
Key numbers
  • 3 co-founders run the company (2026-07-09)
  • About 10 GitHub stars on the SDK repo (2026-06-09)
  • OpenCode plugin shipped July 21, 2026 (2026-07-21)
Named risks
  • No shipped moat; core integration glue is economically easy for Twilio, Auth0, Okta, or frontier labs to absorb. Severity: high
  • iMessage relay depends on an unofficial workaround on a platform (Apple) that has shut down similar tools before. Severity: high
  • No disclosed funding, revenue, or customers as a 3-person company; runway and survival unclear. Severity: high
  • Fast-moving standards (IETF AIP draft, Visa TAP, Mastercard Agent Pay) could commoditize the niche before Inkbox gains lock-in. Severity: medium
  • Minimal developer traction signal (~10 GitHub stars) as of June 2026 despite active shipping. Severity: medium
Rivals, as read in July 2026
RivalDirectionEvidence
TwiliocontestingPositions against Twilio's lack of native AI voice agent and required custom stitching, per May 20 2026 comparison
Visa (Trusted Agent Protocol)losing toVisa TAP had 100+ partners and hundreds of agent transactions by Dec 18 2025, far ahead of Inkbox's traction
Mastercard (Agent Pay)losing toMastercard Agent Pay rolled out in the US in November 2025, an incumbent-scale identity/payments move
AgentPhonecontestingDirect peer offering phone numbers, SMS, and voice APIs for AI agents as of July 2026
SkyfirecontestingKYA token-binding identity tool positioned as leading agentic-commerce identity product as of July 10 2026
Auth0, WorkOS, Oktalosing toEnterprise identity incumbents already shipping agent-auth features as of July 10 2026 comparison
Questions people ask
Is Inkbox profitable or does it have paying customers in 2026?
No revenue, customer counts, or enterprise logos have been disclosed as of July 2026. Inkbox says early users have agents sending and receiving email and iMessage through the platform, per a July 9, 2026 newsletter summary of its launch, but this is unverified vendor-reported traction.
Who owns Inkbox and has it raised funding?
Inkbox is privately held and part of Y Combinator's Summer 2026 (S26) batch as of July 2026. No funding amount or valuation has been disclosed; YC lists it simply as Active with a team of three and no other named institutional investors.
How many employees does Inkbox have?
Inkbox has three employees, the co-founders Ray Liao, Alex Wilcox, and Dima Vremenko, per Y Combinator's company listing as of July 2026. No open job postings were found on YC's platform, suggesting no publicized near-term hiring push.
Could AI labs like OpenAI or Anthropic replace Inkbox?
Possibly. Inkbox's core function, stitching email, phone, and iMessage access for AI agents, is integration glue that frontier labs could subsume natively via MCP/A2A protocol tooling, which would commoditize its thin relay layer, per a July 10, 2026 HackerNoon analysis of the emerging agent-identity space.
Who is Inkbox's biggest competitor?
Twilio is the dominant CPaaS incumbent Inkbox positions against, alongside direct peers AgentPhone and Skyfire (KYA identity tokens), plus Auth0, WorkOS, and Okta in agent authentication, and Visa's Trusted Agent Protocol and Mastercard's Agent Pay in agent-commerce identity, all active in the same space as of mid-2026.
What does Inkbox actually build?
Inkbox gives AI agents an identity: custom-domain email, toll-free phone numbers with SMS/MMS and voice, iMessage access, an encrypted credential vault, and outbound tunnels, via Python and TypeScript SDKs, a CLI, and agent skills for Claude Code, per its GitHub repo dated June 9, 2026.
Timeline
  • 2026-07-21Released OpenCode plugin giving OpenCode coding agents Inkbox identity with autostart integration
  • 2026-07-09Third-party newsletter reports early users' agents sending/receiving email and iMessage via Inkbox
  • 2026-07-07Public launch on Y Combinator's Launch platform
  • 2026-06-09GitHub SDK repo shows roughly 10 stars; repo documents full product feature set
  • 2026-05-26Inkbox GitHub organization page shows repo activity
  • 2026-04-22Added iMessage support to Python SDK, TypeScript SDK, and CLI
  • 2025Inkbox founded by Ray Liao, Alex Wilcox, and Dima Vremenko
Revision history
26 July 2026
First assessed. Protection under test. The text above is fixed as of this date and is not edited afterwards.
In the same band
Sources