AINumbers.co Swift API

openapi: 3.2.0
info:
  title: AINumbers.co Fintech Intelligence Suite Swift 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: swift
paths:
  /v1/tools/decode_swift_mt_mx_field_migration:
    post:
      operationId: decode_swift_mt_mx_field_migration
      summary: SWIFT MT→MX Field Migration Decoder
      description: 'Maps legacy SWIFT MT fields (MT103/MT202/MT940/MT950) to ISO 20022 MX equivalents with truncation alerts and coexistence period guidance.


        **Tool URL:** https://ainumbers.co/tools/402-swift-mt-mx-field-decoder.html'
      tags:
      - swift
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties: {}
      responses:
        '200':
          description: Successful tool execution result
          content:
            application/json:
              schema:
                type: object
                properties:
                  result:
                    type: object
                  summary:
                    type: string
      x-mcp-tool-name: decode_swift_mt_mx_field_migration
      x-tool-url: https://ainumbers.co/tools/402-swift-mt-mx-field-decoder.html
      x-source: manifest
  /v1/tools/check_mt101_coexistence_readiness:
    post:
      operationId: check_mt101_coexistence_readiness
      summary: Swift MT101 Coexistence Readiness Diff
      description: 'Evaluates Swift CBPR+ MT101 message-type retirement readiness for the end of FI-to-FI coexistence, when bulk/multiple payment initiation drops MT101 (FIN) in favor of pain.001v9 (ISO 20022 MX). The former 14 November 2026 coexistence end was deferred by Swift on 27 August 2026 and no replacement date has been published, so the countdown below is planning-only against the superseded date. Declare the message format currently in production and a structural self-declared readiness checklist and get a deterministic ready/not-ready verdict plus days to the superseded planning date. Client-side, deterministic, zero PII.


        **Tool URL:** https://ainumbers.co/tools/577-mt101-coexistence-readiness-diff.html

        **AP2/Policy Mandate export:** yes'
      tags:
      - swift
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - currentMessageFormat
              - asOfDate
              properties:
                currentMessageFormat:
                  type: string
                  enum:
                  - MT101
                  - pain.001v9
                  description: Message format currently in production for FI-to-FI bulk payment initiation
                asOfDate:
                  type: string
                  description: ISO date (YYYY-MM-DD) to evaluate readiness as of
                emitsPain001v9Bulk:
                  type: boolean
                  description: True if the sender's system already emits pain.001v9 for bulk FI-to-FI (only relevant when currentMessageFormat is pain.001v9)
                fallbackPathStaged:
                  type: boolean
                  description: True if a fallback pain.001v9 path is staged (only relevant when currentMessageFormat is MT101)
                correspondentConfirmedReceipt:
                  type: boolean
                  description: True if the correspondent has confirmed it can receive pain.001v9 (only relevant when currentMessageFormat is MT101)
      responses:
        '200':
          description: Successful tool execution result
          content:
            application/json:
              schema:
                type: object
                properties:
                  mt101_coexistence_deadline:
                    type: string
                  days_to_deadline:
                    type: number
                  ready:
                    type: boolean
                  readiness_gaps:
                    type: array
                  structural_issues:
                    type: array
      x-mcp-tool-name: check_mt101_coexistence_readiness
      x-tool-url: https://ainumbers.co/tools/577-mt101-coexistence-readiness-diff.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.