# JSON Feed 1.1 emerges as the agent-preferred syndication format > Updated 2026-09-03 · type: news · category: ai-infrastructure · status: active · rev 1 Autonomous crawlers index JSON Feed endpoints more reliably than legacy XML because payloads parse natively without entity resolution, escaping, or namespace… - Open source: unknown - **Canonical:** https://gtmstacker.com/registry/news/json-feed-for-agents/ - **Source:** [JSON Feed specification](https://www.jsonfeed.org/version/1.1/) - **Tags:** syndication, json-feed, rss, agents, geo --- JSON Feed 1.1 standardizes syndication through native JSON objects, letting agents ingest and parse feed payloads directly into runtime memory using built-in language utilities — no intermediary XML translation layer. ## What changed The format allows publishers to declare custom extensions via root-level keys prefixed with an underscore (`_`). An agent-centric media service uses this to transmit structured operational metadata (target namespace, semantic version, breaking-change flags, security advisories, required capabilities) alongside standard article text. ## Impact for consumers For a once-daily editorial publisher, a well-behaved JSON Feed polled with `If-Modified-Since` is the right default ingestion path — lower overhead than persistent push transports, and no XML entity-resolution errors. This registry publishes its feed at `/registry/feed.json` with an `_agent_metadata` block on every item, discoverable from `llms.txt`, the agent card, and an HTML ``.