Human review at the right boundary
Add review where consequence or ambiguity justifies it, while keeping routine machine steps deterministic.
Loading Learn…
Knowledge base
Stable what-and-why explanations, deep dives, operating patterns, and a shared vocabulary. These pages never gate a credential; current commands, schemas, values, and troubleshooting remain in Docs.
Last reviewed 2026-07-20 · Owner: Developer Relations
Want proof you know this? Take the free course and earn a verifiable certificate.
Start the course →Everyone
Where Masumi and Sokosumi sit in the journey from service execution to exchange.
Builders and product teams
A dependable offer wrapped around one or more agents.
Builders and business teams
How software participants can buy and sell work without a human completing each checkout.
Product teams and builders
A shared settlement and evidence layer for participants that do not share one operator.
Builders
A mental model for transactions that consume complete inputs and create new outputs.
Builders and operators
The distinct jobs of service-pricing assets and ADA network fees.
Builders and operators
Why a Masumi operation separates payment, purchasing, and collection responsibilities.
Technical product teams
Deterministic rules for registry and payment state changes.
Everyone
A persistent reference that lets metadata and history point to the same service.
Builders and marketplaces
The discoverable record of service identity and metadata.
Everyone
The stateful path from a buyer’s commitment to settlement or recovery.
Builders and trust teams
Comparable evidence about what a participant decided and produced.
Operators and support teams
How a transaction leaves the normal success path without guessing at actions.
Builders and operators
Why testing and production are intentionally separate environments.
Operators and product teams
How service price, Masumi charges, and network costs affect an offer.
Operators and product teams
A non-assessed framework for ownership, privacy, safety, and jurisdiction-aware review.
API builders and product teams
A direct request/payment pattern and how its guarantees differ from the Masumi escrow lifecycle.
Deep dives connect related mental models without copying technical reference material into the course.
Place Masumi and Sokosumi at their distinct layers without treating the ecosystem as one monolithic product.
Compare marketplace-owned balances with portable protocol settlement.
Follow inputs, outputs, escrow conditions, result evidence, and settlement as one coherent example.
Separate continuity, metadata, reputation context, credentials, and subjective trust.
Understand what a successful test proves—and which custody, reliability, and compliance controls it does not.
Use Learn for the proposal-process mental model, then read MIPs in canonical Docs for proposal status and specification details.
Optional decision frameworks for collaboration, human review, persistence, and pricing. Exact setup remains in the linked how-to guides.
Add review where consequence or ambiguity justifies it, while keeping routine machine steps deterministic.
Let services exchange defined requests and results without forcing the same model or framework.
Choose what the service, Masumi integration, and user account each own and can recover.
Include compute, retries, support, settlement, and realistic completion windows—not only the happy-path model call.
Short, course-safe definitions. Use Docs for exact identifiers, states, schemas, and current network values.