agent inbox

Agent-Native Infrastructure

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 one inbox without rebuilding it from prose every time.

Core 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
  • built for agents acting for owners
  • humans and agents operate the same system
join waitlistdocshuman uisee flows

How It Works

how it feels to use

The shape is real. These examples are intentionally masked so humans and agents can see the model without us pretending self-serve access is fully open yet.

01

install skill

keep the agent-first entrypoint visible

npx @agent-inbox/cli skill install
npx @agent-inbox/cli schema
open https://app.agent-inbox.***
02

check the api shape

show the request surface without exposing live credentials

curl -s https://api.agent-inbox.***/openapi.json

# session or api token
authorization: Bearer aix_[workspace_token]
03

send a typed message

move structured state instead of rebuilding it from prose

curl -s https://api.agent-inbox.***/v1/messages \
  -H 'authorization: Bearer aix_[workspace_token]' \
  -H 'content-type: application/json' \
  -d '{
    "recipient_account_id": "[target_account_id]",
    "schema_id": "task/result@v1",
    "thread_key": "job-1842",
    "metadata": { "status": "completed", "latency_ms": 284 },
    "parts": [
      {
        "kind": "inline_json",
        "name": "result",
        "content_type": "application/json",
        "value": { "summary": "done" }
      }
    ]
  }'
04

catch external traffic

let the inbox hold webhook traffic while your agent is offline

npx @agent-inbox/cli ingress create --json '{
  "channel": "webhook",
  "auth_mode": "bearer_secret",
  "enabled": true
}'

npx @agent-inbox/cli messages list --channel webhook

Efficiency

less token burn

keep payloads typed. keep attachments intact. stop wasting context window explaining state that could have just been delivered as data.

Reliability

fewer lost events

when transport is durable, the agent spends less time coordinating and more time finishing the job the user actually asked for.

Platform

built for agents

email, webhook inboxes, and sms all land in one system so agents can operate on behalf of their owners without a pile of extra transport code.

Launch Surface

  • agent cli and skill install
  • inbox, compose, and control plane
  • webhook ingress and replay
  • managed email and phone numbers

Early Access

tell us:
- who the user is
- which channels matter first
- what the agent should do
- what prompt or workflow you are already using
join waitlist