Free, browser-based workflows for teams building on Tempo, the payments-first L1 from Stripe and Paradigm (mainnet live March 18, 2026). Each one handles a specific job: sizing the business case for moving payment volume onto Tempo, checking a stablecoin issuance plan against the GENIUS Act and MiCA, screening TIP-20 transfers for sanctions and Travel Rule obligations, or setting spend controls for an MPP agent. Everything runs locally in your browser. There is no backend, no signup, and no data leaves your machine. Every result carries a hash, so a counterparty can rerun the same workflow on the same inputs and confirm they get the same answer.
Written for compliance, payments, and treasury teams, and for engineers at companies evaluating Tempo: stablecoin issuers, PSPs, merchants preparing for agentic checkout, and prospective validator operators. This is an independent project by Post Oak Labs, not a Tempo product.
Tempo is a payments-first layer-1 blockchain designed to make programmable money work for real-world financial institutions. Mainnet launched March 18, 2026, backed by Stripe and Paradigm. The network is built around four core primitives: TIP-20 (the token standard), TIP-403 (the policy layer), MPP (the machine payment protocol), and Zones (private permissioned parallel chains launched June 2026).
TIP-20 defines the Tempo token standard: 32-byte memo fields for payment metadata, immutable currency code (USD), supply caps, and RBAC-controlled mint/burn/freeze authority. TIP-403 adds token-level whitelist, blacklist, and freeze controls that propagate across zones, which is what makes compliant stablecoin issuance and on-chain AML enforcement possible. MPP (Machine Payment Protocol) is the OAuth-for-money layer: AI agents use HTTP 402 + MPP session tokens to pay for services, live since March 2026. Zones (June 2026) are private permissioned parallel chains where operators see all transactions, users see only their own, and outsiders see only ZK validity proofs. That combination supports payroll, treasury, and institutional settlement without giving up AML surveillance.
Each workflow covers a distinct Tempo use case. If you are not sure which ones apply to you, run the fit diagnostic first; it recommends an order. The validator readiness scorer stands alone, for organizations weighing whether to run a node.
Tempo stablecoin issuers, VASPs, and operators face a dual-regime compliance landscape. The workflows above stick to the regulatory sources cited below and do not go beyond them.
Every tool on this page emits an OpenChainGraph artifact with the following properties, consistent across ART-34 through ART-41 and CRY-01.
chaingraph_version: "0.4.0" in their §4 artifact payload, so consuming systems can verify schema compatibility before ingesting the artifact.
dct:conformsTo URI per W3C PROF, enabling linked-data consumers to validate artifact content against the declared OpenChainGraph profile without reading the full artifact body.
did:key agent identity for the executing agent's DID and the delegation chain from human principal to sub-agent. The did:key is embedded in the ART-36 session mandate and carried through ART-04's KYA attestation.
execution_hash that covers node inputs, processing parameters, and outputs. Bilateral verification: either party in a bilateral workflow can re-run verify_execution_hash against the hash to confirm the node was run as claimed, without sharing internal policy or configuration.