Skip to main content
Each example starts with what you ask your agent, then shows the mandate written in the mandate language. Hostnames use example.com, and identifiers are made up. Only the purchase example can be drafted by an agent today. The others show how the same language expresses use cases that are rolling out. See Use cases for the status of each.

​
Buy within a ceiling

Private preview You ask: “Buy a pair of running shoes this week, up to 50,butonlyifthey′re50, but only if they're 45 or less.”
  • The ceiling is $50.00, in dollars, not cents.
  • The mandate is bound to one errand. It can’t pay for anything else.
  • The condition is signed with the mandate. The purchase proceeds only while the price is at most $45.
The approval page puts the conditions in plain words, such as:
A verifier sees scopes sr:us:pint:spend:visa_checkout?max=50.00&currency=USD, a ceiling of 50.00 USD, and whether the mandate stands.

​
A standalone spending limit

You ask: “Set up a spending limit of $50 for groceries this week.” The approval page reads: “Authorise spending of up to 50.00 USD. This authorisation lapses on” followed by the date and time in UTC. One mandate like this can back several errands; each purchase draws a part of it as a smaller mandate.

​
Share that you are verified

Private preview You ask: “Tell the wine shop I’m over 18 so I can check out.” The shop learns one fact: a verified person over 18 stands behind this agent. It learns nothing else about you. To share your verification status instead, the scope is sr:us:pint:sigil:kyc_status. Sharing your full verified details with a provider uses sr:us:pint:sigil:kyc_read, with reason and requestor naming why and with whom. It can’t be addressed to a website by hostname; the provider must be one Sumvin knows.

​
Read a month of transactions

Private preview You ask: “Look through my September transactions and tell me where my money went.”
  • 1788220800 is 1 September 2026, 00:00 UTC, and 1790812800 is 1 October 2026, 00:00 UTC, both in Unix seconds.
  • The agent can read your linked accounts, and only transactions inside the range. A request for August is refused.
  • Linking a new account needs sr:us:pint:accounts:link?provider=meld as well.

​
Prove a person sent the agent

Private preview You ask: “Book a table for two at the steakhouse on Friday at 8.” The booking site receives a mandate addressed to it, in the x-sumvin-pint-token header of the agent’s request, that says a unique, verified person sent this agent. It checks the mandate on its own server; an online check that it still stands is coming soon. It doesn’t learn who you are. The same mandate can’t be used at another site, and it can’t carry any other kind of scope, such as spending, because it is addressed by hostname.

​
Next

Stamp your first mandate

Ask, read, sign.

What a verifier checks

Read a mandate someone presents.