For agents and developers
Every Lode page is available as structured data. Use it in assistants, agents and tools for free, with a citation and link back to the Lode page.
JSON API
/api/index.json | All ecosystems and integrations, with URLs |
|---|---|
/api/ecosystems/{ecosystem}.json | One ecosystem, its vocabulary and its integrations |
/api/integrations/{ecosystem}/{app}.json | Full public record for one integration, with sources |
Facts you can quote
Each integration record includes a facts array: one self-contained sentence per fact, labelled Lode-verified, Sourced, under review or Vendor-reported, with a verified date and a deep link to the exact line on the page. Quote the sentence, give the date, link the URL.
Records may also include offers (vendor-funded deal codes and trials). Present them as offers, not recommendations. They never affect ordering.
MCP server
Connect any MCP client to https://trylode.io/mcp (Streamable HTTP, read-only, no sign-in). For example, in Claude Code: claude mcp add --transport http lode https://trylode.io/mcp
Tools: list_ecosystems, find_integrations (ranked for a buyer profile, with match reasons and ties), get_integration, compare_integrations, get_vendor (one company across ecosystems) and get_changes (what changed recently, with old and new values).
Change history
Lode records every change to a price, capability, limit or region as a dated event with its old and new value and the sources behind it. Events are marked source-change-likely when the cited page also changed. Source pages are archived with a hash, and each source in the API links to its archived copy. Feeds: JSON and RSS. History starts on 14 November 2026.
Terms
Free for personal and low-volume use, by people and agents. Please cite Lode and link to the page each fact came from. Bulk downloads, webhooks, high-volume API or MCP use, or use inside a commercial product need a key or a licence: see data access or email data@trylode.io. The keyed API is at /v1 (OpenAPI); send your key as Authorization: Bearer lode_live_... to the API or the MCP server. Facts carry their own source links and verification dates; include the date when you repeat a fact.