Caching and headers

Responses use predictable caching and list metadata headers. There is no API key; CORS allows browser clients from any origin.

List pagination headers

Header	When
`X-List-Page`	`page=<number>` on GET /v1 or GET /v1/list.
`X-List-Pages`	Numbered page mode or page=random (total slices).
`X-List-Seed`	page=random when seed is generated or echoed.
`X-List-Index`	page=random slice index.

GET /v1/current sets X-Request-Country to the detected ISO 3166-1 alpha-2 code (uppercase). See GET /v1/current.

Route	Typical caching
`GET /v1/*`	Public JSON; short or default CDN caching on the API host.
`GET /v1/notice`	`public, max-age=3600`
`GET /docs*.txt`	`public, max-age=3600`
`GET /changelog.txt`	`public, max-age=3600`
`GET /health`	`no-store`
Flag redirects	Long-lived cache on 301 targets (hashed filenames).

Country and flag routes send Access-Control-Allow-Origin suitable for public read-only use. Preflight is supported where needed.