Skip to main content

Create an agent with owner approval

When an agent has its own account, it signs its identity first. Then send the owner to Proofable to approve permissions:
With identityQHash, Proofable asks the owner only for permissions. The callback receives the permission proof ID, agentId, and agentWallet. Keep agent setup on its own URL. Do not combine it with gateId or intent: 'login'. For an agent on the owner’s own profile, ask Proofable over MCP instead: proofable_agent_create.

Sign identity and permissions directly

For server-side or custom signing, create the two proofs with client.verify:
Every field is in Agent identity and Agent permissions.

Set a spend cap

Your application checks the cap before it signs each payment.

Check an action before it runs

The deny list applies first, then the allow list, then approval. The SDK evaluates one action. Your host owns the tool call and must stop it when allowed is false.

Load the permission bundle

Load agent context covers where each host picks the bundle up.
Last modified on September 12, 2026