Learn the control plane before you wire a provider.
These 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
AI operator playbooks for managing providers, regimes, compliance gates, scoped keys, and agentic commerce workflows.
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 primitives.
The public guides should answer build decisions, not chase generic SEO.
If a topic does not help a builder understand provider eligibility, control-plane behavior, or readiness state, it stays out of the public guide set for now.
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.
Each guide is intentionally narrow. When a claim needs live market data or a commercial commitment, the page avoids making that claim.
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 primitives.
No market-data rankings
The public guides do not publish hardcoded market caps, APYs, or rankings without an owned refresh process.
No live-provider overclaims
Simulation paths are labeled as simulation. Live third-party provider rollout stays framed as corridor work.
No generic explainers
Generic stablecoin education is trimmed unless it helps a builder make a control-plane decision.