FIELD GUIDE / 001 · 9 SOURCE ENTRIES
Evidence basis: September 9, 2026. Entry points and boundaries, not a price list or a grant of access.

The institutional data source access map separates public information and software from licensed feeds and participant systems. Each entry identifies what is reachable and the conditions that remain outside that access.

Download Markdown ↗Download JSON ↗

01. SEC EDGAR

Access: Public interface.

Reaches: Company submissions and extracted XBRL information through SEC data APIs. The documented data service requires no API key.

Boundary: This is a filings service. It does not supply a live exchange order book or authorize an order. Observe the service’s current access policies.

Original source: U.S. Securities and Exchange Commission · Read the mechanism

Access: Public reference.

Reaches: Historical and current Legal Entity Identifier records and related reference data.

Boundary: An LEI identifies a legal entity. It does not independently verify every beneficial owner, authorize account access or establish enforceable netting.

Original source: Global Legal Entity Identifier Foundation · Read the mechanism

03. OpenFIGI mappings

Access: Published mapping interface.

Reaches: Mappings between FIGIs and other market identifiers, with the instrument and listing context required by the request.

Boundary: An instrument mapping does not select every venue or identify a transaction counterparty. Service limits and usage terms apply to the actual access arrangement.

Original source: OpenFIGI / Bloomberg · Read the mechanism

04. QuantLib

Access: Open calculation component.

Reaches: A quantitative-finance library with a C++ core and language bindings. It supplies components for constructing financial calculations.

Boundary: The library does not supply every input dataset, validate a financial model or confer trading access. Curves, calendars, units and tolerances remain part of the calculation contract.

Original source: QuantLib Project · Read the mechanism

05. NYSE market feeds

Access: Licensed information product.

Reaches: Defined feeds covering categories such as depth, trades, top-of-book and auction information.

Boundary: Coverage and update semantics differ by product. Access, automated use, redistribution and storage rights require the applicable entitlement and agreement.

Original source: NYSE / ICE · Read the mechanism

06. Bloomberg Server API

Access: Session-bound licensed access.

Reaches: Delivery of licensed Bloomberg information into connected applications under the documented user access arrangement.

Boundary: The retained documentation requires an active Bloomberg Professional session for delivery to the user. An SDK download alone provides no data entitlement or universal retention right.

Original source: Bloomberg · Read the mechanism

07. Broker and venue order interfaces

Access: Authorized participant path.

Reaches: Order entry and status through the supported venue or broker interface and the account’s permitted operations.

Boundary: A public protocol specification is not a membership or account entitlement. Acceptance, execution, allocation and settlement remain separate states.

Original source: Nasdaq · Read the mechanism

08. Fedwire Funds

Access: Settlement service.

Reaches: Real-time gross settlement of eligible obligations through the service’s participation and account arrangements.

Boundary: A customer-facing API does not independently grant rail participation or usable settlement funds. Customer posting and availability rules are separate from the rail event.

Original source: Federal Reserve Financial Services · Read the mechanism

09. CLSSettlement

Access: FX settlement mechanism.

Reaches: Payment-versus-payment settlement for eligible FX payments within the supported service arrangement.

Boundary: Eligibility, participation and funding still need to be established. The settlement mechanism does not eliminate every risk in the underlying transaction.

Original source: CLS · Read the mechanism

How to interpret access

A working interface establishes a technical connection. Information coverage, usage rights, financial permission and usable funding are separate conditions. Check the operative service terms for a concrete use. The source dates above identify the evidence used by this map; they do not imply a live status check.