Skip to main content

​
Channel roadmap

Lupin is one identity per agent, many channels. Email proves the pattern: scoped keys, allow/block lists, webhooks, usage, projects per tenant. Every new channel reuses it.

​
Next up

  • Phone — DIDs + SMS/voice behind a provider abstraction shaped like today’s MailProvider (log → real carrier). Number webhooks mirror email.received.
  • Cards — virtual cards per agent with spend limits; spend.authorized events next to email.sent.
  • Containers — sandboxed execution bound to the agent identity that already owns the inbox.
  • Browsers — persistent profiles and consents. The footing exists: browser enrollments, credentials and lifecycle events already live under /v0/api-keys/browser-credentials…, and AgentID public keys under /v0/api-keys/public-keys….
Channel(kind) in packages/db is the console-side registry; the data plane adds one namespace per channel the way projects did for tenants.