Every page on this site grouped by the job it does

An educational, hands-on tool for students and newcomers: click-to-compose a multi-step compliance workflow and watch parent_hash provenance wire up, then compare it to the legacy paper trail it replaces. It teaches the concept and does not execute. To run a chain for real, use the Workbench or Canvas. Client-side, zero-egress.

Edit an OCG v0.3 artifact live and watch the execution_hash recompute in your browser. Tamper with fields and see exactly why the fingerprint breaks. No server. Zero PII. WebCrypto SHA-256.

A source-cited wall of regulatory filing deadlines: Pillar Two GIR, DORA Register of Information, NYDFS certification, FFIEC Call Report, FR 2052a, FR Y-14, CTC e-invoicing, Fedwire, and Regulation CC. Filter by regime or jurisdiction and export to your calendar.

Browser-based fintech tools and MCP-callable, hash-anchored OpenChainGraph workflows for payments engineers and compliance teams. Zero PII. No install.

Author a checklist or SOP definition as a signed, hash-anchored OpenChainGraph document. Steps, evidence requirements, and blocking gates, exported client-side with zero PII.

Run a checklist or SOP definition step by step. Every completed step emits a hash-chained receipt; the finished run emits a Merkle-rooted run receipt, offline-verifiable.

Author an in-toto supply-chain layout in-browser: steps, artifact rules, authorized functionaries, threshold, inspections. DSSE-signed and exported client-side with zero PII.

Build a DSSE-signed in-toto link or in-toto attestation statement from drag-drop file hashing, and verify a layout against links offline in your browser.

Every AINumbers example prompt on one page: showcase, deep dives, everyday, and domain briefs with full copy-paste bodies, tool chips, verify surfaces, and the chain catalog one-liners. The same list the hosted worker serves via prompts/list.

Load two OpenChainGraph artifacts, chains, or §27.6 evidence bundles and get an OCG-semantic diff: which input hashes moved, which kernel/policy versions changed, which §27 approvals/roles/thresholds differ, and whether the verdict changed. Runs entirely in your browser.

Free, static, client-side checker that runs the applicable subset of the OpenChainGraph v0.4 SPEC.md §15 gate suite against a submitted artifact, entirely in your browser. No account, no submission stored, methodology public.

Verify the execution_hash of any OpenChainGraph v0.4 artifact. Client-side SHA-256 verification, no data leaves your browser.

Drop an OpenChainGraph artifact, chain, or §27.6 evidence bundle and get a section-by-section verification report: shape, hash, signature, compute proof, anchor timestamp, input attestations, and approval records. Runs entirely in your browser.

Drag any number of artifacts, chains, or evidence files and get a PBC-style index: filename, sha256, artifact type, section coverage detected, signer roles present, chain membership. Print view and a JSON export that is itself hash-anchored. Runs entirely in your browser.

Three sample checklist definitions covering permit-to-work operations, SOC 2 evidence collection, and stablecoin issuer disclosure prep. Load any of them straight into the Run Executor.

Paste a checklist run bundle and check every step receipt's hash chain and the run's Merkle root. A tampered step is named exactly, offline, client-side.

Sweep a numeric input or two through a live compliance node or gated workflow and see exactly where the decision flips. Renders the outcome surface as an SVG chart and signs the calibration result with an ephemeral key.

The claim-level evidence register for AINumbers.co: every registered public number bound to its source surface, the date it was measured, its next scheduled review, and a point-in-time snapshot of the exact source line.

OpenChainGraph GENIUS Continuous Reserve Watch: a receipted weekly monitor that runs the check_genius_reserve_disclosure kernel (art-275), signs a receipt referencing the result, and logs a CloudEvents envelope. Zero PII, zero paid plan.

Embeddable OCG receipt verify badge: embed instructions, zero-egress and fragment-payload notes, and golden/tampered fixture proof.

