The London Stock Exchange and DataBP have announced a programme to make the administrative records behind market-data licences more accessible to customer software. The 8 October release describes DataBP's Licensing Ledger providing structured licensing inventory, billing history and invoice information through REST interfaces and a Model Context Protocol server. That is different from the exchange giving away the underlying prices, trades or licensed datasets themselves.[1][2]
For a brokerage or professional data consumer, cost is often driven by both the feed and how many systems, users, locations or redistribution channels are permitted to access it. A licence may specify display rights, non-display use, derived data and reporting duties in terms that do not sit neatly in an operational spreadsheet. The new approach is designed to let customers query the authoritative commercial record programmatically, subject to their own permissions.[1]
The disclosed features include access to entitlement details, usage terms, invoice line items and billing history. The MCP interface is intended to allow AI assistants to ask questions against those same structured records, rather than compose answers based on out-of-date copies of licence documents. A useful workflow is checking a charge against a named entitlement, while ensuring that the response is drawn from an authorised account context.[1]
Market-data administration: information versus permission
The supplier emphasises authenticated and entitlement-scoped access through the customer portal. This is a material condition. It does not follow that a connected AI model has unrestricted rights to the prices or analytical content covered by the contract. Nor should the ability to retrieve an invoice line automatically allow a user to alter licences, approve bills or redistribute data to third parties.[1]
The underlying business problem is concrete: an exchange may have one record of licensed use, while the customer tracks entitlements, users and invoices in separate internal tools. Reconciliation across these records is manual and prone to disagreement about which licence is in force. DataBP describes using common structured fields to make those comparisons less burdensome, but the companies have not provided an independent measure of aggregate cost savings.[1]
Market-data administration: information versus permission
| Record or capability | Available in announced design | Not implied |
|---|---|---|
| Licence inventory | Structured customer entitlement data | New data redistribution rights |
| Invoices and billing history | Programmatic reconciliation | Automatic bill approval |
| REST interface | Authenticated software access | Unauthenticated public API |
| MCP interface | AI-assisted queries of authorised records | Unrestricted access to exchange feeds |
For brokers, the practical value is better evidence of what may be used and billed within each service. That is particularly relevant where data supports websites, white-label trading platforms, derivatives pricing tools and automated analytics. The parties' announcement describes an automation foundation; detailed operating controls, coverage and reliability should be tested before any firm delegates financial approval or contractual interpretation to an agent.[1]
Sources & further reading
- Making market data administration simpler with AI-ready licensing intelligence London Stock Exchange Group · 8 Oct 2026 · Accessed 31 Oct 2026
- LSEG Partners with DataBP on AI-enablement DataBP · 9 Oct 2026 · Accessed 31 Oct 2026