Versioning Policy

LIVEUTC.AI exposes simple endpoints and versioned API endpoints.

Why it matters

Versioned endpoints help developers and AI agents build stable integrations.

Recommended endpoints

• /v1/time.json
• /v1/time
• /v1/status

Example

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

Scope

Once published, V1 response structures should not be broken. Breaking changes require /v2/.

V1 stability rule

• Existing fields will not be renamed.
• Existing fields will not be removed.
• Existing field types will not be changed.
• Optional fields may be added.
• Breaking changes require a new version path.

Related pages

• Documentation index
• Trust and reliability
• AI usage guide
• API documentation
• LLM-readable time anchor
• OpenAPI specification

Maintainer: IVEON.AI