📰RSS / Atom Feed Parser
Fetch an RSS or Atom feed and return normalized JSON items: title, link, publication date (ISO) and summary. Server-side fetching with SSRF guard; handles both RSS 2.0 and Atom dialects.
🔌 Server-side tool
This tool runs on the server (it fetches third-party URLs directly and cannot run in your browser). Use the paid JSON API below — the worked examples show real server-side results and refresh automatically.
Worked examples
Hacker News front page
GET /api/v1/dev/feed-parser?url=https%3A%2F%2Fhnrss.org%2Ffrontpage&limit=10
Result: 10 items — Bez: Generating a browser engine from specs and tests
BBC world news
GET /api/v1/dev/feed-parser?url=https%3A%2F%2Ffeeds.bbci.co.uk%2Fnews%2Fworld%2Frss.xml&limit=10
Result: 10 items — BBC News
NASA news
GET /api/v1/dev/feed-parser?url=https%3A%2F%2Fwww.nasa.gov%2Fnews-release%2Ffeed%2F&limit=5
Result: 5 items — NASA
Machine API (x402)
$0.002 / callThis tool is also a JSON API for AI agents. Requests without payment receive 402 Payment Required plus instructions; agents pay USDC on Base via the x402 protocol — no accounts, no API keys.
GET /api/v1/dev/feed-parser?url=https%3A%2F%2Fhnrss.org%2Ffrontpage&limit=10 HTTP/1.1
Host: agenttools-hub.vercel.app
→ 402 (payment required, instructions in headers)
→ 200 (after X-PAYMENT header; JSON body below)
{
"tool": "dev/feed-parser",
"input": {"url":"https://hnrss.org/frontpage","limit":10},
"result": { "value": 10, "answer": "10 items — Bez: Generating a browser engine from specs and tests" }
}Agent docs: /llms.txt · OpenAPI spec · integration guide
About this tool
Feeds are the web's original structured API, and agents monitor them constantly — but nobody wants to parse XML. Give it a feed URL and get normalized JSON: titles, links, ISO dates and summaries, RSS 2.0 and Atom both handled, fetched server-side with an SSRF guard.
Frequently asked questions
Which formats are supported?
RSS 2.0 and Atom. The parser detects the dialect automatically and normalizes both to the same item shape.
Where is the full item content?
Summaries appear in the table; the complete item array (title, link, isoDate, contentSnippet) is in `result.artifacts.items` as JSON.