- Every answer to a key is
Cache-Control: private, no-storewithVary: Authorization. No shared cache or proxy may keep it, since every answer is for one key and some carry personal fields. - Your own cache is fine. Keep what you fetch for at least the route's freshness: an answer can be that old on our side anyway, so asking again sooner returns the same data and costs the same units.
| Freshness | Routes |
|---|---|
| Up to 1 hour | Genres, fandoms and tags |
| Up to 10 minutes | Popular |
| Up to 1 minute | A novel's chapter list |
| Live | Everything else: search, a novel, glossaries, recaps, your library, place, notifications and limits |
"Live" means read when you ask. It does not mean it changes often: a novel's page facts and its glossary change rarely, and a few times a day is plenty for most tools. See Keeping in sync for what changes when.
- Errors carry
no-storetoo. Do not keep them; ask again later (afterRetry-After, for a 429 or a 503). - Without a key, the routes are the website's own and are cached for the site, not for you. They are not a supported API.
- The connector,
/mcp, and the sign-in pages under/oauth/are never cached anywhere.