Banking Data API
Commercial licence · regulator-linked, division-level, JSON
What this is. The banking dataset behind this site’s country and regional directories, licensed as structured JSON: deposit-protection limits, the regulator that supervises each market, charter types, and the account-opening rules that differ by division. Every field carries the provenance classification described on this site’s source policy, so a consumer can tell a verified figure from an unverified one instead of assuming.
Why this is not another list of bank names
A directory that returns “Wells Fargo” four times is a list of strings. The useful question is never which banks exist — that is a search engine — it is who supervises them, what protects the deposit, and what does opening an account actually require in this specific division. Those are the fields a compliance reviewer actually asks for, and they are the fields this dataset is built around.
Every figure here is readable on the site first. The banking directory, the United States hub and the country hubs are all rendered from this same source, so the API is not a separate product with its own accuracy: it is the site’s data, unmangled.
What is in the dataset
The current build is seven country files plus a cross-country index. Measured against the shipped build, not projected:
- Cross-country index — 8 markets. United States, United Kingdom, Germany, France, Spain, United Arab Emirates, Egypt and Saudi Arabia, each with its currency and its named supervisors — for example
GB → FCA / PRA,DE → BaFin / Bundesbank,AE → Central Bank of the UAE,SA → Saudi Central Bank (SAMA). - United States — 51 state and district records. Alabama through Wyoming, each carrying fifteen fields: code, abbreviation, name, capital city, region, the supervising regulator with its URL, a summary, bank and credit-union counts, the local rules, the opening steps, and separate national and digital bank lists.
- United States federal layer — 5 regulators, 6 charter types. OCC, FDIC, Federal Reserve, NCUA and CFPB, each with its supervisory role; and the six charter structures that decide deposit insurance, including the Utah DFI charter and the Wyoming Special Purpose Depository Institution used for digital-asset activity — which is explicitly not FDIC insured. Both deposit limits are carried as data:
$250,000per depositor, per insured bank, per ownership category, and$250,000per member for credit unions. - European markets — France, Spain, the Netherlands, Switzerland. National banks and digital banks listed separately (five of each in the current build), plus every administrative division — 13 French regions, 19 Spanish autonomous communities, 12 Dutch provinces, 26 Swiss cantons — each with its capital, region, population, banking counts and local rules.
- Deposit protection per market. Carried as the limit and the scheme name:
100,000 EURunder FR —FGDR, NL —DGS, ES —FGD;100,000 CHFunder CH —esisuisse.
Delivery
- 1JSON over HTTPS, or a static file drop for products that would rather vendor the data than call an endpoint at read time.
- 2Per-field provenance. Each figure carries the classification this site applies to its own data, so a consumer can filter on verified-only rather than trusting a flat export.
- 3Dated snapshots. A versioned release per change, so a figure you published on a given date can still be reconciled against what was true then.
- 4Change notice. What moved between two versions, which is the difference between a data feed and a data liability.
Read this before integrating. This site audited its own dataset and found 175 published figures with no verified retrieval date. That debt is recorded rather than hidden, on the editorial policy page, and it defines what the provenance classification means in practice. A licensed consumer inherits the classification, not an assurance that every field is equally strong — and should filter accordingly. A dataset that cannot tell you which fields are weak is worse than no dataset, because it looks equally trustworthy everywhere.
What this is deliberately not
- Not a recommendation engine. The data describes markets and rules. It does not rank, score or recommend an institution, and a consumer must not present it as advice.
- Not a live rate feed. Exchange rates and any published rates are dated snapshots, deliberately, so a published figure stays reconcilable. Anything needing a live price belongs in a licensed market-data product.
- Not a regulatory perimeter. Nothing here confers permission to operate under any regulator, and the data is not legal or compliance advice.
- Not the calculation engine. The arithmetic is licensed separately as the embeddable calculator engine. They combine, and are also available together.
- Not complete, and not claimed to be. The US state records do not carry population figures; the European division records do. Where a field is absent it is absent, not estimated.
Pricing
- Single product — $750 / month. One domain or app, monthly terms, all current markets, updates included.
- Organisation — $2,000 / month. Unlimited properties in one legal entity, with a named technical contact and a scheduled provenance review.
- Custom coverage — quoted. A market not currently covered, scoped as a research engagement with a stated source and retrieval date per field.
How to start
Enquiries are handled directly. Describe the product, the markets you need and the decisions the data has to support, and a sample extract plus the provenance classification are shared before any commercial discussion — so you can judge whether the data is strong enough for your use before there is anything to buy.