AINumbers.co Fedwire API
The fedwire API from AINumbers.co — 1 operation(s) for fedwire.
The fedwire API from AINumbers.co — 1 operation(s) for fedwire.
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-fedwire-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 Fedwire 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: fedwire
paths:
/v1/tools/fedwire_remediation_diff_receipt:
post:
operationId: fedwire_remediation_diff_receipt
summary: Fedwire/CHIPS Remediation Diff Receipt
description: 'Diffs an original and a remediated Fedwire/CHIPS structured-address payment file (CSV) record-by-record against the Fedwire/CHIPS structured-address lint (Fedwire''s ISO 20022 structured-address release was rescheduled from 16 November 2026 to the November 2027 release by Federal Reserve Financial Services on 27 August 2026; exact date to be announced) and produces a remediation-evidence receipt binding both file digests and the rule-clearance delta (non-compliant count before minus after).
**Tool URL:** https://ainumbers.co/tools/548-fedwire-remediation-diff-receipt.html
**AP2/Policy Mandate export:** yes'
tags:
- fedwire
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- originalCsv
- remediatedCsv
properties:
originalCsv:
type: string
description: 'Raw CSV content of the pre-remediation payment file. Header: network,street_name,building_number,post_code,town_name,country,country_subdivision,address_lines'
remediatedCsv:
type: string
description: Raw CSV content of the post-remediation payment file, same row order as originalCsv
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
original_file_digest:
type: string
remediated_file_digest:
type: string
before_non_compliant_count:
type: number
after_non_compliant_count:
type: number
clearance_delta:
type: number
fully_cleared:
type: boolean
per_record_diff:
type: array
x-mcp-tool-name: fedwire_remediation_diff_receipt
x-tool-url: https://ainumbers.co/tools/548-fedwire-remediation-diff-receipt.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.