An application is the isolation boundary. A credential, connection, workflow, operation, invocation receipt, credit reservation, and purchase belongs to exactly one application.
Roles
| Role | Read | Configure and invoke | Manage members and owner-only billing |
|---|---|---|---|
OWNER |
Yes | Yes | Yes |
DEVELOPER |
Yes | Yes | No |
VIEWER |
Yes | No | No |
Downgrading or removing a member revokes that member’s Agent keys. Inaccessible applications return 404 so callers cannot enumerate application IDs.
Why this boundary exists
Agents need narrower authority than the people who configure them. Application-scoped keys and operation discovery make the authority visible and revocable without exposing workspace-wide orchestration APIs.
Boundaries
- An application does not make a disabled or unconfigured operation callable.
- A credential value is write-only and never returned by a later read.
- A receipt from one application cannot be used to retrieve another application’s result.
- Platform-operator and internal runtime APIs are separate from application membership.