Set up a licensed feed of LME reference/settlement metal prices for internal application use
domain: London Metal Exchange (LME) Market Data Licensing · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the market data licensing page on lme.com to determine whether internal-use-only access or a distribution license is required, since LME licenses data differently for internal business use versus redistribution or public display.
Choose an access channel: direct real-time/delayed feeds (LMEsource, LMEselectMD), the day-delayed XML feed, or an authorized third-party distributor (LSEG, ICE, etc.).
For a lightweight integration, subscribe to the LME next-day delayed XML feed, which includes daily reference prices, FX rates, traded volumes, and warehouse stock movement reports.
Integrate the XML feed into internal systems/websites per the licensing terms — confirm whether the intended use (internal dashboard vs. public-facing app) matches the license tier purchased.
For enterprise-grade or cross-reference symbology needs, evaluate LSEG's or ICE's LME data products, which offer both request-response and bulk access alongside desktop/API delivery.
Known gotchas
Real-time or intraday LME prices require a real-time license and are materially more expensive/restricted than the day-delayed feed — confirm latency requirements before committing to a license tier.
Displaying LME data publicly (even derived/calculated values) can trigger the need for a distribution license separate from an internal-use license — read the specific use case against LME's licensing terms before launch.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?