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

# Source Transparency

> How Centaur connects structured data back to the source material that produced it.

Centaur is source-backed: structured trade data keeps references back to the source material when that material is available to the product.

## Source previews

Product source previews can show:

* source platform, such as Telegram or X
* trader identity
* source account or channel identity
* source timestamp
* sanitized source text
* source image attachment
* link to the full original message when available

Source previews exist to make structured events auditable without turning Centaur into an unbounded raw-message transcript.

## Source Message IDs

The public API uses a **Source Message ID** as the stable opaque public handle for a source message. Do not infer Telegram channel/message tuples or X account/tweet IDs from this value.

Event rows can reference a source message by `messageId`. Use the message read surface to hydrate that ID when you need the source text, attachments, timestamp, or original-source URL.

Message hydration responses expose source metadata under `source.identity` and message display data under `source.preview`. Use the `platform` field in those objects to render platform-specific labels, icons, and links. Use the `sourcePlatforms` filter on message reads when an agent needs Telegram-only or X-only source messages.

Trader discovery and trader stats responses expose each trader's single source platform under `source`. Trader discovery rows also expose `tradeCount`, which is the eligible visible position count for the discovery result. Use `source`, `tradeCount`, or the `sourcePlatforms`, `minTrades`, `startTime`, and `endTime` filters when an agent needs platform-aware trader discovery with an activity threshold.

## Event reporting

When the product exposes a report-event action, use it for data-quality issues such as:

* wrong asset
* wrong direction
* wrong event type
* missing or incorrect source context
* duplicate or stale position behavior

Reporting an event does not immediately change public API responses. It gives the Centaur team a review target tied to a concrete source-backed record.

## Limits

Not every structured record has a user-visible source link. Some events are system-inferred or system-generated, and some source material may be unavailable to a given product surface.