RSS / Atom · Developer Tools · 1 endpoint
Feed Parser
Any RSS or Atom feed URL, parsed to normalized JSON — the plumbing under every feed reader and digest bot.
- Status
- Operational
- Price
- 1 credit / request
- Rate limit
- 60 / 60s
- Cache
- 15m
- Requests
- 0
Endpoint
How to call it
Code
Request — cURL
v1
curl https://api.diraz.co.id/v1/utility/feed \
-H "Authorization: Bearer drz_live_…"For AI agents
Callable through the MCP server with the same key:
call_api {"endpoint":"feed-parse","params":{"feed_url":"https://hnrss.org/frontpage","max_age":"60"}}Parameters
- feed_urlstring · required
- The feed's URL.
- max_ageinteger (seconds) · optional
- Ask for data no older than this. Clamped to the product's own floor, so it can narrow the window but never force a refresh on every call.Default: 300
Example response
200 OK
JSON
{
"data": {
"feedUrl": "https://hnrss.org/frontpage",
"title": "Hacker News: Front Page",
"format": "rss",
"items": [
{
"title": "Show HN: A thing people like",
"url": "https://example.com/thing",
"publishedAt": "2026-08-22T03:14:00.000Z",
"summary": "377 points, 128 comments"
}
]
},
"meta": { "request_id": "req_7Q2fK4mZ", "as_of": "2026-08-22T04:05:00.000Z", "age_seconds": 42, "next_update_at": "2026-08-22T04:20:00.000Z" }
}- title / format
- The feed's own name, and whether it's `rss` or `atom`.
- items[].title / url / publishedAt / summary
- Every entry, one shape regardless of the feed's format.
Errors
When something goes wrong
Every failure carries a stable machine-readable code and the same meta.request_id a success carries — quote it and we can find your request. Errors are never billed.
401 Unauthorized
JSON
{
"error": {
"code": "UNAUTHORIZED",
"message": "The API key is invalid, expired, or revoked."
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}- UNAUTHORIZEDHTTP 401
- Missing, malformed, expired, or revoked API key.
- FORBIDDENHTTP 403
- The key is valid but lacks the scope this product needs.
- VALIDATION_ERRORHTTP 422
- A query parameter is the wrong type or out of range.
- RATE_LIMITEDHTTP 429
- Rate limit exhausted. `Retry-After` says how long to wait.
- SERVICE_UNAVAILABLEHTTP 503
- No data recent enough to serve. Carries `Retry-After`, and is never billed.
Data freshness
Every response is timestamped
as_of is when the data was published, age_seconds how old it is now, and next_update_at when newer data is expected.
Up to date
200
Inside its published window. Almost every request.
Delayed
delayed: true
Newer data is late; you get the latest there is, flagged.
Unavailable
503
Nothing recent enough. Carries Retry-After, never billed.
Health
Is it up?
- Feed Parser
1/1 passing