Criteria, registry, and badge asset for the OpenChainGraph Verified Build program: a self-declared-with-evidence conformance mark tied to the OCG v0.4 §15 gate suite.

Paste a RECEIPT-BUNDLE v0.1 portable receipt bundle and verify both halves offline in the browser: the zk proof half (Groth16 seal over the journal byte contract) and the logged half (Sigsum inclusion proof plus witness cosignature quorum). The two verdicts are always reported separately. Zero network calls. Zero PII.

Type or paste a government-payments RFP requirement list, drop the OpenChainGraph artifacts that answer it, and get a print-ready evidence annex: each requirement against its matched artifact, verified hash and signature, or an explicit narrative-response marker. Runs entirely in your browser.

Generate an Ed25519 did:key entirely in your browser, sign a §27.1 role-binding record, and print a dual-control key-custody record. The private key never leaves this tab.

CC0 1.0 defensive publication: binding a computation execution receipt hash to an independent external timestamp anchor for tamper-evident third-party verification.

Verify STP and auto-decisioning receipts from agent workflows. Hash, signature, gate-replay, and timestamp checks in your browser. Nothing uploaded.

Convert Markdown, tabular data, and documents locally in the browser, then bind the conversion into a hash-anchored receipt and verify it independently. Six deterministic OpenChainGraph nodes, zero network calls, zero PII.

Paste or drop an ocg-xbrl-json@1 export to see its facts, dimensions, and units as a table, check canonicalValues + JCS conformance, and verify the embedded execution_hash metadata against the original artifact. A round-trip check, not a conformance authority.

Preview the QR code an OCG verify deep-link will carry: version, module grid, and the exact URL a phone camera decodes.

Call the live AINumbers MCP server from your browser: initialize, list tools, and call any tool with a generated form. Raw request/response view, copyable curl and client-config snippets. Nothing stored, nothing sent anywhere but mcp.ainumbers.co.

Suggest a new fintech tool, an OpenChainGraph compute node, or a verifiable workflow (chain) for the AINumbers.co suite. Tell us the regulation, the input, and the output you need.

Evidence pack for the AINumbers AuthZ API on Bazantic: an x402/MPP gateway, a published Recipe, and a same-model A/B test where the Recipe is the only material difference between the two runs.

The OpenChainGraph education hub. Short descriptions and links to every explainer, the technical specification and white paper, the compute-integrity deep dive, and the integration guides. For engineers, auditors, and teams evaluating verifiable decision provenance.

The normative OpenChainGraph specification: artifact envelope and execution hash, RFC 8785 canonicalization, the financial payload layer, and the §15 conformance gate suite an implementation must pass.

A technical white paper on OpenChainGraph (OCG), an open standard for deterministic, hash-anchored, agent-callable decision artifacts that recompute in the browser. Covers the artifact envelope and execution hash, canonicalization, cross-vendor chaining, the strength-of-verifiable ladder (recompute, Data Integrity signature, zkVM compute-integrity proof), anchor bindings for independent timestamp evidence, decision gates for conditional chain execution, the agent interaction model, conformance-by-construction, the trust model, and a cross-domain deployment of more than 830 tools on three independent sites. Candid about what it does and does not prove.

A 3D brick scene of one ChainGraph workflow. The x402-spend-evidence chain runs three catalog tools in order, each step cites the hash of the step before it, and the run folds into one composite hash that outside authorities timestamp. Every hash on the page is quoted from a live run of 26 September 2026.

The same task done twice, side by side: fill out a form the old way, then run it as a verified workflow. Type in your own numbers, seal the result, then try to fake it and watch the seal break.

What AINumbers.co is, how it works, and how it relates to Post Oak Labs. A large catalog of deterministic, browser-based fintech tools across payments, compliance, treasury and risk. Zero install, zero PII, zero network calls, and results any agent can re-verify.

How Autonity's Auton Currency Unit (ACU) basket worked: seven currencies with fixed SDR-method amounts, floating USD weights, and a daily recomputed index value.

