Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

RSS

RSS (Really Simple Syndication) is an XML-based web feed format for publishing frequently updated content such as blog posts and news. Clients subscribe to feeds to receive new items without visiting each site.

RSS, short for Really Simple Syndication, is an XML-based web feed format that lets a site publish a machine-readable stream of its latest content — blog posts, news, podcast episodes — that clients can subscribe to and poll for updates. It is one of the earliest and most durable examples of a simple, open data contract on the web: a feed at a known URL, a handful of standardized elements, and a subscription model that requires no accounts or negotiation.

  • XML data contract - A fixed vocabulary of channel, item, title, link, and pubDate elements makes every feed parseable by the same generic reader.
  • Pull-based subscription - Clients poll the feed URL on their own schedule, so publishers expose content once and any number of consumers can follow it.
  • A known, discoverable location - Feeds are advertised in page <head> tags and at conventional paths, making them easy for tools and crawlers to find.
  • Sibling of Atom - The Atom syndication format standardized the same idea with stricter rules; the two coexist and most readers speak both.

RSS is effectively a read-only API that predates most of what we call API design, and it still shows up constantly in real operations — changelogs, status pages, release notes, and podcast distribution all lean on it. Because a feed is a stable, low-cost, machine-readable surface, it is one of the easiest ways to make content agent-consumable without building a bespoke endpoint. When I evaluate a provider’s discoverability, a working feed is a small but honest signal that they think about programmatic access to their content, not just their core API.

Referenced on the API Evangelist blog

Where this standard shows up across sixteen years of my writing at apievangelist.com — how it fits into API design, governance, and the agentic turn.