Commerce-facing requirements for the Content Telemetry standard.
This repository is a draft profile. It names a single accreditation tier - Compliant - and the requirements an implementer in agentic commerce (affiliate networks, marketplaces, brands, destination sites) must meet to be assessed at it: conformance to the standard, event-level and real-time delivery, click-out reporting, ctx_token propagation across the click boundary, multi-citation attribution, and - for telemetry consumers - resolving a ctx_token to a privacy- and consent-gated click manifest.
The standard - the telemetry wire format itself - lives in SPUR-Coalition/telemetry. This profile references the standard by version and does not restate it.
A click from an AI agent's response is the end of a chain of sources, not a single referrer. The agent read several reviews and guides, cited some, displayed some, and the user clicked one link. This profile keeps that chain intact across the boundary between the agent and the landing page, so a destination can credit every source that informed the response - multi-citation attribution - rather than only the clicked URL.
The mechanism is the standard's ctx_token: an opaque click-token the agent issues, carried to the landing page in place of the session identifier, which a telemetry consumer resolves to the click manifest (the session's grounded, cited, and displayed sources). The session UUID never crosses the boundary.
The standard is permissive and value-neutral; this profile adds commerce-specific requirements on top. The dependency runs one way - profile to standard, never the reverse - so the profile can change its requirements, and other communities can profile the same standard, without touching the wire format. The profile names no operator and no hosted endpoint: a competing operator can implement and be assessed against it with no dependency on any single operator's infrastructure.
- PROFILE.md - the profile: requirements, conformance assessment, conformance mark
- accreditation/ - example fixtures and the assessment runner
- acp/ - ACP binding: the
content_attributionextension embedding citation data in Agentic Commerce Protocol checkouts (Apache 2.0) - ucp/ - UCP binding: the
org.openattribution.telemetryvendor extension and standalone capability for Universal Commerce Protocol (Apache 2.0) - LICENSE - Creative Commons Attribution-ShareAlike 4.0 International (the profile text; the binding schemas under
acp/anducp/are Apache 2.0)
The ACP and UCP bindings moved here from the retired openattribution-org/telemetry repository; they are protocol bindings of the neutral Content Telemetry standard, maintained by OpenAttribution alongside this profile.
| Requirement | Means |
|---|---|
| Conformance to the standard | Valid Content Telemetry documents; advertised Retrieval, Grounding, or Citation levels must be satisfied |
| Event-level delivery | Discrete events per fetch / grounding / citation / display / engagement - no aggregation, no sampling |
| Real-time delivery | Events dispatched as they occur; alternative cadence by negotiation |
| Click-out reporting | Click-outs reported as content_engaged events: link_click for a clicked link, agent_navigate where the agent opened the destination at the user's direction |
| ctx_token propagation | Cross-boundary click-outs carry a ctx_token, never the raw session_id |
| Multi-citation attribution | Credit every source in the click manifest, not only the clicked URL; weighting model disclosed to credited parties |
Telemetry consumers meet a parallel set (PROFILE.md section 5.7): standard consumer conformance, ctx_token resolution to a privacy- and consent-gated click manifest, and content-owner resolution and isolation.
python3 accreditation/validate.pyNo external dependencies. Exit code 0 means every fixture's assessed tier matched its declared expectation.
Draft (v0.1). Constrains Content Telemetry v0.1. The two standard additions this profile relies on - the ctx_token field and its click-manifest resolution semantics - are present in the Content Telemetry standard v0.1 (sections 6.7 and 7.1), so the profile's one-way dependency on the standard is clean. Requirements may change before 1.0.