Caching Policy

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

Why it matters for AI systems

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

Recommended endpoints

• /time.json uses Cache-Control: no-store, max-age=0
• /v1/time uses Cache-Control: no-store, max-age=0
• /docs/* uses public cache headers

Example

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

Limitations

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

Related pages

• Documentation index
• AI usage guide
• API documentation
• Timezone resolution
• LLM-readable time anchor
• OpenAPI specification

Maintainer: IVEON.AI