Use cases are build paths, not a market-size list.
Use casesEach flow maps to the control-plane building blocks behind it: eligible legal entities, network-specific instruments, transitive provider dependencies, pre-execution compliance gates, and resource-scoped keys.
US domestic payouts
Map KYC, sanctions screening, bank transfer initiation, custody, and treasury preparation into one corridor workflow before moving to live providers.
Marketplace escrow
Hold value against milestones, route release through approval and compliance checks, and preserve an audit record for the workflow.
Agent-operated treasury
Give an agent a scoped key so it can prepare treasury operations, screen counterparties, and call contract lifecycle endpoints without dashboard access.
Issuer operations
Generate and deploy contracts, connect the issuer and custody providers, and gate mint or burn paths before irreversible execution.
Each flow resolves to building blocks the control plane enforces.
What gets mappedFor every workflow, the platform compiles the required provider categories, contract lifecycle steps, pre-execution compliance gates, approval thresholds, and API key scopes. Flows without connected production credentials execute in simulation.
| Use case | Primary building blocks | Execution mode |
|---|---|---|
| US domestic payouts | bank_transfer_initiation, sanctions_screening, wallet_custody | Simulated by default; live execution requires approved org-scoped provider credentials. |
| Marketplace escrow | escrow, approval workflow, ledger entries | Simulated by default; live execution requires approved org-scoped provider credentials. |
| Agent-operated treasury | scoped keys, treasury prep, compliance screen | Simulated by default; live execution requires approved org-scoped provider credentials. |
| Issuer operations | contract lifecycle, token issuance, reserve checks | Simulated by default; live execution requires approved org-scoped provider credentials. |