② Run

Verifiable fintech workflows built to run in your browser

This is an entry point for fintech workflows that only live in your browser, covering compliance, payments, lending, and insurance. Choose a task, run it through a published workflow, and receive a cryptographically verifiable result. Every output carries an execution hash you can replay or share with an auditor. Your agents can do it all as well, because every tool and workflow produces a verifiable receipt, including via MCP.

Agents: connect at mcp.ainumbers.co/mcp · index at /llms.txt · read the whitepaper

Explore the suite

The primary elements of serverless architecture

Run and build
Verify and evidence
Verify ✅
Check the execution_hash of any OpenChainGraph artifact, client-side, no data leaves your browser.
Open
Conformance Gate 🚦
Drop in an artifact and run the applicable subset of the SPEC.md §15 gate suite client-side: which gates passed, which failed, and why.
Open
Audit-Trail Crosswalk 📋
Receipt fields mapped clause by clause to EU AI Act Article 12, PCI DSS v4.0.1 Requirement 10, and SOX, gaps included.
Read
Verification Desk 🔎
Drop an artifact, chain, or evidence bundle for a full section-by-section report: shape, signature, compute proof, anchor, attestations, approvals.
Open
Groth16 Receipts 🧾
What the compute receipt on a proof-bearing kernel contains, what its seal proves and what it does not, and three ways to verify one: browser, on-chain, or repo.
Read
Mechanical Verification ⚙️
The standard behind verification claims that come with a re-run: the claim tiers, the exact evidence paths, and the commands that check them.
Read
Groth16, Drawn 📐
Six animated scenes from kernel source to verified receipt: the two lanes that meet in a node file, the fields a verifier reads, and the bindings that make a receipt count.
Read
Verification, Drawn 📊
Eight animated scenes on the mechanical standard: the claim ladder, the denominators behind each tier, one kernel's evidence stack, and the red controls that prove the harnesses can fail.
Read
Bundle Diff 🔀
Compare two artifacts or evidence bundles: which input hashes moved, which kernel or policy versions changed, which §27 approvals differ, whether the verdict changed.
Open
Workpaper Index 🗂️
Drag any number of artifacts or evidence files into a PBC-style index: filename, hash, type, section coverage, signer roles, chain membership, exported as a hash-anchored JSON file.
Open
Anchor ⚓
Timestamp and sign any hash as independent evidence, no account needed.
Open
Key Ceremony Helper 🔑
Generate a did:key, sign a §27.1 role-binding record, and print a dual-control key-custody record. Key never leaves your browser.
Open
Ledger 📋
Look up a hash, check receipts, and replay execution hashes your agent produced.
Open
Convert and inspect
Connect
Read
Find a tool

Search 590+ tools and workflows

Results include standalone tools and multi-step workflows. All run locally, no data sent anywhere.

Connect an agent

Your first receipt in 60 seconds

Point any MCP client at the suite and run one tool. Here is the whole path, start to finish.

  1. Find the listing at co.ainumbers/tools in the MCP registry, or connect directly.
  2. Endpoint: https://mcp.ainumbers.co/mcp
  3. Add it to your client config:
    {
      "mcpServers": {
        "ainumbers": {
          "url": "https://mcp.ainumbers.co/mcp"
        }
      }
    }
  4. Run any tool. Your agent gets back a receipt with an execution hash.
  5. Paste that receipt into verify.html to check it, client-side, no data leaves your browser.

Verify witness cosignatures with the witness cosignature verifier. Document conversion with a verifiable receipt is live now at the Conversion Lab.