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

# Platform map

> The four Sumvin products and the surfaces you reach them through.

Sumvin is four products sitting on one identity. You reach them through surfaces — the API and dashboard access points you build on or accept credentials at. This page lays out both layers and answers a single question: which surface do you need?

<Snippet file="product-term-disambiguation.mdx" />

## The products

The products are *what* Sumvin gives you. Each is anchored to a user's portable, KYC-verified identity.

<CardGroup cols={2}>
  <Card title="Sigil" icon="fingerprint" href="/identity/overview">
    Portable, KYC-verified identity — Proof of Personhood. A user verifies once and carries it across every product.
  </Card>

  <Card title="Errand" icon="route" href="/concepts/errands">
    An agent's scope-bound tasking run: Intent → Authorization → Vigilance. Lets an agent execute purchases on a user's behalf within set limits.
  </Card>

  <Card title="Envoy" icon="send" href="/overview/personas/agent-flows">
    The money agent itself — executing Errands against a user's Stamped Mandates.
  </Card>

  <Card title="Atomic Money" icon="coins" href="/products/atomic-money/overview">
    The payments umbrella: ramps, card issuing, x402, and payment links.
  </Card>
</CardGroup>

## The surfaces

The surfaces are *how* you reach the products — the access points you integrate against.

| Surface           | What it does                                                                                                                                                                                                                                                                                                                                                              | Who uses it                                                             | Entry page                                                                                                   |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Platform API**  | Creates users, manages wallets, runs onboarding and KYC, drives Errands, and issues Stamped Mandates.                                                                                                                                                                                                                                                                     | Partners building consumer apps on Sumvin.                              | [Platform API introduction](/introduction)                                                                   |
| **SIS API**       | Exchanges signed Stamped Mandates for verifiable JWTs, serves <Tooltip tip="JSON Web Key Set — the public-key document used to validate PINT JWTs." headline="JWKS" cta="Glossary →" href="/glossary">JWKS</Tooltip>, and reports revocation state. Used in two modes: partners building on Sumvin exchange tokens; verifiers accepting Sumvin credentials validate them. | App developers (token exchange) and merchants/verifiers (validation).   | [Identity overview](/identity/overview) for builders; [Verifier overview](/merchant/overview) for acceptors. |
| **SIS Dashboard** | Configures your organisation, environments, auth providers (Dynamic, Privy), CORS origins, API keys, and members.                                                                                                                                                                                                                                                         | Engineering teams operating a federated identity integration on Sumvin. | [SIS Dashboard introduction](/dashboard/introduction)                                                        |
| **Verifier**      | Accepts a Sumvin credential at your request boundary — checks the Stamped Mandate's JWT against the SIS JWKS and, for spend, the underlying EIP-712 signature.                                                                                                                                                                                                            | Merchants and services receiving Sumvin credentials.                    | [Verifier overview](/merchant/overview)                                                                      |

## How products and surfaces connect

App developers use the **Platform API** to bring a user online — creating the user's **Sigil**, wallet, and Safe smart account, and running them through onboarding and KYC. Once the user exists, they sign a **Stamped Mandate (PINT)** — an EIP-712 message declaring the scope of an authorised action. When an **Envoy** acts for the user, it signs on the user's behalf and carries out the work as an **Errand**.

The signed Stamped Mandate is exchanged with the **SIS API** for a JWT, which travels as `x-sumvin-pint-token` on outbound requests. At the **Verifier** surface, merchants receive that header, check the signature against the SIS JWKS, and — for enhanced-tier actions like spend execution — also verify the underlying EIP-712 signature.

App developers configure the integration through the **SIS Dashboard**: which auth provider SIS should trust for their users, which origins may call SIS from the browser, and which API keys grant server-to-server access. Each dashboard environment holds its own auth provider credentials and CORS origin list, so development, staging, and production stay isolated at the request-authentication and browser-origin boundary. API keys, by contrast, are [organisation-scoped](/dashboard/api-keys) — the same key authenticates server-to-server calls regardless of environment.

## Pick a surface

**The products are one identity in four shapes. The surfaces are how you reach them — they don't compete, they compose.**

<CardGroup cols={2}>
  <Card title="Platform API" icon="code" href="/introduction">
    Build a consumer app on Sumvin — users, wallets, Errands
  </Card>

  <Card title="Identity & Stamped Mandates" icon="file-pen" href="/identity/overview">
    Create Stamped Mandates and exchange them for JWTs
  </Card>

  <Card title="Verifier Guide" icon="shield-check" href="/merchant/overview">
    Accept Sumvin credentials at your request boundary
  </Card>

  <Card title="SIS Dashboard" icon="sliders-horizontal" href="/dashboard/introduction">
    Configure auth providers, API keys, and environments
  </Card>
</CardGroup>

## Atomic Money surfaces

Every Sumvin identity also ships payment primitives under **Atomic Money**. Both are Stamped Mandate-backed and x402-addressable:

* [**Payment request links**](/products/payment-links/payment-request-links) — ad-hoc, identity-anchored request URLs any x402 wallet or agent can settle.
* [**Global x402 acceptance**](/products/payment-links/global-x402-acceptance) — a persistent, SRI-resolvable acceptance endpoint on every identity.

## Related

* [Partner personas](/overview/personas/app-developer)
* [Quickstart index](/overview/quickstart-index)