Skip to main content
Sumvin is the orchestration layer for identity-anchored agentic money. Partners build on four products — for verified identity, for agent tasking, the money agent, and for payments — choosing one or more to compose their own agentic finance or commerce flow. Every product ties back to the same portable, -verified identity, so any action an agent takes on a user’s behalf traces directly to a real, verified person.

​
Why this exists

Every consumer finance or commerce product has to solve the same problems before it can ship: verify users, hold funds, authorise actions (including actions taken by AI agents on a user’s behalf), and accept those authorisations at the point of sale. Today, each product rebuilds that plumbing in isolation, which means every partner pays the same KYC, wallet, and agent-authorisation cost, and every user re-verifies the same identity across silos. Sumvin is that plumbing as a shared layer, split across our four products: Sigil verifies identity once, Envoy holds and moves funds, Errand authorises what an agent is allowed to do, and Atomic Money accepts those authorisations at the point of sale. A user verifies once, holds a portable identity through Sigil, and signs s — signed, time-bound permissions — that travel with their requests wherever they go. Partners either build on that identity through the Platform API, or accept it through the Verifier surface — without having to own the identity substrate themselves.

​
The products

Four products sit on top of one identity:
  • Sigil — portable, KYC-verified identity (“Proof of Personhood”). A user verifies once and carries it across every product.
  • Errand — an agent’s scope-bound tasking run: Intent → Authorization → Vigilance. Lets an agent execute purchases on a user’s behalf within limits they set.
  • Envoy — the money agent itself, executing Errands against a user’s Stamped Mandates.
  • Atomic Money — the payments umbrella: ramps, card issuing, x402, and payment links.
Product name → wire artifact. The product names below are how Sumvin is described. On the wire, the API, headers, scopes, and error codes are unchanged — keep using the technical identifiers in your code.SIS (the SIS API and SIS Dashboard) keeps its name.
You reach these products through the Platform API (build consumer apps), the SIS API (verify credentials at your boundary), or the SIS Dashboard (configure your organisation). See the Platform map to pick the surface you need.

​
Start with the SIS Dashboard

Almost every Sumvin integration begins in the SIS Dashboard. You create an organisation, add an environment, configure an auth provider, and mint the API key you need for server-to-server calls — all before you write any code. Work through the SIS Dashboard quickstart first. It ends with a live verifier call against the SIS API, proving your API key works. From there, pick the surface you are building on and follow its quickstart.

​
Where to go next

The identity is the plumbing. Everything built on top of it — apps, verifiers, agents — is what the plumbing makes possible.

SIS Dashboard quickstart

Set up your organisation and mint your first API key

Platform map

Pick the right surface for your integration

Quickstart index

Every quickstart grouped by persona

I'm an app developer

Start here if you’re building a consumer product on Sumvin

Verifier overview

Start here if you’re accepting Sumvin credentials