AINumbers.co salted hash API

openapi: 3.2.0
info:
  title: AINumbers.co Fintech Intelligence Suite salted hash API
  version: 1.0.0
  description: '**1255 fintech intelligence tools** covering ISO 20022, A2A payments, CFPB §1033, EU AI Act, DORA, MiCA, AML/KYC, BaaS, DLT/tokenization, ESG/climate finance, agentic payments (AP2, ACP, x402, Visa TAP, Mastercard Agent Pay), PQC migration, sanctions screening, and OpenChainGraph v0.4 computation chains.


    ## Transport


    > **The live transport is MCP JSON-RPC 2.0 at `https://mcp.ainumbers.co/mcp` — not REST.**

    >

    > This OpenAPI file is a **descriptive data-room artifact** — a machine-readable index of all tools and their input/output schemas. The REST paths (`POST /v1/tools/{name}`) described here are a projection; they become functional only if the optional REST shim (Area 2 Path B) is deployed.

    >

    > To call tools today, connect via the official MCP client SDKs. TypeScript: `@modelcontextprotocol/sdk`. Python: `mcp`.


    ## Architecture


    All tools run **entirely client-side** (browser JavaScript). Zero PII. Zero server calls after page load. Deterministic, reproducible outputs. Licensed CC BY 4.0.


    OpenChainGraph v0.4 compute-binding nodes additionally run **server-side on the MCP Worker** and emit verifiable artifacts with `execution_hash` (WebCrypto SHA-256 over RFC 8785 canonical JSON).'
  contact:
    name: Post Oak Labs
    url: https://postoaklabs.com
    email: tim@postoaklabs.com
  license:
    name: CC BY 4.0
    url: https://creativecommons.org/licenses/by/4.0/
servers:
- url: https://ainumbers.co
  description: Static browser-based tool host (DreamHost). Tools run client-side — no REST gateway is active on this origin. See x-mcp for the live MCP endpoint.
tags:
- name: salted hash
paths:
  /v1/tools/salted_hash_enumerability_demo:
    post:
      operationId: salted_hash_enumerability_demo
      summary: Salted Hash Enumerability Demo
      description: 'Teaching demo of hash enumerability over toy corpora. Panel 1 hashes a chosen low-entropy identifier (month name, ISO country short name, or a synthetic plate ID) with bare SHA-256. Panel 2 runs a client-side dictionary attack over the same corpus and visibly recovers the identifier, with a candidate counter and elapsed milliseconds. Panel 3 commits to the same identifier under the estate''s sha256-salted@1 shape: a fresh 256-bit crypto.getRandomValues salt, declared hash-excluded, is generated in the browser and withheld from the attack panel, and the same attack exhausts the corpus without a match. An honesty line states the boundary: the protection holds because the salt stays with the committer; a salt published next to the digest defeats precomputation, not enumeration. Toy corpora only; never presented as an eKYC compliance tool. No network, no storage, deterministic seeded example.


        **Tool URL:** https://ainumbers.co/tools/689-salted-hash-enumerability-demo.html'
      tags:
      - salted hash
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                corpus:
                  type: string
                  enum:
                  - months
                  - countries
                  - plates
                  description: Toy corpus name.
                identifier:
                  type: string
                  description: Identifier from the selected corpus.
              required:
              - corpus
              - identifier
      responses:
        '200':
          description: Successful tool execution result
          content:
            application/json:
              schema:
                type: object
                properties:
                  bare_digest:
                    type: string
                  attack:
                    type: object
                  salted_commitment:
                    type: string
                  salted_attack:
                    type: object
                  verdict:
                    type: string
      x-mcp-tool-name: salted_hash_enumerability_demo
      x-tool-url: https://ainumbers.co/tools/689-salted-hash-enumerability-demo.html
      x-source: manifest
x-mcp:
  transport: MCP JSON-RPC 2.0 (streamable HTTP)
  endpoint: https://mcp.ainumbers.co/mcp
  protocol_version: '2025-11-25'
  authentication: none
  registry: co.ainumbers/tools (official MCP registry)
  note: Connect any MCP-compatible client (Claude, ChatGPT, custom agent) directly to this endpoint. The REST paths in this file are descriptive only — they do not exist on the live server unless the REST shim is deployed.