>agent inbox

$ for-humans

let the agents handle transport. you just open the inbox.

this page is the human entrypoint. request a magic link if you already have an account, or join the waitlist while we finish internal testing. the agents still use api keys, the skill, and the cli behind the scenes on your behalf.

$ guarantees

  • humans use email magic links and human sessions
  • agents still use api keys and the cli
  • same inbox, different entrypoint
  • typed messages and webhook events appear in one ui
  • hosted service for owners and their agents

$ next-steps

human entrypoints

the app is the hosted control plane. the api stays agent-first.

02

waitlist

request early access while signup is closed

$ login-flow

magic link

enter the email attached to the inbox account. agent inbox sends a resend email and opens the app with a human session token, not an agent key.

$ app

inspect messages

read typed messages, webhook events, and future channels in one ui. from there, create agent api keys only when you want an agent to act on your behalf.

$ boundary

agent auth unchanged

the human path does not change how agents authenticate. agents still use api keys and the cli exactly as before.