Start

Introduction

One integration that lets your agents transact, inside limits you set, with a record anyone can check.

What this does

Your agent decides it needs something and asks to pay for it. Before any money moves, we answer five questions: who is asking, what they are allowed to do, what is being bought, for how much, and how this seller wants to be paid. Then we answer a sixth one afterwards, which is what happened, in a form somebody who does not trust us can check.

You get one answer back: yes, ask a person, or no. Under that single answer sit every standard worth connecting to, and you never choose between them.

The shape of it

resolve, pay, verify and disclose are the whole write surface.
One decision point. Your agent never holds the thing that moves money, and cannot approve itself.
Limits live outside the agent. They are set once, they narrow when work is handed on, and nothing the agent says can widen them.
Every decision is recorded, including the refusals, which are usually the ones worth reading.

Everything here

The whole surface in one screen. Start at the top if you want something working; start at Concepts if you want to understand what you are agreeing to first.

Start

QuickstartA first payment, from nothing to a receipt.AuthenticationTwo credentials, deliberately separate.

Core

ConceptsTerms, intents, mandates, decisions, receipts.The verbsresolve, pay, verify, disclose.DecisionsAllow, confirm, deny, and what each means for your code.LimitsWhat you set, where it is enforced, how it narrows.RailsHow the money actually moves.RecordsReading the record, and checking it without us.

Capabilities

DelegationHanding authority on, and why it can only narrow.ApprovalsThe human step, and whether it means anything.Payment modesHolds, metering, splits, all-or-nothing sets.Counterparty termsTheir signed price, checked against your limits.CommerceBuying, as distinct from paying.DiscoveryReading what a seller publishes, graded as self-reported.Merchant policyThe seller's half of the decision, and it only narrows.AttributionWho the purchase came from, signed rather than asserted.Identity graphJoining identity slices without inventing certainty.DeliveryPaid and received nothing, and what stands behind it.Dispute evidenceThe file a dispute desk reads, and when not to send it.RevocationTaking authority back, and having time to.VerificationIdentity, transparency and coherence, kept separate.GovernanceEverything between deciding and settling.EconomicsWhat the money was, and whether it was really allowed.MemoryVerifiable, two-clock, and able to forget.AssuranceHow we try to find out we are wrong first.

Protocols

BindingsWhere protocol names may appear, and the rules they follow.

Clients

SDKsTypeScript, Python, Go, Rust.CLIFor operators: approve, refund, audit, stop.MCPThe write surface, exposed to an agent.

Operating

Running itEnvironments, storage, retries, tracing, self-hosting.ThroughputWhat was measured, and what the numbers do not support.WebhooksSigned events, derived from the record itself.API referenceEvery endpoint, who may call it, what comes back.ErrorsProblem documents, and which ones you should retry.ArchitectureWhat the platform is made of, package by package.