404 (existence is never confirmed). These are consumption endpoints for feed readers and site embeds, not a general read API.
RSS
application/rss+xml) — point any feed reader at it. This is the URL shown on a feed’s public page at app.dexi.net/feeds/{feed_id}.
JSON
Example response
updated may be null on rare legacy notes.
Fields
Access and visibility
A feed’s publisher chooses one of three access levels in the app. Public and link-only feeds behave identically on these endpoints — the UUID is the only credential, so treat a link-only URL as a secret. Private feeds answer404 to everyone but the signed-in owner, and the two routes never reveal whether an id exists. Changing a feed’s access, or the tag filter behind it, takes effect on the next request; nothing is cached server-side.
Polling
Both routes are rate-limited per IP (120 requests per minute) and return theRateLimit-* headers described in Versioning. Feed readers that poll every 15–60 minutes are well inside the cap. There are no conditional-request headers (ETag, Last-Modified) today — compare entries[].updated to detect changes, or just re-render the list.
Embedding
The JSON route is not open to cross-origin browser requests from arbitrary sites, so fetch it from your build step or server (a static-site generator, an edge function, a cron job) and render the entries into your page. For a no-code option, hand the RSS URL to any feed-to-HTML widget or newsletter tool that accepts RSS 2.0 — that is what the public share page atapp.dexi.net/feeds/{feed_id} links to.