AINumbers.co case file API

The case file API from AINumbers.co — 3 operation(s) for case file.

Operations 3

POST /v1/tools/build_casefile_binder Case-File Binder Composer #
POST /v1/tools/verify_casefile_binder Case-File Binder Verifier #
POST /v1/tools/build_evidence_handover_bundle Evidence Handover Bundle #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/ainumbers-co:ainumbers-co-case-file-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

ainumbers-co-case-file-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: AINumbers.co Fintech Intelligence Suite case file 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: case file
paths:
  /v1/tools/build_casefile_binder:
    post:
      operationId: build_casefile_binder
      summary: Case-File Binder Composer
      description: 'Composes a signed, Merkle-rooted case-file binder manifest over a caller-supplied set of heterogeneous receipts (OCG artifacts, chain composites, disclosure manifests, Helm bundle signposts, anchor proofs). A manifest-of-manifests: never ingests file contents, never re-verifies a referenced receipt, only indexes it by digest with a hint for where to check it.


        **Tool URL:** https://ainumbers.co/tools/574-casefile-binder-composer.html'
      tags:
      - case file
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - entries
              properties:
                engagement_label:
                  type: string
                  description: Label for the engagement or matter
                period:
                  type: string
                  description: Reporting or engagement period
                entries:
                  type: array
                  description: List of {kind,ref_label,digest,verify_hint}
      responses:
        '200':
          description: Successful tool execution result
          content:
            application/json:
              schema:
                type: object
                properties:
                  manifest:
                    type: object
                  merkle_root:
                    type: string
                  diff:
                    type: object
      x-mcp-tool-name: build_casefile_binder
      x-tool-url: https://ainumbers.co/tools/574-casefile-binder-composer.html
      x-source: manifest
  /v1/tools/verify_casefile_binder:
    post:
      operationId: verify_casefile_binder
      summary: Case-File Binder Verifier
      description: 'Verifies a case-file binder manifest''s eddsa-jcs-2022 signature, recomputes its Merkle root over entries, and offers per-entry digest checks against a pasted referenced receipt (disclosure manifest, OCG artifact, chain composite). Never claims to re-verify a Helm bundle or anchor proof''s internals — surfaces the entry''s verify_hint instead.


        **Tool URL:** https://ainumbers.co/tools/575-casefile-binder-verifier.html'
      tags:
      - case file
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - binder
              properties:
                binder:
                  type: object
                  description: The case-file binder manifest to verify
      responses:
        '200':
          description: Successful tool execution result
          content:
            application/json:
              schema:
                type: object
                properties:
                  signature_valid:
                    type: boolean
                  merkle_root_valid:
                    type: boolean
                  entry_checks:
                    type: array
      x-mcp-tool-name: verify_casefile_binder
      x-tool-url: https://ainumbers.co/tools/575-casefile-binder-verifier.html
      x-source: manifest
  /v1/tools/build_evidence_handover_bundle:
    post:
      operationId: build_evidence_handover_bundle
      summary: Evidence Handover Bundle
      description: 'Packages a case-file binder manifest plus its caller-pasted referenced receipts into one client-side zip: a self-contained offline verify.html (zero network calls at verify time), the raw JSON receipts, and a plain-English README explaining what verified does and does not mean. Optionally attaches a pre-captured DNSSEC chain (dig +dnssec output the caller ran externally) as a corroboration item; this tool never queries DNS itself and never validates the chain. Built for handing an examiner a bundle they can open on an air-gapped machine.


        **Tool URL:** https://ainumbers.co/tools/576-evidence-handover-bundle.html'
      tags:
      - case file
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - binder
              properties:
                binder:
                  type: object
                  description: A case-file binder manifest (ainumbers-casefile-binder-v1)
                receipts:
                  type: array
                  description: Optional list of receipt JSON objects the caller has in hand, matched to binder entries by digest
                dnssec_chain_capture:
                  type: object
                  description: Optional pre-captured DNSSEC chain (queried_name, resolver, captured_at, raw_chain_text). Never fetched or validated here; verify with delv.
      responses:
        '200':
          description: Successful tool execution result
          content:
            application/json:
              schema:
                type: object
                properties:
                  zip_filename:
                    type: string
                  file_count:
                    type: number
      x-mcp-tool-name: build_evidence_handover_bundle
      x-tool-url: https://ainumbers.co/tools/576-evidence-handover-bundle.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.