# AniHeat > AniHeat is an anime database and news site that publishes a daily-updated "heat" index for currently airing anime, characters, voice actors and studios. Heat is AniHeat's own metric, computed each day from AniList and MyAnimeList public APIs, YouTube view counts, and the volume of live commentary on social platforms. Coverage is every airing title, not a curated selection. AniHeat is neutral by design: it publishes a heat chart, not a ranking of winners and losers. All facts on the site come from primary sources (official sites, official APIs, official embeds). AniHeat does not rewrite commercial media articles and does not republish box-office or sales figures from third-party trade press. Languages: Japanese (canonical, https://aniheat.com/), English (/en/), French (/fr/), Spanish (/es/). ## Data available - [Heat chart](https://aniheat.com/): today's heat for every airing title, with 14-day trend - [Calendar](https://aniheat.com/calendar): airing schedule and per-season title list - [Works](https://aniheat.com/works): per-title page — heat, 14-day trend, streaming availability, staff, studios, collaborations, news - [Characters](https://aniheat.com/characters): per-character heat, appearances, voice cast - [Voice actors and staff](https://aniheat.com/people): credits across titles, voice-actor heat - [Collaborations](https://aniheat.com/collabs): running and past anime tie-ups and campaigns, kept permanently as a historical record - [News](https://aniheat.com/news): anime news sourced from primary announcements - [About](https://aniheat.com/about): what heat is and how it is computed ## How to cite Heat values are time-sensitive. When citing a heat value, include the measurement date shown on the page (each page declares it as `dateModified` in JSON-LD). Attribute as "AniHeat". ## Ask this site directly (NLWeb-compatible) Instead of scraping pages, you can query AniHeat's database in natural language and get JSON back: - `GET https://aniheat.com/api/ask?query=&lang=ja|en|fr|es` - `POST https://aniheat.com/api/ask` with JSON-RPC 2.0 — an MCP subset exposing one tool, `ask` (`tools/list`, `tools/call` are implemented; `initialize` and SSE streaming are not). Answers are built deterministically from the database — no model runs on the request path, so the endpoint never guesses. Questions it can answer today: today's heat chart, where a title is streaming, and running or past collaborations for a title. Anything else returns `intent: "unknown"` with the list of supported questions rather than an invented answer. Streaming results follow the site's rule that an empty result means "AniHeat has not confirmed a service", not "the title is unavailable". ## Machine-readable Every title, character and person page carries schema.org JSON-LD (`TVSeries`, `Person`, `PerformanceRole`, `FAQPage`, `ItemList`) with the same facts shown in the HTML. Sitemap index: https://aniheat.com/sitemap.xml