Reporting paths

Your infrastructure detects AI bot requests and reports them directly. No cooperation from the agent required. Whether you run a news site, a product catalogue, or a brand portal - you control the data at source.

AI Agent ──GET──> Your CDN / CMS / Origin Server
                          │
                          ├── Detect AI user agent
                          ├── Read OA-Telemetry-ID header (if present)
                          └── POST content_retrieved event to OA telemetry endpoint

The telemetry spec calls this source_role: "origin" or source_role: "edge" depending on whether the event is reported from the origin server or an edge network (CDN).

When the requesting agent includes an OA-Telemetry-ID header, that ID correlates your event with the agent's own event - two independent observations of the same retrieval. When the agent doesn't include the header, you still get the event. It's just one-sided.

Integrations

Content marketplaces and licensed content repositories act as intermediaries. When an agent retrieves content through a marketplace, the marketplace can report the retrieval event on behalf of the content owner.

AI Agent ──GET──> Content Marketplace (Microsoft, Amazon, etc.)
                          │
                          ├── Serves licensed content to agent
                          └── POST content_retrieved event (source_role: "index")

The telemetry spec calls this source_role: "index". The marketplace has visibility into which content was served and can report events with full metadata - content URL, licensing terms, and the telemetry ID for correlation.

The AI agent itself reports what content it retrieved. This is the most complete path - the agent has full visibility into what it fetched, how it used the content, and what the user did with the response.

AI Agent (Google, OpenAI, Perplexity, etc.)
    │
    ├── Retrieves content from web / index / RAG
    ├── POST content_retrieved event (source_role: "agent")
    ├── Cites content in response
    ├── POST content_cited event
    └── User clicks through
        └── POST content_engaged event

Agent-side reporting covers the full event lifecycle - retrieval, citation, engagement, and outcome. When combined with server-side reporting on the same retrieval, the OA-Telemetry-ID header correlates both observations into a single, corroborated event.