AINumbers.co Recordkeeping API
The recordkeeping API from AINumbers.co — 1 operation(s) for recordkeeping.
The recordkeeping API from AINumbers.co — 1 operation(s) for recordkeeping.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/ainumbers-co:ainumbers-co-recordkeeping-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: AINumbers.co Fintech Intelligence Suite Recordkeeping 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: recordkeeping
paths:
/v1/tools/compute_recordkeeping_completeness_mapper:
post:
operationId: compute_recordkeeping_completeness_mapper
summary: Recordkeeping Completeness Mapper
description: 'Channel inventory roll-up for books-and-records completeness over caller-declared synthetic inputs. Declares each channel (email, chat, voice, messaging, ...) with a captured flag and a retrieval-test result (pass/fail/not_run), and computes: total, captured count, completeness percentage (whole number, half-up), the uncaptured listing, retrieval-pass count, and an overall verdict (COMPLETE only when every channel is captured AND every retrieval test passes; otherwise GAPS_FOUND). Not-proven discipline: it does not check live SSR tapes, borrow lists, cutoff feeds, registers, or any records system -- a COMPLETE verdict is the caller''s declaration, never an attestation. Absent or invalid inputs fail closed and are named. No network, no storage, no clock.
**Tool URL:** https://ainumbers.co/tools/675-recordkeeping-completeness-mapper.html
**AP2/Policy Mandate export:** yes'
tags:
- recordkeeping
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
channels:
type: array
description: 'Declared channels: {name, captured (boolean), retrieval_test (pass|fail|not_run)}.'
required:
- channels
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
total:
type:
- number
- 'null'
description: Declared channel count; null on the fail-closed path.
captured:
type:
- number
- 'null'
description: Count of channels declared captured.
completeness_pct:
type:
- number
- 'null'
description: Whole-number percentage, half-up rounded, of captured/total.
uncaptured:
type: array
description: Names of channels declared not captured.
retrieval_passes:
type:
- number
- 'null'
description: Count of channels whose declared retrieval_test is pass.
overall:
type:
- string
- 'null'
enum:
- COMPLETE
- GAPS_FOUND
- null
description: COMPLETE iff every channel captured and every retrieval test pass; otherwise GAPS_FOUND.
trace:
type: string
description: Fail-closed reasons naming each rejected input (fail-closed path only).
domain_errors:
type: array
description: Fail-closed error codes (fail-closed path only).
x-mcp-tool-name: compute_recordkeeping_completeness_mapper
x-tool-url: https://ainumbers.co/tools/675-recordkeeping-completeness-mapper.html
x-source: manifest
x-ap2-export: true
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.