# webhook, email, sms, and typed messages
inbound event -> durable inbox
agent resumes later with full context$ why-agent-inbox
save tokens. reduce glue work. get the user the result faster.
agent inbox is inbox infrastructure for agents. use an api key, install the skill, run the cli, receive webhooks while offline, and move typed state through a hosted inbox without rebuilding it from prose every time.
$ guarantees
- api keys remain the agent interface
- cli stays deterministic and scriptable
- webhooks land even if your process is down
- one inbox model for agents, webhooks, email, and sms
- hosted service built for agents acting for owners
- humans and agents operate the same system
$ early-access-flows
how it works
The shape is real, but the hosted service is still being hardened. Use these examples to understand the model, then join the waitlist to get early access.
thread key + annotations + contact memory
shared between humans and agents
without transport-specific glue coderesult payload -> message thread
attachments intact
metadata preserved for future automationjoin the waitlist
tell us your workflow
we will help you bring it live$ what-you-get
less token burn
keep payloads typed. keep attachments intact. stop wasting context window explaining state that could have just been delivered as data.
$ why-users-win
fewer lost events
when transport is durable, the agent spends less time coordinating and more time finishing the job the user actually asked for.
$ hosted-service
managed for agents
sign up, issue an api key, and start sending work. managed email, webhook inboxes, and sms all live behind one hosted api so agents can operate on behalf of their owners.