SPUR Content Telemetry Profile

The publisher-facing profile of the Content Telemetry standard — and the identifier a licensing layer references to require telemetry reporting.

Profile URI: https://contenttelemetry.org/profiles/spur

Status: v0.1 (preview). Constrains Content Telemetry v0.1.

The profile

The profile names a single accreditation tier — Compliant — and the requirements an implementer meets to be assessed at it: conforming emitter at any level, event-level delivery, real-time delivery, and a publisher-designated endpoint. It adds requirements; it never modifies the wire format.

Profile document, fixtures, and accreditation runner
Content Telemetry standard (the wire format this profile constrains)

Reporting binding

A licensing declaration layer — for example the RSL <reporting> element — references this profile URI to make telemetry reporting a condition of the licence. The standard's manifest cannot demand a minimum reporting level from an agent; a licence can. The licence carries the demand, the manifest carries the transport.

Layer	Scope	Carries
Licensing declaration	Per-licence	The demand: minimum conformance level, privacy floor, cadence
`.well-known` manifest	Per-domain	The transport of record: signing keys, claimed domains, endpoint
This profile	The rules	What conforming means, and how it is assessed

Reporting configuration

The JSON object a licence carries is validated by /profiles/spur/reporting-config.schema.json. Field names match the standard verbatim. Only conformance_level is required.

<reporting type="telemetry"
           profile="https://contenttelemetry.org/profiles/spur"
           endpoint="https://telemetry.example.com/v1/events">
  <![CDATA[
  {
    "conformance_level": "grounding",
    "privacy_level": "minimal",
    "manifest": "https://example.com/.well-known/content-telemetry.json"
  }
  ]]>
</reporting>

privacy_level is a floor: the Client populates at least the fields it permits, and may disclose more. endpoint is the destination events must reach — for agent telemetry, routed through a telemetry consumer that exposes each publisher only its own events, not necessarily a direct POST target.

Maintainer

Maintained by Alex Springer on behalf of the SPUR Coalition. Questions go to alex@spurcoalition.org.