> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Tracer: operational endpoints removed from public reference

> Tracer health, version, and readiness endpoints no longer appear in the public API reference because they belong in internal operational documentation.

<Badge stroke icon="calendar-days" iconType="regular">May 11, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation update</Badge> <Badge color="green" size="lg" stroke icon="circle-check" iconType="regular">No migration required</Badge>

## Affects

***

Teams reading the public Tracer API reference.

This update applies to the public documentation portal. It does not change the runtime API behavior.

<Note>
  The public documentation portal is the customer-facing reference. Repository source files should not be treated as integration artifacts or downloaded API specifications for client use.
</Note>

## What changed

***

### Operational endpoints removed from public API reference

The following Tracer endpoints no longer appear in the public API reference:

* `/health`
* `/version`
* `/readyz`

These endpoints remain part of operational use where applicable. They are simply no longer presented as customer-facing integration endpoints.

## Impact

***

This is a documentation update. It narrows the public Tracer API reference to the integrator-facing surface.

No product behavior changed.

## What you need to do

***

<Steps>
  <Step>
    Do not use the public Tracer API reference as the source for operational health, version, or readiness checks.
  </Step>

  <Step>
    Keep operational monitoring tied to internal documentation and deployment-specific configuration.
  </Step>

  <Step>
    Do not treat repository source files as client integration artifacts. Use the documentation portal as the customer-facing reference.
  </Step>
</Steps>

### Deadline

None.

### Why

Operational endpoints are useful, but they are not the same thing as customer-facing integration endpoints. Removing them from the public reference keeps the documentation clearer.

## Resources

***

* [Tracer error list](/en/reference/tracer/tracer-error-list)