Last updated
Every change that matters to someone using the charts, the API or the MCP server — newest first, with data corrections stated plainly. Subscribe with the Atom feed; live service health is on the status page.
Atom feed · Service status · SDK releases
The MCP server instructions — the text every client shows its model before the first tool call — now say how fresh the data is: flow and spending metrics are republished after each Bitcoin block as 5-minute buckets (last 30 days), network-activity charts every 30 minutes, daily series once the UTC day is closed. The MCP Registry entry, the Python and TypeScript SDKs (kotecharts 0.2.2) and the stdio bridge (kotecharts-mcp 0.1.4) carry the same description.
Tools, arguments, results and limits are unchanged.
Flow and spending metrics — SOPR, adjusted SOPR, realized profit/loss, coin days destroyed, spent volume, transfer volume, issuance, and exchange, miner, fund and whale flows — are now recalculated and published after every Bitcoin block, typically within a couple of minutes of the block being mined. Their 5-minute buckets (last 30 days, granularity=5m) and the open day therefore move with the chain instead of once a day.
Network-activity charts (transactions, fees, addresses, block statistics) are refreshed every 30 minutes. Daily values are still finalised only after the UTC day is complete, and market data is refreshed once a day.
The home page now shows the latest block the data reflects, how long ago it was mined and when the most requested charts last changed. The same facts are available programmatically: dataPipeline.analysedBlockHeight and processedAt in GET /api/v1/status, asOf and watermark in a chart response, and publishedAt in GET /api/v1/metrics/{id}. Formulas, values and response shapes are unchanged.
Charts: sopr · adjusted-sopr · realized-pnl · coin-days-destroyed · spent-volume · volume · issuance · exchange-netflow · miner-flows · fund-flows · whale-tx-volume · whale-to-exchange · exchange-whale-ratio
Without a key the limit is 60 tool calls per minute per IP — tools/call and reads of kote://charts/{id}. The handshake and discovery requests (initialize, tools/list, resources/list, prompts, ping) now have their own allowance and no longer use up that budget, so a client can always connect and list the tools. Each message of a JSON-RPC batch counts separately. With an API key the limit stays 3 requests per second.
Tools, arguments and results are unchanged.
Charts embedded on other websites with the official widget keep every view and control but no longer show the CSV download button — a widget displays the chart, it does not redistribute the series as a file. The download stays available on kotecharts.com chart pages, and programmatic access is unchanged through the keyed API and the MCP server.
Chart data on the site is now served from a shared in-memory cache with standard HTTP validators (ETag, Cache-Control), so repeated views load faster. Values and response shapes are unchanged.
Section 12 of the Terms of Use now states the data licence in full: personal, educational, research and other non-commercial use at no charge, with required attribution (previously “preferably”). Commercial use needs prior written permission — request a licence. Quoting individual figures or a single chart with attribution is allowed in any article, post or video, and the unmodified official widget may be embedded on any website.
A plain-language summary is on the new data licence page. The site no longer describes itself as “free” without that qualification.
New keyless endpoints: GET /api/v1/health (API + database liveness) and GET /api/v1/status (components, analysed block and its age, public chart counts, stale charts, versions).
Additive response fields: license and attribution on GET /api/v1/public/charts; pageUrl, cite and license on GET /api/v1/public/charts/{id}. Every public response carries Link: <https://kotecharts.com/license>; rel="license". No field was removed or renamed.
list_charts, get_chart and get_latest now return the license URL next to pageUrl and cite; the server instructions state the licence and link the status page. Tools and arguments are unchanged.
The home page (and, before data loaded, the MCP page) counted every chart in the code (127) — including charts withdrawn from the public catalog — and listed a fixed category count. The home page, the catalog, the API docs, the MCP page, the chart sidebar, the API (/api/v1/metrics total), MCP list_charts and /api/v1/status now report the same number of public charts, taken from one definition.
New pages: status (live components and data freshness) and this changelog (also as an Atom feed). The developer landing moved to /bitcoin-onchain-api; the old URL redirects.
The public whale event feed (/whales) and every endpoint that exposed address labels, clusters or scores were switched off. Aggregate exchange and whale charts are unaffected.
API keys are accepted as Authorization: Bearer kote_… as well as X-API-Key; public endpoints allow cross-origin requests; the OpenAPI document has explicit operation ids and named schemas.
New keyless GET /api/v1/metrics and GET /api/v1/metrics/{id}: formula, payload fields with units, input categories, update cadence, known limitations and freshness for every public chart (methodology).
The server is listed as com.kotecharts/charts in the official MCP Registry, with resources kote://catalog, kote://methodology, kote://charts/{id} and two prompts. Open-source SDKs: pip install kotecharts, npm i kotecharts, and the stdio bridge npx -y kotecharts-mcp (GitHub).
The approxSupplyBtc field of the overview payload applied only the first halving and overstated supply (about 29.6 million BTC). It now applies the full halving schedule.
Charts withdrawn from the public catalog are no longer counted, listed in the sitemap or llms.txt, or prerendered. Thirteen charts are currently withdrawn, mostly entity-level and wealth-distribution views.
Daily charts show the still-open UTC day as a clearly marked partial point: flow metrics as a rolling 24 hours ending at the as-of time (comparable with a closed day), level metrics as of that time. In the API it is opt-in with includePartial=true; closed days are unchanged.
Published the public OpenAPI document, llms.txt / llms-full.txt, the methodology, glossary and about pages, and richer MCP answers (page URL, formula, freshness, ready citation).
From 2026-08-08 to 2026-10-27 the daily processing did not backfill intraday (5-minute) BTC prices, so blocks without a price left SOPR, adjusted SOPR, realized profit/loss and related realized metrics empty for those days. The gap was fixed on 2026-10-27 and the affected days were recomputed by 2026-10-30; the daily run now fills missing intraday prices before every build.
Known residue: in older realized-index series, daily profit/loss values for 2026-08-08 – 2026-10-26 were computed with the daily opening price instead of intraday prices and can be distorted for individual days; realized cap and realized price are affected negligibly (about 0.05 %).
Charts: sopr · adjusted-sopr · realized-pnl