The centerpiece Autonity explainer: how the AFP DCC separated margin custody from trade intent using two keys, enabling venue-agnostic clearing. The computations outlive the chain.

How-to: an agent closes a mutual NDA with court-checkable artifacts by composing two shipped nodes, assemble_mutual_nda (ART-276) and bind_agreement_acceptance (ART-277), into an assemble-then-accept receipt chain. Zero PII. Not legal advice.

What an OpenChainGraph anchor binding proves: RFC 3161 tokens from independent timestamp authorities, one Merkle root covering many artifacts, and witness-cosigned checkpoints on a public log, with anchors already published on this estate that you can verify offline.

Tamper with a 3D wall of proof layers and see which layer catches each change, which only warns and which cannot tell, with real checks run in the browser on real evidence.

Step through three Canton settlement workflows: DvP readiness, repo collateral mobility, and capital efficiency. Each step links the tool that runs it and every workflow links its chain page.

Beginner walkthrough of a zero-knowledge proof: confirm an official rule produced a result without seeing the private data or redoing the work.

How OpenChainGraph §18 compute-integrity proofs work, with the math and code for each step, why they matter for regulated financial computation, and what we learned building them (including the parts that did not work) so other teams can skip the same mistakes. Software and cryptography only: no trusted hardware, no blockchain in the verify path.

Contact AINumbers.co. Report a bug, request a new payment tool, suggest an MCC or payment code, or ask about the suite. We read every message.

Every design idea AINumbers.co borrowed from elsewhere, with attribution, license, and status. Ideas only, never copied text or code.

Six report runs from four physical machines re-ran the estate's kernels at pinned commits and compared output digests. This page walks the dated attestation snapshot, the named mismatch classes, and the commands that re-derive every count.

CC0 1.0 defensive publication: forward-only decision-gated workflow chains with machine-checkable both-branch coverage proofs.

CC0 1.0 defensive publication: compiling a passkey-signed Work Mandate into a machine-checkable execution-gating policy whose hash propagates into every receipt an agent produces.

CC0 1.0 defensive publications from Post Oak Labs establishing dated prior art for mandate compilation, gated-chain workflow structure, and receipt-anchor timestamp binding.

Every deploy of ainumbers.co publishes a manifest and a sha256 line per published file. Run the two checks that connect a downloaded file to the commit that shipped it.

How Autonity's Forecastathon competition scored participants across four seasons: a four-component composite for S1-S3 and a simplified PnL-only measure for S4.

Transparency record of findings against previously-attested formal-verification spec versions. Never a dependency of receipt validity: receipts verify offline regardless.

A guided walkthrough of one synthetic CCP default-waterfall run: how the execution hash binds a result to its declared inputs and pinned kernel, how the salted commitment check reproduces from the witness, and what the ledger receipt establishes about attestation, time and verifier trust. Every hash recomputes from the public kernels.

The RISC Zero proving pipeline for AINumbers kernels: cycle preflight, GPU segments, recursion, a Groth16 wrap to 256 bytes and offline verification.

What each field of a compute receipt means, a step-by-step reading of one real receipt from the repository, and four ways to verify one: in the browser, on-chain, or from a clone.

Six drawn scenes follow one real compute receipt from the kernel that produced it to the checks that bind it: the two lanes that meet in a node file, the fields of the receipt, the three bindings that make it count, and the four ways to verify one.

Step-by-step animation of the Model Context Protocol: the handshake, the tool list and three linked tool calls to the AINumbers MCP server on Cloudflare.

Eight drawn scenes walk the mechanical verification standard: the claim ladder and its three tiers, the denominators behind each tier, a metamorphic property you can check by hand, one kernel's full evidence stack, and the red controls that prove the harnesses can fail.

