Changelog

Compatibility notes for integrations. This manually maintained page is not a deployment history and does not confirm that a particular source revision is live. Inspect the current endpoint response and discovery documents before relying on an interface.

• Content negotiation. HCRB serves a browser experience and a machine manifest. Request /?format=json explicitly for the manifest rather than parsing browser HTML. Use the agent reference and discovery documents for the supported schema.
• Credential-bearing requests. API paths on this domain relay to HCRB with the caller's method, headers and body, rather than using a cross-origin redirect that can strip Authorization. New integrations should use https://hcrb.in directly. Read-only discovery documents redirect to their canonical HCRB destination.
• Health endpoints. /healthz uses the machine relay. The human /health link redirects to https://hcrb.in/health. Neither path provides an uptime history or verifies a paid workflow.