Agent Capability Tokens
ACTs describe a bounded capability. An integration can limit which service and operation the token represents instead of distributing an unrestricted credential.
Scoped credentials for agents
Give access a smaller surface.
Arsenal provides scoped capability tokens and a credential proxy so agents can use external services without carrying the underlying long-lived secrets.
ArsenalIllustrated study
Defined scope / checked / bounded
A permission is a condition, not a blank cheque.
Arsenal
01 / Built for a purpose
Authorize the job, not the entire account.
An agent may need to call one API for one task. Arsenal separates that permission from the credential used to reach the service. Its capability and proxy model gives the integration a place to enforce scope, expiry, and request policy.
Credentials behind a proxy
The proxy handles the upstream credential on the agent’s behalf. The agent receives the capability it needs for the approved interaction.
Policy around outgoing requests
Request controls and destination checks belong at the proxy boundary. Approval requirements can be attached where an action needs human involvement.
A record of access
Audit records help connect a credentialed request to an identity and capability. Their presence complements, rather than replaces, monitoring and application policy.
The details matterGood questions.
Good questions.
Clear answers.
How does Arsenal relate to Sigil mandates?+
Arsenal controls access to external credentials and services. Mandates describe bounded on-chain delegation, with a separately documented activation state. They operate at different boundaries and should not be treated as interchangeable permissions.
Keep exploringOne capability.