Data & API
The register is a static site: every endpoint below is a plain file, so there are no API keys, no rate limits beyond your host's, and responses are identical for every client. Records are licensed CC BY 4.0.
| Path | Format | Contents |
|---|---|---|
/api/v1/entities.json | JSON | Every entity with full holding history and sources. |
/api/v1/entities/binance-exchange.json | JSON | One entity. Replace the ID with any entity ID. |
/api/v1/categories/exchanges.json | JSON | Entities in one category. |
/api/v1/categories/exchanges/centralized-exchange.json | JSON | Entities in one subcategory. |
/api/v1/summary.json | JSON | Totals by category and the date range of current figures. |
/api/v1/schema.json | JSON Schema | Field-by-field definition of an entity record. |
/api/v1/openapi.json | OpenAPI 3.1 | Description of every endpoint on this page. |
/data/entities.csv | CSV | One row per entity with its current holding. |
/data/holdings.csv | CSV | One row per holding snapshot (long format, for time series). |
/data/entities/binance-exchange.csv | CSV | Every holding snapshot for one entity. |
/data/addresses/binance-exchange.csv | CSV | One entity’s attributed addresses (address, label, attribution). Only for entities with any; see address_count. |
/data/series/entities/binance-exchange.json | JSON | One entity’s holdings as compact [date, LTC] pairs (used by the chart). |
/data/series/categories/exchanges.json | JSON | A category’s combined holdings over time as [date, LTC] pairs. |
/data/prices/ltc-usd.csv | CSV | Daily LTC/USD prices used for every USD value on the site. |
/datapackage.json | Data Package | Frictionless Data descriptor for both CSV files. |
/entities/binance-exchange.md | Markdown | One entity as Markdown with YAML front matter. |
/llms.txt | llms.txt | Short, linked index of the site for language models. |
/llms-full.txt | Markdown | The whole register in one Markdown file. |
/sitemap-index.xml | XML | Sitemap of every HTML page. |
/robots.txt | Text | Crawler policy. All crawlers, including AI crawlers, are allowed. |
Response envelope
JSON responses wrap their payload in data alongside schema_version,generated_at, license and links to the documentation and schema. Dates areYYYY-MM-DD strings; amounts are decimal numbers in whole LTC. Missing optional values arenull, never omitted, so every record has the same keys.
Example
curl -s https://litecoinregister.org/api/v1/entities/binance-exchange.json | jq '.data.current_holding'