An interactive walkthrough of the OpenChainGraph standard (version of record 0.8.13): SHA-256 hashing, parent_hash chains, MCP agent verification, cross-vendor trust, W3C PROV-DM, Ed25519 signing and key lifecycle, OpenTelemetry spans, ISO 20022, OKF bundles, profile conformance, Compute Binding, Export Profiles, Proof Binding (eddsa-jcs-2022), Kernel Identity Binding, Compute-Integrity Proofs, compliance_flags and RFC 3161 time anchoring. Client-side, zero-egress, with a live SHA-256 demo.

How the public OpenChainGraph conformance corpus pins the execution_hash: the canonical formula, the four checks the standalone verifier runs, and the kit a third party uses to submit its own kernel's vector.

How one self-contained tool page becomes an MCP Apps View inside an AI host and how its Policy Mandate receipt reaches an open ledger tab live over a same-origin BroadcastChannel. Every method name quoted on the page comes from the merged bridge code.

A seven-panel visual walk of the formal-verification pilot as implemented: clause to LLM-drafted spec, independence gates, human review, verification tiers, execution binding, the fixtures-are-not-proofs story, and how far the claims reach.

Animated WebMCP walkthrough: web pages register their own tools and a browser agent runs a three-step verification workflow entirely in your tabs.

How OpenChainGraph §27 records which named human took responsibility for a result: closed accountability roles, SCITT-style approval records over a subject execution_hash, in-toto dual-control thresholds counted by distinct identity, a §21.4-wired gate-policy vocabulary, time-boxed §22.10 overrides, and a §13.12 SD-JWT evidence bundle. Client-side, zero-egress.

Published in-toto Statement v1 predicate type for OpenChainGraph execution receipts. predicateType: https://ainumbers.co/attestations/ocg-execution-receipt/v0.1

Seven workflows run in your browser as one inverted database: receipts, a Merkle root, public timestamps and offline checks that need no server.

Interactive explainer: how the AFP DCC computed margin health, maintenance thresholds, and liquidation prices for isolated derivatives positions. Includes a live calculator with Autonity, Hyperliquid, and generic presets.

What mechanical verification means, the three claim tiers, a file-by-file walkthrough of the evidence for each of the five kernels with a formal claim, and the commands that re-run every check.

How AINumbers.co checks its outputs: golden fixtures, in-page rule citations, clause binding, the conformance gate suite, byte-identical replay, and zk compute proofs. What each mechanism establishes, and what it does not.

OpenChainGraph (OCG) application concepts across generative art, gaming, narrative, AI agents, physical installations, payments infrastructure, scientific computing, digital identity, software supply-chain, trade/logistics, regulatory transaction reporting, EU deforestation due diligence, and insurance prudential reporting, and verifiable client-side file conversions, with OCG primitives and build-readiness for each. Eighteen clusters across all industry verticals.

A field-by-field mapping of OpenChainGraph v0.4 execution receipt members to the EU AI Act's Article 12 record-keeping (automatic logging) requirements, with gaps stated honestly.

Verify an AINumbers compute-integrity receipt (risc0 Groth16) with one read-only eth_call against RISC Zero's deployed VerifierRouter on Ethereum mainnet or Base. No wallet, no gas, no code we wrote.

One AI shopping agent, one USD 120 purchase, three workflows: who the agent is, both budgets, a caught double order and a session receipt that reconciles it all.

Beginner walkthrough: one AINumbers workflow checks an AI shopping agent in three steps inside your browser. See pages, fingerprints and receipts.

An animated comparison of OpenChainGraph and a blockchain. Both link records by hash and fold them into Merkle roots. OpenChainGraph has no shared ledger and no validators, and it can still use a blockchain as one witness to when a record existed.

What happens when you paste an AINumbers chain prompt into an AI assistant: run_chain on the MCP worker, one changed input and a verified hash.

Interactive explainer: how scalar and binary event-market contracts pay out, the difference in payoff shape, and how Autonity's AFP ran forecast futures in Season 1. Try the live PnL calculator.

