> ## 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 authentication and validation-history contract

> Tracer authentication precedence and validation-history scope are now documented.

<Badge stroke icon="calendar-days" iconType="regular">August 26, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation correction</Badge> <Badge color="purple" size="lg" stroke icon="eye" iconType="regular">Review recommended</Badge>

## Affects

***

Teams that authenticate to Tracer or use its validation records for investigations or compliance processes.

## What changed

***

Tracer supports API key and plugin authentication. Plugin authentication takes precedence when both are enabled, except on API-key-only endpoints. Multi-tenant deployments require plugin authentication.

This update distinguishes validation-history queries from Tracer's separate immutable Audit Context and hash-chain verification. It corrects the release-note description of existing behavior; it does not announce a runtime release.

## Impact

***

**Classification: Review recommended.** Authentication headers and the stated scope of validation records may affect integration and compliance assumptions.

## What you need to do

***

<Steps>
  <Step>Confirm which authentication mode applies to every Tracer endpoint your client calls.</Step>
  <Step>Use a Bearer token when plugin authentication applies; use an API key only where the documented configuration permits it.</Step>
  <Step>Review compliance material that treated Tracer validation history as an immutable audit log or hash chain.</Step>
</Steps>

### Deadline

Review before the next Tracer client or authentication configuration change.

## Resources

***

* [Getting started with Tracer](/en/products/tracer/getting-started)
* [Tracer integration guide](/en/products/tracer/integration-guide)