AINumbers.co Whistleblowing API
The whistleblowing API from AINumbers.co — 1 operation(s) for whistleblowing.
The whistleblowing API from AINumbers.co — 1 operation(s) for whistleblowing.
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-whistleblowing-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 Whistleblowing 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: whistleblowing
paths:
/v1/tools/compute_whistleblowing_channel_clock:
post:
operationId: compute_whistleblowing_channel_clock
summary: Whistleblowing Channel Clock Checker
description: 'Pure calendar-clock arithmetic for a whistleblowing channel over caller-declared synthetic inputs. Checks the declared acknowledgement date against the 7-calendar-day acknowledgement deadline of Directive (EU) 2019/1937 Art 9(1)(b), and computes the follow-up due date as receipt plus a caller-declared whole-day basis (the spec pins the declared basis at 90 days, the Directive''s Art 9(1)(f) three-month ceiling as declared days). Pure integer civil-day arithmetic -- no Date object, no runtime clock. No report register, no case feed, no network.
**Tool URL:** https://ainumbers.co/tools/677-whistleblowing-channel-clock.html
**AP2/Policy Mandate export:** yes'
tags:
- whistleblowing
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
report_received:
type: string
description: declared report receipt date, YYYY-MM-DD
ack_sent:
type: string
description: declared acknowledgement date, YYYY-MM-DD
followup_basis_days:
type: number
description: declared follow-up basis in whole civil days
required:
- report_received
- ack_sent
- followup_basis_days
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
ack_days:
type:
- integer
- 'null'
description: Civil days from report receipt to acknowledgement; null on the fail-closed path.
ack_within_7:
type:
- boolean
- 'null'
description: True when ack_days <= 7 (Dir 2019/1937 Art 9(1)(b)); null on the fail-closed path.
followup_due:
type:
- string
- 'null'
description: Follow-up due date, receipt + basis civil days, YYYY-MM-DD; null on the fail-closed path.
trace:
type: string
description: The two clock clauses, or the fail-closed reasons naming each rejected input.
overall:
type: string
description: CLOCKS_COMPLIANT, ACK_WINDOW_BREACHED, or INPUT_REFUSED on the fail-closed path.
x-mcp-tool-name: compute_whistleblowing_channel_clock
x-tool-url: https://ainumbers.co/tools/677-whistleblowing-channel-clock.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.