AINumbers.co OTLP API
The OTLP API from AINumbers.co — 2 operation(s) for otlp.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/ainumbers-co:ainumbers-co-otlp-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
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 Specification
openapi: 3.2.0
info:
title: AINumbers.co Fintech Intelligence Suite OTLP 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: OTLP
paths:
/v1/tools/lint_otlp_genai_trace:
post:
operationId: lint_otlp_genai_trace
summary: OTLP GenAI Span Composer & Semconv Linter
description: 'Compose hand-rolled OTLP/JSON traces (resourceSpans/scopeSpans/spans) with gen_ai presets for invoke_agent, chat, and execute_tool spans, and lint any OTLP/JSON trace for structural validity and gen_ai attribute conformance against a pinned attribute snapshot — the gen_ai semantic-convention namespace has zero tagged upstream releases, so semconv_snapshot is stamped into every artifact. File export only, zero network egress. Zero PII.
**Tool URL:** https://ainumbers.co/tools/556-otlp-genai-span-composer-linter.html
**AP2/Policy Mandate export:** yes'
tags:
- OTLP
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- trace
properties:
trace:
type: object
description: OTLP/JSON trace document (resourceSpans root)
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
$schema: https://json-schema.org/draft/2020-12/schema
type: object
required:
- overall_valid
- findings
properties:
overall_valid:
type: boolean
violations:
type: integer
checks_passed:
type: integer
findings:
type: array
items:
type: object
properties:
id:
type: string
title:
type: string
status:
type: string
enum:
- ok
- bad
- warn
- info
ok:
type:
- boolean
- 'null'
receipt:
type: object
description: OCG check receipt (policy_parameters, output_payload, execution_hash, semconv_snapshot)
x-mcp-tool-name: lint_otlp_genai_trace
x-tool-url: https://ainumbers.co/tools/556-otlp-genai-span-composer-linter.html
x-source: manifest
x-ap2-export: true
/v1/tools/verify_otel_span_receipt:
post:
operationId: verify_otel_span_receipt
summary: OTel Span Receipt Verifier
description: 'Generates a per-span receipt chain over an OTLP/JSON trace (span digest, parent-span receipt digest, semconv_snapshot, eddsa-jcs-2022 signature over an ephemeral did:key) plus a Merkle-rooted (RFC 6962) trace receipt, then verifies any trace + receipt bundle: recomputes digests, walks the parent-receipt chain, rebuilds the Merkle root, and reports which spans are attested, unattested, or tampered. File export only, zero network egress. Zero PII.
**Tool URL:** https://ainumbers.co/tools/566-otel-span-receipt-verifier.html
**AP2/Policy Mandate export:** yes'
tags:
- OTLP
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- trace
- bundle
properties:
trace:
type: object
description: OTLP/JSON trace document (resourceSpans root)
bundle:
type: object
description: Span-receipt bundle (span_receipts[] + trace_receipt) to verify against the trace
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
$schema: https://json-schema.org/draft/2020-12/schema
type: object
required:
- span_receipts
- trace_receipt
properties:
span_receipts:
type: array
items:
type: object
properties:
span_id:
type: string
parent_span_id:
type:
- string
- 'null'
span_digest:
type: string
parent_receipt_digest:
type:
- string
- 'null'
semconv_snapshot:
type: string
proof:
type: object
trace_receipt:
type: object
description: RFC 6962 Merkle root over span_receipts, plus OCG execution_hash and eddsa-jcs-2022 proof
verification_report:
type: object
description: attested/unattested/tampered counts and per-span findings from a verify run
x-mcp-tool-name: verify_otel_span_receipt
x-tool-url: https://ainumbers.co/tools/566-otel-span-receipt-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.