Learn the control plane before you wire a provider.
LearnThese guides explain the decisions that matter in this product: provider eligibility, asset and regime fit, scoped API keys, simulation boundaries, and compliance gates.
Stablecoin University
Operator playbooks for scoped authority, provider readiness, compliance gates, and simulation before an agent requests a payout.
Control-plane FAQ
Plain answers on what is shipped, what runs in simulation, who owns the contracts, and how provider selection works.
Choose an asset by regime
A stablecoin choice changes provider eligibility, reserve posture, and corridor design. Start there, not with market-cap rankings.
Use cases with build paths
A short operator view of payouts, escrow, treasury, and agent-operated flows mapped to platform building blocks.
Built around real architecture and procurement decisions.
Start hereEvery guide maps directly to a decision in the control plane: legal-entity and instrument eligibility, transitive provider dependencies, scoped API authority, and pre-execution compliance gates.
Provider selection is the wedge.
The platform models operational categories such as sanctions screening and bank transfer initiation, then evaluates fit against jurisdiction, corridor, asset, and license context.
Readiness is explicit.
Directory, credential storage, scoped keys, and builtin adapter simulation exist today. Live KYC, banking, custody, and issuance depend on corridor provider rollout.
Compliance runs before execution.
Financial operations pass through a gate before the adapter executes. A block or escalation stops the path and leaves an audit record.
Use the guide that matches your next decision.
What to readEach guide focuses on one stage of evaluation: readiness boundaries, instrument and regime selection, or mapping a payment flow to control-plane building blocks.
Confirm what is live.
Start with the FAQ if you need the shipped, simulated, and roadmap boundary.
Pick the asset context.
Use the regime guide when asset, corridor, or reserve posture changes provider eligibility.
Map the build path.
Use the use-case guide when you need to map a product flow to platform building blocks.
Sourced market data only
Market snapshots carry their primary source and retrieval timestamp. We never publish unverified APYs or static rankings.
Explicit readiness levels
Directory research (L1), credentialed health checks (L2), and adapter execution (L3) are distinct. Simulation paths are always labeled.
Operator-first depth
Every guide connects regulatory regimes, instrument deployments, and supplier dependencies directly to runtime controls.