AINumbers.co Vi DA API
The ViDA API from AINumbers.co — 7 operation(s) for vida.
The ViDA API from AINumbers.co — 7 operation(s) for vida.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/ainumbers-co:ainumbers-co-vida-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: AINumbers.co Fintech Intelligence Suite Vi DA 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: ViDA
paths:
/v1/tools/classify_vida_deemed_supplier_scope:
post:
operationId: classify_vida_deemed_supplier_scope
summary: ViDA Deemed Supplier VAT Scope & Liability Classifier
description: 'Classifies whether an online platform falls within the ViDA deemed supplier provisions (effective 1 July 2028, Art.9a accommodation, Art.9b transport). Determines VAT liability, OSS registration requirements, and B2B exemption applicability.
**Tool URL:** https://ainumbers.co/tools/345-vida-deemed-supplier-classifier.html
**AP2/Policy Mandate export:** yes'
tags:
- ViDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
platform_type:
type: string
eu_countries:
type: integer
annual_gmv_eur:
type: number
supplier_type:
type: string
required:
- platform_type
- eu_countries
- annual_gmv_eur
- supplier_type
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
deemed_supplier_applies:
type: boolean
vat_liability_estimate_eur:
type: number
oss_required:
type: boolean
compliance_gap_count:
type: integer
x-mcp-tool-name: classify_vida_deemed_supplier_scope
x-tool-url: https://ainumbers.co/tools/345-vida-deemed-supplier-classifier.html
x-source: manifest
x-ap2-export: true
/v1/tools/validate_vida_einvoice_conformance:
post:
operationId: validate_vida_einvoice_conformance
summary: ViDA EN 16931 E-Invoice Conformance Validator
description: 'Validate a structured e-invoice against EN 16931-1:2026 mandatory fields for ViDA (EU 2025/516) conformance: invoice number, date, ISO 4217 currency, seller name, buyer name, seller VAT ID, VAT breakdown with valid category code, and total with VAT. Returns conformant/vida_ready verdicts and list of missing fields. Root node of the vida-digital-reporting-requirements chain. Zero network, zero PII.
**Tool URL:** https://ainumbers.co/chaingraph/art-159-vida-einvoice-en16931-conformance-validator.html
**AP2/Policy Mandate export:** yes'
tags:
- ViDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
invoice:
type: object
properties:
invoice_number:
type: string
invoice_date:
type: string
description: YYYY-MM-DD
currency_code:
type: string
description: ISO 4217 3-char
seller_name:
type: string
buyer_name:
type: string
seller_vat_id:
type: string
syntax_id:
type: string
description: EN 16931 syntax identifier URI
vat_breakdown:
type: array
items:
type: object
properties:
category_code:
type: string
total_with_vat:
type: number
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
conformant:
type: boolean
vida_ready:
type: boolean
syntax_id_valid:
type: boolean
mandatory_fields_checked:
type: number
missing_fields:
type: array
items:
type: string
currency_code:
type:
- string
- 'null'
total_with_vat:
type: number
x-mcp-tool-name: validate_vida_einvoice_conformance
x-tool-url: https://ainumbers.co/chaingraph/art-159-vida-einvoice-en16931-conformance-validator.html
x-source: manifest
x-ap2-export: true
/v1/tools/assess_vida_drr_reporting_obligation:
post:
operationId: assess_vida_drr_reporting_obligation
summary: ViDA DRR Transaction Reporter
description: 'Assess whether a B2B transaction falls under ViDA Digital Reporting Requirements (DRR): check intra-EU cross-border B2B scope, calculate 10-day reporting deadline from invoice date, and verify data-element completeness (seller/buyer VAT IDs, transaction value). Returns drr_in_scope, reporting_deadline, and data_elements_ok. Middle node of the vida-digital-reporting-requirements chain. Zero network, zero PII.
**Tool URL:** https://ainumbers.co/chaingraph/art-160-vida-drr-transaction-reporter.html
**AP2/Policy Mandate export:** yes'
tags:
- ViDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
transaction:
type: object
properties:
supply_type:
type: string
seller_member_state:
type: string
buyer_member_state:
type: string
seller_vat_id:
type: string
buyer_vat_id:
type: string
invoice_date:
type: string
transaction_value:
type: number
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
drr_in_scope:
type: boolean
intra_eu:
type: boolean
is_b2b:
type: boolean
seller_member_state:
type:
- string
- 'null'
buyer_member_state:
type:
- string
- 'null'
reporting_deadline:
type:
- string
- 'null'
mandatory_from:
type: string
transaction_value:
type: number
data_elements_ok:
type: boolean
x-mcp-tool-name: assess_vida_drr_reporting_obligation
x-tool-url: https://ainumbers.co/chaingraph/art-160-vida-drr-transaction-reporter.html
x-source: manifest
x-ap2-export: true
/v1/tools/assess_vida_recapitulative_migration:
post:
operationId: assess_vida_recapitulative_migration
summary: ViDA Recapitulative Statement Migration Assessor
description: 'Assess readiness to migrate from EC Sales Lists (recapitulative statements) to ViDA Digital Reporting Requirements: check mandatory ESL fields (seller_vat_id, buyer_vat_id, reporting_period, supply_type), identify data gaps, and surface the applicable harmonization deadline (2030-07-01 or 2035-01-01 for pre-2024 domestic regimes). Terminal node of the vida-digital-reporting-requirements chain. Zero network, zero PII.
**Tool URL:** https://ainumbers.co/chaingraph/art-161-vida-recapitulative-statement-migration-assessor.html
**AP2/Policy Mandate export:** yes'
tags:
- ViDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
regime:
type: object
properties:
pre2024_domestic:
type: boolean
seller_vat_id:
type: string
buyer_vat_id:
type: string
reporting_period:
type: string
supply_type:
type: string
transaction_value:
type: number
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
harmonize_deadline:
type: string
pre2024_domestic:
type: boolean
esl_fields_assessed:
type: number
drr_gap_fields:
type: array
items:
type: string
gap_count:
type: number
migration_ready:
type: boolean
transaction_value:
type: number
x-mcp-tool-name: assess_vida_recapitulative_migration
x-tool-url: https://ainumbers.co/chaingraph/art-161-vida-recapitulative-statement-migration-assessor.html
x-source: manifest
x-ap2-export: true
/v1/tools/classify_vida_platform_deemed_supplier:
post:
operationId: classify_vida_platform_deemed_supplier
summary: ViDA Platform Deemed Supplier Classifier
description: 'Classify a digital platform as a ViDA deemed supplier under Art. 46a (amended VAT Directive): short-term accommodation (≤30 consecutive nights) or intra-EU road passenger transport where the underlying supplier has no valid VAT ID causes VAT liability to transfer to the platform. Returns deemed_supplier verdict, sector_eligible, and applicable deadline (mandatory 2028-07-01, MS extension option 2030-01-01). Root node of the vida-platform-and-registration chain. Zero network, zero PII.
**Tool URL:** https://ainumbers.co/chaingraph/art-162-vida-platform-deemed-supplier-classifier.html
**AP2/Policy Mandate export:** yes'
tags:
- ViDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
platform:
type: object
properties:
sector:
type: string
duration_nights:
type: number
supplier_has_valid_vat_id:
type: boolean
intra_eu_supply:
type: boolean
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
deemed_supplier:
type: boolean
sector:
type: string
sector_eligible:
type: boolean
supplier_has_valid_vat_id:
type:
- boolean
- 'null'
intra_eu_supply:
type: boolean
duration_nights:
type:
- number
- 'null'
mandatory_from:
type: string
ms_extension_option:
type: string
x-mcp-tool-name: classify_vida_platform_deemed_supplier
x-tool-url: https://ainumbers.co/chaingraph/art-162-vida-platform-deemed-supplier-classifier.html
x-source: manifest
x-ap2-export: true
/v1/tools/route_vida_oss_registration:
post:
operationId: route_vida_oss_registration
summary: ViDA OSS Registration Router
description: 'Route a supply to the correct ViDA Single VAT Registration scheme: Union OSS (EU-established supplier, cross-border B2C or stock transfer within EU), Non-Union OSS (non-EU digital or deemed services to EU consumers), IOSS (non-EU goods ≤EUR 150 to EU consumers), or Domestic VAT (same-MS supply). ViDA extends Union OSS coverage from 2028-07-01. Returns recommended_scheme, scheme_rationale, and eligible_for_oss. Middle node of the vida-platform-and-registration chain. Zero network, zero PII.
**Tool URL:** https://ainumbers.co/chaingraph/art-163-vida-oss-registration-router.html
**AP2/Policy Mandate export:** yes'
tags:
- ViDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
supply:
type: object
properties:
supply_type:
type: string
seller_establishment:
type: string
destination_member_state:
type: string
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
recommended_scheme:
type:
- string
- 'null'
scheme_rationale:
type:
- string
- 'null'
eligible_for_oss:
type: boolean
supply_type:
type: string
seller_establishment:
type:
- string
- 'null'
destination_member_state:
type:
- string
- 'null'
seller_in_eu:
type: boolean
dest_in_eu:
type: boolean
x-mcp-tool-name: route_vida_oss_registration
x-tool-url: https://ainumbers.co/chaingraph/art-163-vida-oss-registration-router.html
x-source: manifest
x-ap2-export: true
/v1/tools/run_vida_readiness_diagnostic:
post:
operationId: run_vida_readiness_diagnostic
summary: ViDA Compliance Readiness Diagnostic
description: 'Scored ViDA readiness diagnostic across four dimensions: einvoice (EN 16931-1:2026 ready), drr (DRR reporting pipeline ready), platform (deemed-supplier assessed or not applicable), and oss (OSS/SVR scheme configured or not applicable). Returns readiness_score (0–100), gaps list, fully_ready boolean, and phased obligation timeline (2028-07-01 platform+SVR, 2030-07-01 DRR+e-invoice mandatory, 2035-01-01 legacy regime harmonization). Terminal node of the vida-platform-and-registration chain. Zero network, zero PII.
**Tool URL:** https://ainumbers.co/chaingraph/art-164-vida-compliance-readiness-diagnostic.html
**AP2/Policy Mandate export:** yes'
tags:
- ViDA
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
entity:
type: object
properties:
einvoice_ready:
type: boolean
drr_ready:
type: boolean
platform_assessed:
type: boolean
platform_not_applicable:
type: boolean
oss_scheme_configured:
type: boolean
oss_not_applicable:
type: boolean
responses:
'200':
description: Successful tool execution result
content:
application/json:
schema:
type: object
properties:
readiness_score:
type: number
fully_ready:
type: boolean
dimensions_met:
type: number
dimensions_total:
type: number
gaps:
type: array
items:
type: string
timeline_obligations:
type: array
items:
type: object
properties:
date:
type: string
scope:
type: string
x-mcp-tool-name: run_vida_readiness_diagnostic
x-tool-url: https://ainumbers.co/chaingraph/art-164-vida-compliance-readiness-diagnostic.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.