AINumbers.co Pp.lineage API

openapi: 3.2.0
info:
  title: AINumbers.co Fintech Intelligence Suite Pp.lineage 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: pp.lineage
paths:
  /v1/tools/render_agent_lineage_card:
    post:
      operationId: render_agent_lineage_card
      summary: Agent Lineage Card
      description: 'Paste an agent decision receipt with a pp.lineage block and this page renders a human-legible lineage card: model identity and version tagged asserted or observed, the IOSCO agentic autonomy five, the intent to policy to action to outcome chain, the traceparent binding, and the hash bindings. When the artifact carries its preimage the embedded execution_hash is recomputed in your browser with the estate''s canonical JCS serializer and compared, so a tampered lineage shows MISMATCH. Render only: the card displays exactly the states present in the input and invents nothing. Optional delegation_chain, human_checkpoints and revocable_by members render only when present and are labelled spec-pending; absent members render as not present. A #selftest=1 fragment runs the bundled golden fixture (MATCH), its one-byte tampered twin (MISMATCH) and a minimal fixture (absent optionals) end to end. Runs entirely in the browser, zero network, zero storage, deterministic.


        **Tool URL:** https://ainumbers.co/tools/717-agent-lineage-card.html'
      tags:
      - pp.lineage
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                artifact:
                  type: object
                  description: The OCG artifact JSON to render
              required:
              - artifact
      responses:
        '200':
          description: Successful tool execution result
          content:
            application/json:
              schema:
                type: object
                properties:
                  verdict:
                    type: string
                    enum:
                    - MATCH
                    - MISMATCH
                    - MALFORMED
                    - NOT_AN_OCG_ARTIFACT
                  recomputed_hash:
                    type: string
                  rendered:
                    type: object
      x-mcp-tool-name: render_agent_lineage_card
      x-tool-url: https://ainumbers.co/tools/717-agent-lineage-card.html
      x-source: manifest
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.