THE AUTHORITY LAYER FOR AI AGENTS

Let agents work.
Keep the keys.

Usery gives every agent its own identity and a precise operating boundary. Approve once, revoke instantly, and keep reusable credentials out of model context.

Passkey approvalsCross-agentRevocable grantsUSDC-ready design
Authority requestOpenCode Local

CREATE ISSUE

github.com/name/repository

Calls3 maximum
ExpiresIn 1 hour
CredentialNever shared
Exact scope. Immediate revocation.
One calm control planeClaudeOpenAI / CodexOpenCodeLocal agentsAny MCP client

HOW IT WORKS

Authority travels. Credentials do not.

01

Pair an agent

Every installation receives a separate proof key and identity. Compromise stays contained to that agent’s current authority.

02

Set the boundary

Choose the resource, action, limits, expiry, recipient, repository, or budget. Human approval signs the exact policy.

03

Let it operate

Usery checks every sensitive action, executes through an isolated provider worker, and returns a minimized receipt.

CALM BY DEFAULT

Not another dashboard demanding attention.

Set conservative permissions once. Usery interrupts only for exceptions, escalation, expiry, thresholds, or dangerous actions.

Agent-specific authority

Pause one agent without breaking the rest of your system.

Credential isolation

Agents receive outcomes and receipts, never reusable provider tokens.

Money boundaries

USDC policies can bind chain, asset, recipient, amount, cumulative budget, and time.

History you can trust

Inspect requested, approved, allowed, denied, failed, and revoked actions.

PRIVATE ALPHA

Your agents can ask. Only you can authorize.

Open Usery