Advisory scenarios and corridor case studies from Post Oak Labs, client-side, zero PII, AP2-exportable, MCP-native. The full tool library (500+ tools, 300+ chains) lives at AINumbers.co. Start with a hub below, then engage Post Oak Labs for the advisory layer.
Each hub is an advisory landing page for one buyer archetype, scoped to the problems Post Oak Labs advises on, with links into the relevant AINumbers tools and chains.
Advisory on deploying agentic payment infrastructure: AP2/MCP policy layer, mandate governance, runtime integration.
Explore hub → RegTech Five enforcement clocks, one schemaDORA, NIS2, MiCA, EU AI Act, CFPB §1033, advisory on compliance programme design with dual- and triple-regime overlap.
Explore hub → BaaS Sponsor-bank readiness, embedded finance advisoryProvider selection, embedded-lending unit economics, BIN sponsorship, programme agreements, wallet float yield.
Explore hub → Processors Card economics, A2A migration, ISO cutover14 Nov 2026 CBPR+ structured-address deadline, FCA DPC, FX netting, real-time fraud at FedNow speed, advisory and gap analysis.
Explore hub → Stablecoin Issuer Issuer-grade readiness advisoryMiCA Title III / GENIUS Act readiness, FATF R.16 Travel Rule, tokenized RWA, reserve architecture and regulatory positioning.
Explore hub →USD-pegged wholesale stablecoin bridge across a thin-correspondent, 3-hour UTC overlap corridor. Architecture analysis (CBDC vs stablecoin vs nostro), collateral sizing, ISO 20022 ledger schema.
Case StudyCBDC and stablecoin settlement across West Africa, Nigeria eNaira/cNGN, Ghana e-Cedi, Senegal/BCEAO (WAEMU). Settlement economics vs correspondent banking, FATF compliance overlay.
A set of advisory scenarios and corridor case studies drawn from Post Oak Labs practice and the AINumbers.co tool library. Every page runs entirely client-side, stores zero PII, exports Policy Mandate v1 mandates, and is discoverable over MCP.
Yes. All scenarios are free and open-licensed under CC BY 4.0. They are entirely client-side: no data leaves your browser and no PII is collected or transmitted.
AP2 is Google's Agent Payments Protocol (v0.2.0), a standard for expressing payment policies that AI agents can execute. Each scenario exports its result as a Policy Mandate (schema: @postoaklabs.com/policy-mandate-v1) so the output can be consumed by AP2-capable agents, replayed by an agent runtime, or reviewed by an audit team.
MCP (Model Context Protocol) is an open standard for exposing tools to large language models. The AINumbers tool catalog is MCP-native, so models such as Claude can call the tools directly and receive Policy Mandates in response.
Across the catalog the scenarios cover DORA, NIS2, MiCA, the EU AI Act, CFPB §1033, FATF Recommendation 16 (Travel Rule), Basel III/IV, BIS 239, FCA DPC, ISO 20022 / CBPR+ (14 November 2026 structured-address deadline; MT/MX coexistence ended 22 November 2025), and the US GENIUS Act.
They are built by Post Oak Labs, a firm specializing in tokenized payment infrastructure with advisory on production deployments across frontier markets. Explore the full AINumbers tool catalog at ainumbers.co, or browse by buyer archetype through the five hubs.
Behind every tool is a team that has built and integrated production tokenized payment systems. If one maps to a problem you are facing, let us talk.
Talk to our team →