ActorTokenRuntimeCapability exposes ActorTokenApi under platform.actor-token. It mints a short-lived bearer token representing the current authorized actor for a specific outbound audience.
Use this capability when trusted server-side plugin code must call a host or connected service that accepts a host-issued actor token. It is not a long-lived plugin credential and must not be exposed to an iframe, Agent message, tool result, log, or persisted plugin record.
API
audienceidentifies the intended receiving service or services.ttlSecondsrequests the required lifetime for the outbound operation.actcarries bounded scalar actor context required by the receiving contract.
Example
Bind a token API outside middleware
The platform registry exposesActorTokenRuntimeFactoryCapability (platform.actor-token.factory), not a shared token operation API. Call createScopedApi(authorizedScope) per request/job after restoring and authorizing identity. The factory captures host-defined act claims and isolates its token cache.
Per-call act adds metadata but cannot override fixed host claims. Never accept delegated identity from a form or tool argument, or reuse a scoped API across callers. See Runtime Capabilities.
Security rules
- Resolve and use tokens only in trusted server-side code.
- Never put
tokenin queue payloads, URLs, browser messages, exceptions, logs, analytics, or database columns. - Do not cache or reuse the token beyond
expiresAt; mint a new token for a later job. - Keep
actsmall and machine-readable. Do not include credentials, large objects, or user-authored prose. - The receiving service must still authorize the requested operation. A minted token does not grant capabilities beyond the host’s current actor and audience policy.