AINumbers.co Obligations Register API
The obligations-register API from AINumbers.co — 1 operation(s) for obligations-register.
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-obligations-register-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 Obligations…
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: obligations-register
paths:
/v1/tools/compute_regulatory_obligations_register:
post:
operationId: compute_regulatory_obligations_register
summary: Regulatory Obligations Register
description: 'A regime-agnostic rule-to-obligation-to-evidence register verdict: obligations in (rule_id, owner, control_ids, evidence_refs), coverage math out (owner and evidence percentages, control-linkage count, unassigned list, one FAIL finding per failing check, overall COVERED or GAPS_FOUND). Five stages in one pure compute() per OBLIGATIONS-REGISTER-BUILD-SPEC.md: intake with fail-closed shape validation, owner coverage, control linkage, evidence linkage, verdict. Owner and evidence coverage are the gated checks; control linkage is measured but never gates. The spec''s worked example is carried as the oracle-backed golden fixture (pinned execution_hash bdf74ddc2f836c5e34b374d65f915e96684b061792283d775b08f2e9cd34ba67).
**Tool URL:** https://ainumbers.co/chaingraph/art-691-regulatory-obligations-register.html
**AP2/Policy Mandate export:** yes'
tags:
- obligations-register
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- input_parameters
properties:
input_parameters:
type: object
required:
- rules
properties:
as_of:
type: string
description: Optional as-of date, YYYY-MM-DD; optional; present on the well-formed fixture vectors, absent on some fail-closed ones, and validated as a date string by the kernel whenever present.
rules:
type: array
minItems: 1
description: The obligations register; a register must carry at least one obligation. Each entry must carry a rule_id; a missing or blank rule_id fails closed at intake.
items:
type: object
required:
- rule_id
properties:
rule_id:
type: string
minLength: 1
owner:
type:
- string
- 'null'
minLength: 1
description: Non-empty string, or null marking an unassigned obligation; absent reads as unassigned.
x_null_distinct: true
control_ids:
type:
- array
- 'null'
items:
type: string
minLength: 1
description: Absent or null reads as no controls, not as malformed.
evidence_refs:
type:
- array
- 'null'
items:
type: string
minLength: 1
description: Absent or null reads as no evidence pointers, not as malformed.
x_schema_provenance: 'derived-from-golden-fixtures 2026-09-22 (mirrors input_schema: policy_parameters across the 22 golden fixture vectors)'
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
required:
- total
- owner_assigned
- owner_coverage_pct
- control_linked
- evidence_linked
- evidence_coverage_pct
- unassigned
- findings
- overall_determination
properties:
total:
type: integer
minimum: 0
description: Obligations in the register. 0 on the fail-closed intake path.
owner_assigned:
type: integer
minimum: 0
description: Obligations with a non-null non-empty owner.
owner_coverage_pct:
type: number
minimum: 0
maximum: 100
description: owner_assigned / total as a percentage rounded to one decimal (66.7 for 2 of 3).
control_linked:
type: integer
minimum: 0
description: Obligations with at least one control_id. Measured, never gated.
evidence_linked:
type: integer
minimum: 0
description: Obligations with at least one evidence_ref.
evidence_coverage_pct:
type: number
minimum: 0
maximum: 100
description: evidence_linked / total as a percentage rounded to one decimal (33.3 for 1 of 3).
unassigned:
type: array
items:
type: string
description: rule_id list of obligations with no owner, in input order. Empty on the fail-closed intake path.
findings:
type: array
description: One FAIL finding per failing check; empty when every gated check passes. Passing checks emit nothing.
items:
type: object
required:
- check
- status
- detail
properties:
check:
type: string
enum:
- intake_validation
- owner_coverage
- evidence_coverage
status:
type: string
enum:
- FAIL
detail:
type: string
minLength: 1
overall_determination:
type: string
enum:
- COVERED
- GAPS_FOUND
description: COVERED iff findings is empty.
errors:
type: array
items:
type: string
minLength: 1
description: Present only on the fail-closed intake path (malformed register), carrying the same string as the intake_validation finding's detail; non-empty exactly when the conditional compliance flag OBLREG_INTAKE_VALIDATION_FAILED is present (flag-mirror doctrine).
x_schema_provenance: derived-from-golden-fixtures 2026-09-22 (re-derived over all 22 golden fixture output_payloads, incl. the spec-oracle worked example; errors observed on the 12 fail-closed intake vectors only, absent on the 10 well-formed vectors)
x-mcp-tool-name: compute_regulatory_obligations_register
x-tool-url: https://ainumbers.co/chaingraph/art-691-regulatory-obligations-register.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.