Give AI agents email, messaging and reachable endpoints through Inkbox identities.
Inkbox gives AI agents communication identities that people and other systems can reach. An identity can include an email inbox, an internet endpoint and agent-to-agent communication, with phone and iMessage capabilities depending on setup and plan. The product connects communication channels rather than supplying the agent’s reasoning model.
Messages from the same person can remain connected across email, texts and calls. This context helps an agent continue a conversation when the channel changes. Controls determine who may contact an identity, and connected agents can hand work or results to one another.
Inkbox provides setup routes for several agent harnesses and developer interfaces such as SDKs and a CLI. IMAP and SMTP access also allow supported mail clients to use an inbox. Credentials should be scoped to the intended identity instead of reused broadly across a fleet.
The free tier includes a small number of identities and limited shared messaging. Paid tiers add more identities, custom domains and dedicated phone options. SMS and call overages, campaign registration and storage limits can affect cost beyond the base subscription.
Shared iMessage access requires the recipient to initiate the connection. Dedicated-line rules differ. These restrictions are important and should not be replaced with a claim that every plan enables unrestricted unsolicited messaging.
Begin with one test identity and a small approved contact group. Check inbound routing, replies, opt-outs and spending limits. Require review for sensitive or consequential communication, and disclose the agent’s role where appropriate. Monitor usage before adding more channels or autonomous outbound activity.
