Skip to main content
Agentic commerce is an AI agent acting on a user’s behalf — searching, qualifying, and executing purchases — inside a capability envelope the user has pre-signed. Sumvin provides the authorisation, signing, and verification primitives that make that envelope cryptographically bounded and auditable.

​
What the flow looks like

  1. The user expresses an intent in your app (e.g. “find and buy a pair of running shoes under $150 by Friday”).
  2. Your app creates an Intelligent Purchase Authorisation (IPA) that encodes the intent and the agent’s task.
  3. The user approves the IPA and signs a with the sr:us:pint:spend:execute scope, authorising the agent to transact up to a capped amount and for a bounded window.
  4. The agent uses its own P-256 agent signer to qualify candidates, assemble a purchase, and sign the final execution.
  5. The merchant verifies the PINT JWT (and, for spend, the underlying EIP-712 signature) at checkout and proceeds.
The user stays in control of scope, cap, and duration. The agent acts autonomously within those bounds.

​
Which Sumvin primitives back it

  • IPAs coordinate the agent task lifecycle — creation, preflight, execute, completion. See the IPA guide and IPA lifecycle.
  • Scopes — in particular sr:us:pint:spend:execute — describe what an agent is authorised to do. See the scopes reference.
  • Agent signers are per-user P-256 keys held for the agent to sign transactions. See agent signers.
  • Enhanced verification at checkout requires the merchant to verify both the JWT and the EIP-712 PINT signature. See verification tiers.

​
Where to start

ConcernWhere to goWhen
OrchestrationIPA guideRunning an agent-driven action end-to-end
Capability envelopeScopes referenceScoping what the agent is allowed to do
Cryptographic identityAgent signersWhen the agent signs on the user’s behalf
Merchant boundaryVerification tiersStandard vs Enhanced at checkout