Banking Regulation
Banking regulation encompasses the rules, standards, and frameworks governing banks and financial institutions. Key frameworks include the Basel Accords (Basel I, II, III, IV) for capital adequacy, the Dodd-Frank Act in the US, PSD2 and CRD IV/V in Europe, and anti-money laundering (AML) / know-your-customer (KYC) requirements. Regulatory technology (RegTech) APIs and data services help financial institutions automate compliance reporting, risk management, and supervisory data submissions.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Banking Regulation the way a machine reads it — 19 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Banking Regulation scores 21.4/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Banking Regulation
Each block below is one kind of artifact we hold for Banking Regulation. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Features 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Capital Adequacy Reporting
APIs and platforms for Basel III risk-weighted asset and capital ratio calculations.
AML Transaction Monitoring
Real-time transaction screening and suspicious activity reporting.
KYC Onboarding
Identity verification, sanctions screening, and beneficial ownership APIs.
Regulatory Reporting
Automated generation of supervisory reports (FINREP, COREP, FR Y-9C).
Stress Testing
Scenario analysis and stress testing platforms for regulatory capital requirements.
Compliance Data Management
Data lineage, audit trails, and regulatory change management solutions.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Banking Regulation Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Banking Regulation API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
RegulatoryReport
JSON SCHEMASecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 9
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Basel III / IV
International capital adequacy, leverage, and liquidity standards for banks.
Dodd-Frank Act
US financial reform legislation covering derivatives, systemic risk, and consumer protection.
PSD2
EU Payment Services Directive 2 governing open banking and payment security.
CRD IV / V
EU Capital Requirements Directive for bank capital, liquidity, and governance.
AML / BSA
Anti-Money Laundering and Bank Secrecy Act compliance and reporting requirements.
KYC
Know Your Customer identity verification and due diligence requirements.
DORA
Digital Operational Resilience Act for ICT risk in EU financial services.
CCAR / DFAST
US Comprehensive Capital Analysis and Review stress testing requirements.
FRTB
Fundamental Review of the Trading Book market risk capital requirements.
Scroll within the panel for all 9 ·
Resources
Every other property we hold for Banking Regulation — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Company 5
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/banking-regulation · machine-readable index on apis.io