Markdown edition

# New publishers join SPUR's AI content tracking coalition

> Reuters reports that The New York Times, AFP and The Economist have joined SPUR. Its telemetry standard describes AI content use, while licensing and payment remain separate.

By BIG CHANGE Editorial

Published: 2026-10-13T10:42:18.599Z
Updated: 2026-10-13T10:42:18.599Z
Canonical: https://bigchange.ai/blog/spur-publisher-coalition-ai-content-telemetry

![Conceptual charcoal illustration of one newspaper partly withdrawn from a dark metal newsstand rack, while other copies remain inside.](https://bigchange.ai/api/media/file/spur-retrieval-newsstand-hero-v1.png)
AI-generated conceptual illustration by BIG CHANGE; not an actual SPUR system, publisher event or AI agent interaction.

Reuters reported on October 12 that The New York Times, Agence France-Presse and The Economist have joined [SPUR](https://www.spurcoalition.org/), a publisher coalition working on common rules for how AI companies use journalism. The expansion follows SPUR's October 2 [announcement of Content Telemetry 1.0](https://www.spurcoalition.org/updates/spur-content-telemetry-standard-v1-published), a proposed way for AI agents to report what happens to a publisher's material after an agent retrieves it.

According to [Reuters' reporting](https://www.aol.com/articles/nyt-economist-among-publishers-joining-230559000.html), the coalition has more than 80 members across more than 20 countries, including more than 40 publishers.

## The big change

- **What changed:** More publishers are participating in an effort to give AI content use a shared reporting format. SPUR's specification separates a page fetched by an agent from material that enters an answer's generation context, appears in a citation or reaches a user.
- **Why it matters:** A publisher can see a request to its site, but that request alone cannot show whether its reporting shaped an AI answer. A participating agent's later events could give the publisher a more useful account for a licensing discussion, subject to what the operator records and agrees to share.
- **What to watch:** SPUR says it is developing implementations and proofs of concept with industry partners. Their scope will show whether operators can produce useful reports beyond the published specification. The format leaves license terms and payments to separate agreements.

## What the format measures

The [version 1.0 specification](https://github.com/SPUR-Coalition/telemetry/blob/v1.0/SPECIFICATION.md) describes five stages of an AI agent's interaction with content: retrieval, grounding, citation, presentation and engagement. A retrieval is a completed fetch. Grounding means an identified item entered a generation model's context, where it could affect the answer. Citation records an explicit source association in an output. Presentation means content or a source reference reached a surface a recipient could perceive. Engagement records an observed action, such as an interaction with that presentation.

These are different counts. An agent can retrieve a page and never use it in an answer. Material can enter the model's context without being cited. A citation built into an output need not be shown to a user. The specification also says presentation does not prove that anyone noticed it. Its event definitions make those distinctions explicit so a publisher and an AI operator can discuss the same reported activity.

The visibility problem remains. A publisher or its delivery network may observe a fetch. The specification says only the agent can report grounding, citation and presentation inside its own workflow. Those later stages therefore depend on agent participation and the quality of its records. The format allows reports to declare whether coverage is complete, sampled, aggregated or selected; the governing terms determine what a particular relationship requires.

## Where reporting stops

SPUR's [coalition announcement](https://www.spurcoalition.org/updates/spur-content-telemetry-standard-v1-published) presents the standard as a basis for discussing licenses and accounting for content use. The specification itself says it does not define content access or licensing protocols, attribution algorithms, or how compensation is calculated. SPUR's [FAQ](https://www.spurcoalition.org/) says it is not a collective licensing organisation and that members retain control of their own commercial relationships.

The current format focuses on content used while an AI system produces a response. Its text explicitly excludes reporting whether a work was used to assemble a training corpus, train or fine-tune a model, build embeddings, or construct a search index. A publisher seeking an account of model training would need evidence beyond a conforming telemetry report. The specification also does not prevent access to content or require an AI company to pay for it.

SPUR says it is working with partners on implementations, proofs of concept and tools for agent operators. The material reviewed here establishes a published open-source specification and a coalition plan, not a verified production reporting system. The new Reuters-reported members increase the number of publishers with an interest in that plan. Whether it changes licensing practice depends on adoption, report quality and agreements that sit outside the specification.

## Sources & further reading

- [SPUR's Content Telemetry 1.0 announcement](https://www.spurcoalition.org/updates/spur-content-telemetry-standard-v1-published), October 2, 2026: explains the coalition's goal, the five reporting stages and its work on implementation and proofs of concept. It is the coalition's account of its own initiative.
- [Content Telemetry Specification, version 1.0](https://github.com/SPUR-Coalition/telemetry/blob/v1.0/SPECIFICATION.md): the primary technical record for event definitions, reporting boundaries and exclusions. Its text is marked published September 2, 2026; SPUR publicly announced the standard on October 2.
- [SPUR coalition FAQ](https://www.spurcoalition.org/): states the coalition's role and clarifies that members keep their own commercial relationships; it is not a collective licensing organisation.
- [Reuters' October 12 membership report](https://www.aol.com/articles/nyt-economist-among-publishers-joining-230559000.html): original reporting, republished by AOL, for the newly named members and coalition size. Those figures were not independently established from the coalition's member page in this review.

## Sources

- [Reuters, publisher membership report, October 12, 2026](https://www.aol.com/articles/nyt-economist-among-publishers-joining-230559000.html) — Original Reuters reporting republished by AOL. Supports the new member names and coalition size; those are Reuters-reported.
- [SPUR Content Telemetry 1.0 announcement, October 2, 2026](https://www.spurcoalition.org/updates/spur-content-telemetry-standard-v1-published) — Coalition statement on the standard's goals, five reporting stages and implementation/proof-of-concept plans.
- [Content Telemetry Specification, version 1.0](https://github.com/SPUR-Coalition/telemetry/blob/v1.0/SPECIFICATION.md) — Primary technical record, marked published September 2, 2026. Defines stages, report scope and exclusions for training and licensing.
- [SPUR coalition FAQ](https://www.spurcoalition.org/) — States SPUR is not a collective licensing organisation and members retain their commercial autonomy.