How ainumbers.co and the mcp.ainumbers.co endpoint treat your data: tools run in your browser, the MCP server stores no inputs or outputs, no accounts, no cookies, no tracking, no data sale or model training.

What share of the live OpenChainGraph graph carries a zkVM compute-integrity proof, the profile that requires one of every deterministic node, and what a deferred node is.

When the full record of a public payment lives inside the operator's own system, what can an outside audit authority actually verify? An animated, panel-by-panel walk through seven independent questions: settlement, attribution, reconciliation, the audit trail, bulk-run authorisation, migration completeness, and operator exit: mapped to shipped OpenChainGraph nodes. Client-side, zero-egress.

How to report a security vulnerability in AINumbers.co or Helm. Solo-maintainer disclosure policy: no fixed response-time commitment.

Settlement asset models are not interchangeable. A direct or two-tier CBDC has no backing set to check at all, while a reserve-backed stablecoin's backing is a portfolio, and holding limits, offline capability and the redemption path reach into stages beyond backing. An animated, panel-by-panel walk from backing through collection, netting, disbursement, reconciliation and control evidence, mapped to shipped OpenChainGraph nodes. Client-side, zero-egress.

A dated, field-level crosswalk between the VeritasChain Protocol v1.2 record format and the OpenChainGraph receipt: what each format binds, how completeness and anchoring work on both sides, where they genuinely differ, and which connectors do not exist yet. No bridge or implementation is claimed.

What a W3C Data Integrity proof adds to an OpenChainGraph artifact, how the eddsa-jcs-2022 pipeline signs and verifies it, and how a retired key shows up in a revocation status list a verifier can read.

How OpenChainGraph gated chains let a machine make routine regulated decisions end to end, under a signed human mandate, while every exception still lands in front of a person. Mortgage preflight, adverse action, and AI decision logs as shipped evidence.

Ten live AINumbers runs from 26 September 2026 sealed into one session receipt and timestamped by Sigstore, DigiCert and FreeTSA, with the real hashes.

AINumbers.co terms of use and reliance posture: what these tools are, what they are not, and how to treat their output when it cites regulation.

An animated staircase from one tool in a browser tab to an agent that carries verifiable receipts across workflows and blockchains. It covers the tool, kernel, node, execution hash, AIN Bridge, WebMCP, MCP, workflow, Helm pack, signature, kernel identity, RISC Zero, Groth16 and anchoring, then three live worked examples and a comparison with Trusted Compute Units. Every hash on the page comes from a live run.

An interactive brick model of the Agent Staircase. Fourteen bricks stack into five layers, from the tool page to the timestamped receipt, and every brick opens the explainer step behind it. Drag to spin the wall, then trace a run through the finished stack.

An interactive brick model of the AINumbers estate. Eight walls stand for its parts, from the tool catalog to Helm, and thirteen roads show how they work together. Drag to spin the view, watch the recorded tour, and open the page behind each wall.

What each member of the Policy Mandate v1.0 schema holds and the two gates that validate the document before a download can happen.

A regulator checks a real evidence bundle layer by layer in the browser: three timestamps, a session root, a Groth16 receipt, kernel identity, a signature and execution hashes, with what each check cannot prove.

What chaingraph.json contains, how the per-node shards on disk become that one file, where copies of it live, and how to verify a downloaded copy with a checksum line and a Sigstore attestation.

Side-by-side: how compliance decisions are proved today (email chains, PDFs, version drift) versus with OpenChainGraph (hash-linked artifacts, instant verification). For CFOs, auditors, and regulators.

How an artifact becomes a SHA-256 digest, how four independent rails anchor that digest to third-party time, how Sigsum's pending-to-included lifecycle and twelve witness cosigners work, how the resulting proof bundle verifies with the network unplugged, and how ledger.ainumbers.co resolves a hash to content under an RFC 6920 contract, including what none of it claims. Client-side, zero-egress.

