AINumbers.co FIDA API
The FIDA API from AINumbers.co — 5 operation(s) for fida.
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-fida-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 FIDA 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: FIDA
paths:
/v1/tools/score_fida_open_finance_readiness:
post:
operationId: score_fida_open_finance_readiness
summary: EU FIDA / Open Finance Readiness Scorer
description: 'Horizon-readiness scorer for the draft EU Financial Data Access Regulation (FIDA): classifies entity and data-category scope under the Commission proposal COM(2023) 360 and Council General Approach (Dec 2024), scores FDSS membership and permission-dashboard readiness, and compares against US CFPB 1033. Draft-law tool — FIDA is not adopted as of 2026-06-06.
**Tool URL:** https://ainumbers.co/tools/273-fida-open-finance-readiness.html
**AP2/Policy Mandate export:** yes'
tags:
- FIDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
entity_type:
type: string
role:
type: string
data_categories:
type: array
items:
type: string
required:
- entity_type
- role
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
in_scope:
type: boolean
scope_reason:
type: string
readiness_score:
type: number
rag_status:
type: string
enum:
- GREEN
- AMBER
- RED
gaps:
type: array
draft_law:
type: boolean
x-mcp-tool-name: score_fida_open_finance_readiness
x-tool-url: https://ainumbers.co/tools/273-fida-open-finance-readiness.html
x-source: manifest
x-ap2-export: true
/v1/tools/map_fida_open_finance_data_scope:
post:
operationId: map_fida_open_finance_data_scope
summary: FiDA Open Finance Data Access Scope Mapper
description: 'Map FiDA obligations, in-scope data categories, FDSS participation, and API readiness for EU open finance 2027+.
**Tool URL:** https://ainumbers.co/tools/360-fida-open-finance-data-scope-mapper.html
**AP2/Policy Mandate export:** yes'
tags:
- FIDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
entity_type:
type: string
required:
- entity_type
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
x-mcp-tool-name: map_fida_open_finance_data_scope
x-tool-url: https://ainumbers.co/tools/360-fida-open-finance-data-scope-mapper.html
x-source: manifest
x-ap2-export: true
/v1/tools/assess_fida_fip_authorisation_readiness:
post:
operationId: assess_fida_fip_authorisation_readiness
summary: FIDA FIP Authorisation Readiness Builder
description: 'Gaps FIP licence applications against EU FIDA Regulation Articles 14-25. Readiness score 0-100 with authorisation timeline and technical standards.
**Tool URL:** https://ainumbers.co/tools/407-fida-fip-authorisation-readiness-builder.html
**AP2/Policy Mandate export:** yes'
tags:
- FIDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties: {}
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
result:
type: object
summary:
type: string
x-mcp-tool-name: assess_fida_fip_authorisation_readiness
x-tool-url: https://ainumbers.co/tools/407-fida-fip-authorisation-readiness-builder.html
x-source: manifest
x-ap2-export: true
/v1/tools/check_fida_permission_scheme_scope:
post:
operationId: check_fida_permission_scheme_scope
summary: FIDA Permission Scheme Scope Checker
description: 'Maps data categories to FIDA permission scheme vs PSD2/open banking obligations. In Scope / Out of Scope / Existing Obligation per data type.
**Tool URL:** https://ainumbers.co/tools/408-fida-permission-scheme-scope-checker.html
**AP2/Policy Mandate export:** yes'
tags:
- FIDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties: {}
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
result:
type: object
summary:
type: string
x-mcp-tool-name: check_fida_permission_scheme_scope
x-tool-url: https://ainumbers.co/tools/408-fida-permission-scheme-scope-checker.html
x-source: manifest
x-ap2-export: true
/v1/tools/map_fida_cross_sector_data_scope:
post:
operationId: map_fida_cross_sector_data_scope
summary: FIDA Cross-Sector Data Scope Mapper
description: 'Maps insurance, pension, mortgage, and investment data into FIDA scope with Phase 1/2/3 implementation timeline per sector and standardisation body.
**Tool URL:** https://ainumbers.co/tools/410-fida-cross-sector-data-scope-mapper.html
**AP2/Policy Mandate export:** yes'
tags:
- FIDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties: {}
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
result:
type: object
summary:
type: string
x-mcp-tool-name: map_fida_cross_sector_data_scope
x-tool-url: https://ainumbers.co/tools/410-fida-cross-sector-data-scope-mapper.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.