AINumbers.co Psp API

openapi: 3.2.0
info:
  title: AINumbers.co Fintech Intelligence Suite Psp 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: psp
paths:
  /v1/tools/crosswalk_psp_dispute_reasons:
    post:
      operationId: crosswalk_psp_dispute_reasons
      summary: PSP Dispute Reason Crosswalk
      description: 'Dispute reason-code crosswalk across PayPal, Stripe, Adyen and Square (PSP-DISPUTE-CROSSWALK-NODE-1, hub proposal PAYPAL-HUB-PROPOSALS-2026-10-24 §10.3(2) as narrowed by the desk 2026-10-25: static and credential-free). From one PSP''s own dispute-reason value in that PSP''s exact enum spelling, or from a card-network reason code where the snapshots publish a mapping (Visa, Mastercard), the node returns the equivalent reason values at the other three PSPs with a per-cell match grade (exact / partial / none), each cell justified by the snapshot clause ids and verbatim quotes that support it, plus the evidence categories per PSP where a snapshot states them, the network codes where any snapshot states a mapping, the concept and per-PSP match. A mapping no snapshot supports is none, never inferred; snapshot-stated absences are cited as stated. Unknown PSP, unknown reason, non-string reason, both-or-neither input shape and unknown network or network code are refused by name. Clause authority: research/clause-snapshots/{paypal,stripe,adyen,square}-disputes-2026-10/SNAPSHOT.md (row PSP-DISPUTES-PRIMARY-TEXT-1). Zero network, zero PII, synthetic values only.


        **Tool URL:** https://ainumbers.co/chaingraph/art-777-psp-dispute-reason-crosswalk.html

        **AP2/Policy Mandate export:** yes'
      tags:
      - psp
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                psp:
                  type: string
                  enum:
                  - paypal
                  - stripe
                  - adyen
                  - square
                  description: PSP whose vocabulary the reason value belongs to.
                reason:
                  type: string
                  description: Dispute-reason value in that PSP's exact enum spelling.
                network_code:
                  type: object
                  description: '{network: visa|mastercard, code} card-network reason-code lookup, alternative to psp+reason.'
      responses:
        '200':
          description: Successful tool execution result
          content:
            application/json:
              schema:
                type: object
                description: 'output_payload: input echo, concept + concept_label, match, per_psp_match, crosswalk {<psp>: {psp, value, match, basis, evidence_categories, clauses [{id, quote, url}]}}, network_codes, network_codes_note, cited_clauses [{id, quote, url}], domain_errors [{code}], refusal_reason.'
      x-mcp-tool-name: crosswalk_psp_dispute_reasons
      x-tool-url: https://ainumbers.co/chaingraph/art-777-psp-dispute-reason-crosswalk.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.