> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sumvin.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Examples

> Worked Stamped Mandates for each use case: what you ask, what the mandate says, and what a verifier sees.

Each example starts with what you ask your agent, then shows the mandate written in the [mandate language](/concepts/mandates/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](/concepts/mandates/use-cases) for the status of each.

## Buy within a ceiling

<Badge>Private preview</Badge>

**You ask:** "Buy a pair of running shoes this week, up to $50, but only if they're $45 or less."

| Part       | Value                                                       |
| ---------- | ----------------------------------------------------------- |
| Scopes     | `sr:us:pint:spend:visa_checkout?max=50.00&currency=USD`     |
| Resources  | `sr:us:errand:{errand id}`                                  |
| Conditions | `sr:us:condition:price_target?op=lte&value=45&currency=USD` |
| Expiry     | Seven days from signing                                     |

* 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:

```text theme={null}
Purchase proceeds only while all of the following hold:
- the price is at most 45 USD
```

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."

| Part      | Value                                                   |
| --------- | ------------------------------------------------------- |
| Scopes    | `sr:us:pint:spend:visa_checkout?max=50.00&currency=USD` |
| Resources | None                                                    |
| Expiry    | Seven days from signing                                 |

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](/concepts/mandates/limits#narrowing-one-mandate-into-a-smaller-one).

## Share that you are verified

<Badge>Private preview</Badge>

**You ask:** "Tell the wine shop I'm over 18 so I can check out."

| Part     | Value                          |
| -------- | ------------------------------ |
| Scopes   | `sr:us:pint:sigil:age_over_18` |
| Audience | `shop.example.com`             |
| Expiry   | One hour from signing          |

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

<Badge>Private preview</Badge>

**You ask:** "Look through my September transactions and tell me where my money went."

| Part   | Value                                                                                                    |
| ------ | -------------------------------------------------------------------------------------------------------- |
| Scopes | `sr:us:pint:accounts:read` <br /> `sr:us:pint:transactions:read?from_date=1788220800&to_date=1790812800` |
| Expiry | One day from signing                                                                                     |

* `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

<Badge>Private preview</Badge>

**You ask:** "Book a table for two at the steakhouse on Friday at 8."

| Part     | Value                                  |
| -------- | -------------------------------------- |
| Scopes   | `sr:us:pint:sigil:proof_of_personhood` |
| Audience | `reservations.example.com`             |
| Expiry   | One hour from signing                  |

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

<Columns cols={2}>
  <Card title="Stamp your first mandate" icon="stamp" href="/get-started/first/stamped-mandate">
    Ask, read, sign.
  </Card>

  <Card title="What a verifier checks" icon="shield-check" href="/concepts/mandates/verification">
    Read a mandate someone presents.
  </Card>
</Columns>