Skip to main content
You’re building flows where an AI agent takes actions on behalf of a user — searching, selecting, purchasing — inside a capability envelope the user pre-signed. Your integration touches three Sumvin surfaces in sequence: IPAs for orchestration, s for authorisation, and agent signers for cryptographic identity.

​
How the pieces fit

  • IPAs (Intelligent Purchase Authorisations) are the orchestration layer. An IPA represents the agent’s task and its state over time — preflight, execute, completion.
  • PINTs with sr:us:pint:spend:execute are the authorisation layer. The user signs a PINT declaring the cap, duration, and scope of what the agent may do; the agent acts only within that envelope.
  • P-256 agent signers are the identity layer. Each user has a per-user agent signer — the cryptographic key the agent uses to sign transactions on their behalf.
An action flows from IPA → user-signed PINT → agent-signed transaction → merchant verification at checkout.

​
Start here

Read in this order:
  1. IPA guide — the lifecycle of an agent task, end-to-end.
  2. Scopes reference — the capability envelope, with sr:us:pint:spend:execute as the spend scope.
  3. Agent signers — the per-user P-256 key the agent uses to act.
  4. IPA lifecycle — the state machine diagram with every transition.

​
Scope and tier for an agent-initiated action

The scope carried by a PINT determines which verification tier applies at checkout. sr:us:pint:spend:execute is the only Enhanced-tier scope today, and it is the scope an agent-initiated purchase carries. Merchants accepting it must verify both the JWT and the underlying EIP-712 signature. See verification tiers for the full breakdown.

​
Next up

Read the IPA guide for the orchestration layer, then the scopes reference to decide what the agent may do, then agent signers for the cryptographic key that does the signing. Verification tiers is the merchant-side picture — the shape your PINT meets at the checkout boundary. An agent isn’t trusted because it’s an agent. It’s trusted because the envelope it acts inside was pre-signed by the user.