Leave out
controllerWallet when the signed-in account from proofable_context should own the agent.
Ask:
Create or import an agent on my Proofable profile. Give it a separate spend account if it needs one. Set spend and action limits. Then confirm it is ready.To import, inspect a package, repo, or card with the agent import HTTP routes, then call
proofable_agent_create with the mapped fields.
Account options
Signed-in profile (default)
OmitagentWallet. The agent lives on your signed-in account. Identity is enough. Several agents on one account need agentId on every link and mount call.
Dedicated account
The private key stays in your wallet or secure runtime, and Proofable only ever receives the public address. Create the account there, then pass that address asagentWallet.
Bring an existing account
Pass an existingagentWallet. The agent account signs identity. The approving profile signs spend and action limits.
When the signed-in account does not control that key:
- Sign and submit the returned identity step with the agent key.
proofable_verifyreturns the identityqHash. - Repeat
proofable_agent_createwith the same arguments plusidentityQHashset to that value. The returned step carries this call asthenCall. - The approving account completes permissions in-session or through the returned hosted URL.
identityQHash is how the approving session finds it, and the permission is recorded only after the identity exists. proofable_agent_link accepts identityQHash for the same reason.
What each result means
Every non-validation result includespath and next_action.
sessionProgress.identityComplete, delegationRequired, and delegationComplete show which step is required and already saved. On payment_required, add credits and retry the same request.
Hosted callback
Use the SDK helper instead of assembling query strings:identityQHash, Hosted Verify requests only permissions. The callback receives the new permission qHash, agentId, and agentWallet. Keep the identity qHash from step 1.
Keep agent setup, login and gate checkout on separate URLs:
- Login:
intent=login&returnUrl=... - Gate checkout:
gateId=...&returnUrl=... - Agent setup:
getHostedAgentCreateUrl(...)
Billing
Billing follows the signer for each proof unless a validated sponsor or pay-per-call proof overrides it:- Agent identity: the agent account pays.
- Permissions (separate spend account only): the approving profile pays.
- Hosted completion: the signed-in account pays for the step it signs.
- Sponsor grant or pay-per-call: the validated sponsor/caller pays.
instructions, skills, services, expiry, spend cap, runtime policy, approval policy, and allowed/denied actions. See Agent identity and Agent delegation.