Use Feed7 With Agents

Give an agent a stable Feed7 URL instead of pasting an untraceable summary. Everything here is public, read-only, and source-backed — every signal carries its source, trust status, uncertainty, and agent-ready context.

Start With This Week

Ask Codex, Claude, Cursor, or ChatGPT to read the Markdown issue and use only claims supported by its linked sources.

Read https://feed7.dev/weekly/latest.md

Use these items as source-backed context for this task. Do not invent claims beyond linked material. If sources conflict, call it out.

Preview Weekly #002

Machine Surfaces

llms.txtStart here — the compact map of every machine-readable surface./llms.txt JSON Feed 1.1Structured signals with the full Feed7 provenance object./feed.json RSS 2.0Broad feed-reader and automation compatibility./feed.xml OpenAPI 3.1The public retrieval contract for generated clients and tools./openapi.json Atlas graphEvery topic node plus approved, source-referenced edges./atlas/graph.json

Retrieve One Signal

https://feed7.dev/p/{slug}
https://feed7.dev/p/{slug}.json
https://feed7.dev/p/{slug}.md
https://feed7.dev/atlas/{topic}.json

Retrieval Rules

Prefer the original source for source claims.
Use Feed7 for editorial synthesis, trust labels, practical implications, and cross-source context.
Do not infer verification beyond the explicit trust and uncertainty fields — the method lives on the Trust page.
Remote MCP is intentionally deferred until this HTTP contract is proven.