What we build

Bring the use case. The foundations are already there.

A person is verified, a mandate is stamped, an agent acts inside it, money settles, and the whole thing stays provable. Sumvin is the platform that makes that run possible. Sibylline is the studio that builds your part of it with you.

Bring us the use case How we deploy
What Sumvin is, in Sumvin’s words

One run, five steps

  1. Verify the personSigil
  2. Stamp the mandateErrand
  3. Agent actsEnvoy
  4. Money settlesAtomic Money
  5. Stays provableaudit trail

Every engagement below is a span of this. Each step names the primitive that does the work and links to its own page — SDKs and quickstarts live at sumvin.com/developers.

The whole platform map

Four shapes of work

One run. Four places to stand in it.

Two of these consume the same primitives and are nothing like each other — one stamps mandates for its own users, the other checks mandates it did not issue. Where you stand is what decides the build.

Every quickstart, by where you start

01 — Enterprise, internal

Agentic finance tooling, inside the business

You issue the mandates · you are here for agent acts.

How agent flows work

Agents that act on the company's own money and data — procurement, treasury operations, reconciliation, vendor spend — with authority that is scoped per run and an audit trail a regulator can read.

  1. Verify the personSigil
  2. Stamp the mandateErrand
  3. Agent actsEnvoy
  4. Money settlesAtomic Money
  5. Stays provableaudit trail
  • Errand-bounded spend authority per team, per budget, per run
  • Envoy agents against the systems already in place, not a greenfield replacement
  • Settlement through Atomic Money rather than a new banking relationship

02 — Product and platform teams

Productised agentic finance, for your customers

Your users issue the mandates · you are here for verify the person.

Building on Sumvin

A consumer or business product where the agent transacts on the user's behalf. The identity, authorization and settlement layers arrive built, so the work is the product rather than the plumbing beneath it.

  1. Verify the personSigil
  2. Stamp the mandateErrand
  3. Agent actsEnvoy
  4. Money settlesAtomic Money
  5. Stays provableaudit trail
  • Sigil onboarding — verify once, reusable across everything you ship
  • Issued cards and ramps under your own brand
  • Mandates a user can see, scope and revoke

03 — Merchants and marketplaces

Agent-native commerce

You check mandates you did not issue · you are here for money settles.

The merchant side

Accepting demand that arrives from software rather than a browser session. Every transaction traces back to a verified person holding a signed mandate, which is what makes agent traffic bankable instead of a fraud problem.

  1. Verify the personSigil
  2. Check the mandateErrand
  3. Agent buysEnvoy
  4. Money settlesAtomic Money
  5. Stays provableaudit trail
  • x402 and payment links as a machine-payable surface
  • Visa Intelligent Commerce acceptance alongside direct stablecoin settlement
  • Personhood and mandate checks at the point of sale

04 — Regulated and high-assurance

Delegated spend with proof

The whole chain is the deliverable · you are here for stays provable.

Trust and assurance

Where the question is not whether an agent can pay but whether you can prove afterwards that it was allowed to. Authority, identity and settlement are one chain of evidence rather than three systems to correlate under audit.

  1. Verify the personSigil
  2. Stamp the mandateErrand
  3. Agent actsEnvoy
  4. Money settlesAtomic Money
  5. Stays provableaudit trail
  • Cryptographic provenance from person to mandate to payment
  • Deployment inside your own cloud and identity boundary, on Atlas
  • Evaluation harnesses so agent behaviour is measured, not assumed

What happens next

Know where you stand in the run, or want to work that out?

Bring us the use case. We will tell you what it takes on the stack — and then build it with you, on your team.

Start a conversation Read the docs