RSS
RSS (Really Simple Syndication) is the canonical XML feed format family for publishing and subscribing to streams of frequently updated content — blogs, news, podcasts, and other periodic resources. The RSS family in this index covers RSS 2.0 (stewarded by the RSS Advisory Board), Atom 1.0 (RFC 4287), JSON Feed 1.1, the RSS Best Practices Profile, OPML 2.0 for feed subscription lists, and HTML autodiscovery conventions used by feed readers to locate feeds from a site's homepage.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles RSS the way a machine reads it — 23 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — RSS scores 29.8/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile RSS
Each block below is one kind of artifact we hold for RSS. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
RSS 2.0
RSS 2.0 is the dominant XML-based syndication format, stewarded by the RSS Advisory Board. A feed consists of a root
Atom 1.0
Atom 1.0, defined by IETF RFC 4287, is an XML-based syndication format developed as a more rigorously specified alternative to RSS 2.0. An Atom feed (atom:feed) contains require...
JSON Feed 1.1
JSON Feed 1.1 is a JSON-based syndication format created by Brent Simmons and Manton Reece as a developer-friendly alternative to RSS and Atom. A JSON Feed has top-level version...
RSS Best Practices Profile
The RSS Best Practices Profile is the RSS Advisory Board's normative guidance on producing RSS feeds that interoperate cleanly across the diverse population of feed readers. It ...
OPML 2.0
OPML (Outline Processor Markup Language) 2.0 is an XML format for outlines, most commonly used to exchange lists of RSS/Atom feed subscriptions between feed readers. A subscript...
Feed Autodiscovery
Feed autodiscovery is the HTML convention by which a web page advertises the location of its RSS, Atom, or JSON Feed using a
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Rss Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
RSS API Rules
SPECTRALJSON Schema 7
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Atom 1.0 Entry
JSON SCHEMAAtom 1.0 Feed
JSON SCHEMAJSON Feed 1.1 Item
JSON SCHEMAJSON Feed 1.1
JSON SCHEMAOPML 2.0 Subscription List
JSON SCHEMARSS 2.0 Channel
JSON SCHEMARSS 2.0 Item
JSON SCHEMAScroll within the panel for all 7 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Rss Channel Structure
JSON STRUCTUREExamples 6
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Atom Feed Example
EXAMPLEFeed Autodiscovery Example
EXAMPLEJson Feed Example
EXAMPLERss Channel Example
EXAMPLERss Item Example
EXAMPLESecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for RSS — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 4
Reference material describing how the API behaves
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/rss · machine-readable index on apis.io