AINumbers.co VC JCS API

openapi: 3.2.0
info:
  title: AINumbers.co Fintech Intelligence Suite VC JCS 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: VC-JCS
paths:
  /v1/tools/verify_vcjcs_envelope:
    post:
      operationId: verify_vcjcs_envelope
      summary: VC-JCS Envelope Verifier
      description: 'Offline verifier for W3C VC 2.0 Data Integrity (eddsa-jcs-2022 / did:key) exports produced by AINumbers tools. Decodes the did:key verificationMethod directly to Ed25519 key bytes, recomputes the JCS-canonicalized proof hash and verifies the signature, and independently recomputes every embedded execution_hash from its policy_parameters/output_payload — never trusting either the proof or the execution_hash fields as stated in the pasted document. Zero network calls anywhere in the tool.


        **Tool URL:** https://ainumbers.co/tools/624-vcjcs-envelope-verifier.html

        **AP2/Policy Mandate export:** yes'
      tags:
      - VC-JCS
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                export_document:
                  type: object
      responses:
        '200':
          description: Successful tool execution result
          content:
            application/json:
              schema:
                $schema: https://json-schema.org/draft/2020-12/schema
                type: object
                properties:
                  verification_report:
                    type: object
                    description: verdict, signature check, per-receipt execution_hash recompute results, attestation_grade and signing-identity class
      x-mcp-tool-name: verify_vcjcs_envelope
      x-tool-url: https://ainumbers.co/tools/624-vcjcs-envelope-verifier.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.