Inkbox gives AI agents a persistent identity with a real inbox, phone number, and a public tunnel URL, backed by org-wide contacts, notes, and a secure vault that you can scope to specific agents. Your agents can communicate with people, receive inbound traffic, and manage shared context and credentials as a single, consistent entity.

Inkbox is an identity and communication layer for AI agents. Instead of treating email, phone, public reachability, and shared state as separate APIs, Inkbox models them as capabilities around a single agent identity, with org-level resources you can scope to the specific agents that should view or edit them.

Each identity owns exactly one mailbox and one tunnel; both are provisioned atomically when you create the identity, and torn down when you delete it. A phone number is optional and can be attached separately. Handles are globally unique.

Per agent — its own communication channels:

• An identity: a globally unique handle and the persistent record your agent acts under
• A real email address: send and receive email, manage threads, search inboxes
• A public tunnel URL: stable my-agent.inkboxwire.com that routes inbound HTTP, WebSocket, and raw-TCP traffic to your agent over a single persistent connection. No public IP or firewall hole needed
• A real phone number (optional): make and receive calls with real-time audio streaming, plus SMS/MMS
• Filtering: whitelist and blacklist rules on each mailbox and phone number

Org-wide, scopable to specific agents:

• Contacts: an address book of people and companies
• Notes: free-form shared context your agents can read and write
• Vault: zero-knowledge encrypted credentials, API keys, SSH keys, and TOTP secrets — Inkbox never sees the plaintext

Each of these three lives at the organization level; you grant view/edit access to the agents that should use them.

Each agent identity owns its mailbox, tunnel, and (optionally) phone number, plus its conversation history. Contacts, notes, and vault entries live at the organization level, and you scope each one to the set of agents that should view or edit it.

Organization
├── Contacts           →  address book, scoped per agent
├── Notes              →  shared context, scoped per agent
├── Vault              →  zero-knowledge credentials, scoped per agent
└── Agent identity
    ├── Mailbox        →  send/receive email, threads, filters
    ├── Tunnel         →  public URL, inbound HTTP/WS/TCP routing
    └── Phone number   →  optional; calls, SMS/MMS, real-time audio, filters

Conversations persist across channels, so your agent can follow up over email after a call (or vice versa) with full context.

Channels are first-class resources:

• Each mailbox has its own address (agent@inkboxmail.com)
• Each tunnel is reachable at a stable subdomain (e.g. my-agent.inkboxwire.com)
• Each phone number is a real PSTN number your agent can call from or receive calls on

Inkbox is designed for AI agents (and the developers building them) that need to communicate with real people: customer support assistants, outbound sales agents, automated phone operators, and any agent that needs a durable identity to follow up over time.

• Follow the Quickstart to send your first email and place your first call in minutes.
• Set up Agent signup to let agents self-provision without a pre-existing account.
• Install the Inkbox skill to teach your coding assistant the SDK.
• Browse the API Reference to see every endpoint in detail.