Skip to content
TrueFloat API

Changelog

2026-09-25 — caching and CORS fixes

Section titled “2026-09-25 — caching and CORS fixes”
  • dataset_version also covers the code that derives responses. It is a content hash of the data and of how responses are computed from it (places, counts, aliases, response content), so a fix to a derived field now changes it, and your ETag with it. A docs, formatting or infrastructure deploy still leaves it unchanged. See dataset_version.
  • A 304 Not Modified has no body. It used to carry {}; a client that read a body from a 304 should reuse its cached copy instead. See Caching & conditional requests.
  • CORS headers on every response. Access-Control-Allow-Origin: * and Access-Control-Expose-Headers: ETag, Retry-After are now sent whether or not the request has an Origin, and responses no longer vary on Origin, so one cached copy at the edge serves every caller. See Access & rate limits.

2026-09-25 — v1 launched

Section titled “2026-09-25 — v1 launched”

The public TrueFloat API, https://truefloat.app/api/v1, is live: items, guides, seeds, patterns, resolve, meta, and the bulk /dump endpoint. See Introduction and the API reference.