Skip to main content

​
Capability status

Lupin exposes several products through a shared workspace identity, scoped keys, quotas and usage controls. Availability belongs to the connected deployment and workspace, so check /v0/capabilities and the resource response before announcing that an operation can run.

​
Implemented interfaces

A new autonomous registration is not a claim that all these products are enabled. It starts with bounded email reception/reading and drafts, with outgoing mail and paid resources disabled.

​
Future work and explicit boundaries

Virtual cards are not an available product. Browser cross-session profiles and custom proxy routing are not exposed as supported browser-session controls. A listed app may still require operator setup or user authorization; discovery distinguishes configured from unavailable apps. Human accounts, agent workspaces and external provider accounts are separate. Creating an agent cannot consent to another person’s OAuth grant, payment, phone call or email send. See registration, Connections, billing and client coverage.