Bitcompare changelog
Follow updates to Bitcompare's API, MCP, data coverage, providers, assets, and methodology.
- Methodology
Methodology hub rebuilt around the Bitcompare trust model
The methodology hub was rebuilt as a single trust reference for both human readers and AI agents. It now leads with the five-rule trust model, defines every rate distinction we hold apart (APY vs APR, base vs max, fixed vs flexible, CeFi vs DeFi), documents the freshness and staleness rules, and adds explicit guidance for API and MCP consumers on preserving freshness, source, and confidence fields.
- Methodology
Sponsored-placements disclosure rewritten as an operational policy
The sponsored-placements page is no longer a generic disclaimer — it now states the operational rules: sponsored placements are always labelled, sponsorship buys visibility but cannot change organic rate data or rankings, and disclosure applies across every surface, including the API and MCP. It also documents the advertiser review policy and a channel for reporting misleading ads.
- MCP
MCP page reworked around the 18-tool catalog
The /mcp landing page was rebuilt for AI agents and the developers who deploy them. The full catalog of 18 MCP tools is now rendered on the page, grouped by the agent job each tool serves, and pricing and access are clarified so it is obvious how to get a key and start calling tools.
- API
Yield API product page rebuilt with a typed example response
The /yield-api page was rebuilt as the canonical API product page. It now shows a typed example response so developers can see the exact shape before signing up, and surfaces the freshness, source, and confidence signals that ship with every rate — the same trust fields the methodology requires downstream consumers to preserve.
- Product
Audience pages for publishers, wallets, exchanges, and fintechs
Four /for/* audience pages shipped, each explaining how that audience uses Bitcompare yield data: publishers embedding rate tables, wallets surfacing in-app yields, exchanges benchmarking their rates, and fintechs building on the API. All four were subsequently rebuilt to the V2 design.
- Product
Rate-table yield cells and badges localized
The crypto rate table now renders its yield cells and badges through the i18n layer with native translations. Labels such as "via", platform counts, and the Best and Verified badges — plus their screen-reader text — were previously hardcoded English in every rate row, one of the largest remaining localization gaps across the roughly 1,700 statically generated rate pages.
- Data coverage
Live streaming prices wired into the yield pages
Live WebSocket price data now feeds /yield-intelligence and /yield-api directly, replacing static snapshots. The interactive demo on those pages was also wired to the production data backend, so the figures shown are the same ones the API serves rather than hardcoded examples.
- Product
Translations completed across all 18 non-English locales
More than 10,800 backfilled interface keys were translated across all 18 non-English locales, replacing English fallbacks with native translations. Footer navigation and homepage sections now render fully localized in every supported language.
- Product
Design system v2.0 rolled out across the site
The site moved to design system v2.0: a reworked visual language with new typography (Space Grotesk headings, JetBrains Mono data labels), an updated color token system, and a rebuilt homepage, navigation, and footer. Commercial and trust pages were progressively re-skinned to the same system in the following days.
Update types
What each kind of changelog entry means for the data you consume.
- Provider added
- A new platform or protocol enters coverage. Its rates are attributed, timestamped, and refreshed like every other source.
- Asset added
- A new coin or token becomes comparable across the providers that support it.
- Endpoint updated
- An API endpoint gains fields, filters, or behavior. Additive changes ship silently; anything else is called out here.
- MCP schema updated
- A tool in the MCP catalog changes its input or output schema. Agents should re-read the tool definitions.
- Methodology changed
- A rule about how rates are defined, collected, refreshed, or disclosed changes. The methodology pages are updated in the same release.
- Rate category expanded
- A product category (lending, staking, borrowing, stablecoin yield, earn) gains new dimensions or coverage.
- Data freshness improvement
- Refresh cadence, staleness detection, or source verification improves for some or all of the dataset.
Developer notes
Our commitments for anyone building against the API or the MCP server:
- Breaking changes are clearly labelled — look for the red "Breaking" badge on the entry.
- Deprecated fields and endpoints include dates, so you know when they stop being served.
- New endpoints link to their documentation so you can adopt them without guesswork.
- Schema changes link to the OpenAPI spec and the MCP docs so machines and agents can re-sync.
Re-sync against the OpenAPI spec or the MCP docs.
Build with current crypto yield data
Live rates with freshness, source, and confidence signals — over the API or the MCP server.