How a signed Work Mandate becomes literal gates on an agent's workflow: the compiler that turns a threshold clause into a gate object, the halt-and-record semantics when a trigger fires, how a human closes an open exception with a passkey, and how a delegated agent's own identity chain verifies back to a person, including what none of it claims. Client-side, zero-egress.

Ten real run hashes fold into one timestamped Merkle root. Rebuild the tree in your browser, tamper with one run to see only its path break, and prove a single run with four sibling hashes.

An animated walk through the published methods page: the two kinds of evidence behind a result, how a specification earns its proof, what a proof does not tell you, and the checks that surround the proofs.

Compare three ways an AI agent runs AINumbers workflows: WebMCP in the browser, the remote MCP server on Cloudflare and Helm on your own machine.

The three doors an agent can use to reach one kernel on this estate: the page's browser registration, a deep link that carries the inputs, and a tools/call to the worker. One published input sample runs through all three, and the receipts name one hash a reader can recompute.

What WebMCP is on this estate: pages registering tools an agent can discover and call, the discovery file an agent reads, the call and verification loop, and a directory of every WebMCP surface with links.

Is OpenChainGraph actually new? A candid comparison to in-toto, SLSA, OpenLineage, AP2, and verifiable-AI: what OCG borrows, what's genuinely novel, why the pieces only converged in 2024–2026 (MCP, agentic payment standards, browser WebCrypto). For engineers, auditors, and technical due-diligence.

Helm is a local-first control plane for governed, evidenced automation. Runs on your machine, replays every computation, pins the kernel by digest, and produces evidence anyone can verify offline. In beta.

Paste-ready install paths that put Helm, a local evidence engine, behind OpenClaw or AutoClaw: the mcp.servers block, the exec allowlist, the trust statement, and prompts that verify offline.

A read-only guided walkthrough of Helm that runs entirely in this tab. Walk a compiled workflow, then verify a real signed evidence bundle and its tampered twin using the same verifier Helm ships. No download, no upload, no account.

Local Network Access (LNA) admin one-pager for Helm: what LNA is, why Helm's handoff needs it, and paste-ready LocalNetworkAccessAllowedForUrls managed Chrome/Edge policy JSON.

Every network request Helm can make: endpoint, payload shape, and trigger. Covers the browser app, the optional helmd engine, OAuth connectors, the anchor relay, and the fully offline, relay-blocked path.

How AINumbers Helm is built: process and serving model, the pairing gate, the hash-chained journal, the run engine, evidence bundles and offline verification, borrowed versus built, and known limitations.

What you can rely on when a tool on AINumbers.co references a regulation, standard, or supervisory framework.

The full catalog of domain hubs and integration guides, clustered by the work they support: payments, regulation, markets and treasury, risk, tokenization, trade, agents, the OpenChainGraph platform, and evidence.

Free browser-based developer tools for building Model Context Protocol servers and integrating agentic payment protocols. Tools: lint tool definitions and server.json, audit OAuth and transport security, scan for tool poisoning, score readiness, compare and build AP2 / ACP / x402 / Visa TAP / Mastercard Agent Pay, decode x402, validate A2A agent cards. All client-side. Zero PII. (19 tools)

22 free browser-based AML, KYC, and financial crime compliance tools unified as a single onboarding suite for BSA officers, MLROs, and compliance engineers. Covers FATF typologies, FinCEN SAR/CTR, EU 6AMLD, VASP Travel Rule, PEP screening, transaction monitoring rule design, and sanctions exposure. All client-side. Zero PII. (23 tools)

Free browser-based payment infrastructure tools covering A2A fee routing, ISO 20022 message building and migration, VDCAP payload auditing, reconciliation workbenches, synthetic test data generation, failure analysis, truncation auditing, and rail optimisation. All client-side. Zero PII. (10 tools)