Litecoin RegisterData & API
Every endpoint below is a static file. No API key is required, every client receives the same response, and the data is licensed CC BY 4.0.
| Path | Format | Contents |
|---|---|---|
/api/v1/entities.json | JSON | Every holder, with full holding history and sources. |
/api/v1/entities/binance-exchange.json | JSON | One holder. Replace the ID with any holder’s ID. |
/api/v1/categories/exchanges.json | JSON | Holders in one category. |
/api/v1/categories/exchanges/centralized-exchange.json | JSON | Holders 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 a holder record. |
/api/v1/openapi.json | OpenAPI 3.1 | Description of every endpoint on this page. |
/data/entities.csv | CSV | One row per holder, with its current holding. |
/data/holdings.csv | CSV | One row per reported figure (long format, for time series). |
/data/entities/binance-exchange.csv | CSV | Every reported figure for one holder. |
/data/addresses/binance-exchange.csv | CSV | One holder’s attributed addresses (address, label, attribution), for holders that have any; see address_count. |
/data/series/entities/binance-exchange.json | JSON | One holder’s figures as compact [date, LTC] pairs, as used by its 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 behind every USD value on the site. |
/datapackage.json | Data Package | Frictionless Data descriptor for both CSV files. |
/entities/binance-exchange.md | Markdown | One holder as Markdown with YAML front matter. |
/llms.txt | llms.txt | A 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 carry their payload in data, with schema_version, generated_at, license and links to the documentation and schema. Dates are YYYY-MM-DD strings and amounts are decimal numbers in whole LTC. Missing optional values are null rather than omitted, so every record has the same keys.
Example
curl -s https://litecoinregister.com/api/v1/entities/binance-exchange.json | jq '.data.current_holding'