Caching Policy

Live temporal endpoints should not be cached because they return the current time.

Why it matters

LIVEUTC.AI applies no-store headers to live endpoints and public cache headers to stable documentation pages.

Recommended endpoints

/time.json
/v1/time.json
/v1/time
/time.md
/status
/status.md
/v1/status

Example

GET https://liveutc.ai/v1/time.json

Scope

Intermediate proxies should respect cache headers, but clients should avoid reusing old live time responses.

Live endpoint headers

Cache-Control: no-store, max-age=0
Access-Control-Allow-Origin: *
Content-Type: application/json; charset=utf-8

Example curl checks

curl -I https://liveutc.ai/time.json
curl -I https://liveutc.ai/v1/time.json
curl -I https://liveutc.ai/time.md
curl -I "https://liveutc.ai/v1/time?tz=UTC"
curl -I "https://liveutc.ai/v1/time?tz=Europe/London"
curl -I "https://liveutc.ai/v1/time?tz=America/New_York"
curl -I "https://liveutc.ai/v1/time?tz=Asia/Tokyo"
curl -I https://liveutc.ai/status
curl -I https://liveutc.ai/status.md
curl -I https://liveutc.ai/v1/status

Static documentation headers

Cache-Control: public, max-age=3600

Maintainer: IVEON.AI