AINumbers.co Analytics Mandate API
The analytics_mandate API from AINumbers.co — 1 operation(s) for analytics_mandate.
The analytics_mandate API from AINumbers.co — 1 operation(s) for analytics_mandate.
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-analytics-mandate-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 Analytics Mandate…
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: analytics_mandate
paths:
/v1/tools/recompute_bordereau:
post:
operationId: recompute_bordereau
summary: Delegated Authority Bordereau Recomputation
description: 'Recomputes a delegated authority bordereau the way the carrier reviewer does, from the same file the coverholder sent. It foots gross premium, brokerage, coverholder commission, mapped taxes and levies, ceded premium and net per currency, derives net from its components and compares that against a mapped net column, then compares the whole footing field by field against the totals the coverholder asserts. Exact agreement on a footing is a weak result and the tool says so, because both sides added the same column. The check that carries weight is utilisation of the binding authority: the aggregate and per risk limits are held by the carrier and are not on the bordereau, so they are declared caller inputs and are never derived from the document under review, which is what gives that comparison independent provenance. It also reports lines outside the declared period or permitted currency list, repeated policy references, absent expected periods and lines whose mapped fields are missing. Which of the supplied columns carries which measure is a caller declaration, as are the standard label and version, which are pinned into the artifact and shown on screen: no field list, schema, rate table or commission table is bundled or read, and nothing claims which revision of any standard is current, so a later revision makes an old receipt dated rather than wrong. The arithmetic reads only mapped numeric and reference columns. Every other column is ignored and reaches no result, and no rejection record echoes a cell value, so insured names, addresses and claim narratives stay out of the computed output. Money is fixed point in integer minor units with two decimal display throughout, decimal input is parsed from its string form rather than by floating point, and zero rows, an empty mapping and a zero limit each resolve to a defined result rather than to a not a number. Absent asserted totals the run is reported as recompute only, which is its own state and never a pass. Stated boundary: a difference means the two arithmetics disagree on the rows supplied, not that the coverholder misreported. It performs no data standard conformance validation, no terms of business or sanctions screening, no reserving or pricing adequacy assessment, and makes no assertion that authority was properly exercised, which is a conclusion for the delegated authority audit.
**Tool URL:** https://ainumbers.co/chaingraph/art-508-recompute-bordereau.html
**Wave:** 78
**mandate_type:** analytics_mandate
**AP2/Policy Mandate export:** yes'
tags:
- analytics_mandate
requestBody:
required: true
content:
application/json:
schema:
type: object
description: 'See tool page for full input schema: https://ainumbers.co/chaingraph/art-508-recompute-bordereau.html'
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
description: 'OpenChainGraph v0.4 artifact envelope. mandate_type: analytics_mandate. Verify execution_hash at https://ainumbers.co/chaingraph/verify.html'
x-mcp-tool-name: recompute_bordereau
x-tool-url: https://ainumbers.co/chaingraph/art-508-recompute-bordereau.html
x-source: chaingraph
x-ap2-export: true
x-mandate-type: analytics_mandate
x-ocg-wave: 78
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.