feat(platform): standardize exchange inputs with ISO 10383 MIC codes

[sandole]

Pull Request for OpenBB Platform

Description

• Summary: Add an Exchange type that standardizes exchange inputs across providers using ISO 10383 Market Identifier Codes (MIC).
• Link: Partially addresses [IMPROVE] obb.equity.screener: Make Input Of Country & Exchange Uniform Across Providers #6969
• Motivation: Consistent with the Country type approach from PR feat(platform): standardize country inputs with ISO 3166 Country type #7333, this provides uniform exchange input handling across all providers.

Features

Following the same pattern as Country, the Exchange type:

• Inherits from str (storing the MIC code) for type checker compatibility
• Accepts multiple input formats:
  • ISO 10383 MIC codes (e.g., XNAS, XNYS)
  • Exchange acronyms (e.g., NASDAQ, NYSE)
  • Full exchange names (e.g., New York Stock Exchange)
  • lower_snake_case names (e.g., new_york_stock_exchange)
• Provides properties: mic, acronym, name, city, country, website
• Uses ExchangeData TypedDict for proper type inference
• Includes enriched metadata from ISO 10383: city (title-cased), country (ISO alpha_2), and website (normalized with https://)
• 2,272 active MICs with 100% city/country coverage and 98% website coverage

Example Usage

from openbb_core.provider.utils.exchange_utils import Exchange

e = Exchange("nasdaq")
str(e)      # "XNAS"
e.mic       # "XNAS"
e.acronym   # "NASDAQ"
e.name      # "NASDAQ - ALL MARKETS"

e = Exchange("XNYS")
e.mic       # "XNYS"
e.acronym   # "NYSE"
e.name      # "NEW YORK STOCK EXCHANGE, INC."

Sample JSON Entry

{
  "mic": "XNYS",
  "acronym": "NYSE",
  "name": "NEW YORK STOCK EXCHANGE, INC.",
  "city": "New York",
  "country": "US",
  "website": "https://www.nyse.com"
}

Files Added/Modified

• openbb_core/provider/utils/exchange_data.json — Full ISO 10383 dataset (2,272 active MICs) with city, country (ISO alpha_2), and website fields
• openbb_core/provider/utils/exchange_utils.py — Exchange type implementation with ExchangeData TypedDict
• tests/provider/utils/test_exchange_utils.py — Unit tests (13 test cases)
• scripts/update_exchange_data.py — Script to regenerate exchange data from official ISO 20022 source (stdlib only, no external dependencies)

Type Safety

Uses TypedDict for proper type inference (consistent with CountryData pattern from #7352):

class ExchangeData(TypedDict, total=False):
    mic: str
    acronym: str
    name: str
    city: str
    country: str
    website: str

How has this been tested?

• Manually tested Exchange type creation and property access
• Unit tests cover MIC codes, acronyms, full names, snake_case, case insensitivity, whitespace handling
• Syntax and JSON validation passing

Checklist

• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have adhered to the GitFlow naming convention.
• I ensure that I am following the CONTRIBUTING guidelines.
• I have added tests.

[deeleeramone]

Thanks for picking this up. The implementation looks good, but the JSON data seems like it is missing a lot of entries. There are no Cboe markets in there, just to name one company. There should be closer to 2000 items in this ISO.

[sandole]

Good point on completeness - I updated the exchanges JSON to include CBOE and a few more. I did look into pulling the full ISO 10383 list (~1,300 operating MICs, ~2,200 with segments).

Question: what's the practical value of including exchanges beyond the major ~66? Most data providers (FMP, Polygon, Intrinio, etc.) only support major venues. Including 1,300+ MICs means we'd validate inputs that no provider can actually serve data for.

My proposals:

1. Keep curated major exchanges (current) — practical but incomplete
2. Full ISO list — complete but accepts unusable inputs
3. Full list + tier field to distinguish major/regional/mtf — best of both?

I've got a script ready to pull from the official source for whichever way.

[deeleeramone]

Question: what's the practical value of including exchanges beyond the major ~66?

If you have a CTA feed or assets other than stocks, there will be all kinds of MICs that you will never encounter as an individual. Options, futures, commodities, indices, financial derivatives, bonds, etc. all have their own markets and codes.

Exchange code mapping, IMO, is useful for processing raw market data and converting codes into human-readable labels.

[sandole]

updated to pull the full ISO 10383 registry. used the official ISO 20022 source (https://www.iso20022.org/market-identifier-codes). The update script (scripts/update_exchange_data.py) can be re-run anytime the registry updates.

[deeleeramone]

We should probably include city, country, and website in the JSON, eh?