Feed Signal Proof — RSS and Atom API: structured feed entries
Pricing
$1.00 / 1,000 observed articles
Feed Signal Proof — RSS and Atom API: structured feed entries
Normalize RSS, Atom and JSON Feed entries into titles, links, authors and published dates. Capture supplied metadata without fetching full articles. Demo: https://market-data-gateway-production-2084.up.railway.app/launch/feed-signal-proof
Feed Signal Proof — RSS, Atom & News Monitor
Normalize RSS, Atom and JSON feeds; monitor new and updated articles with publisher evidence.
Quick start
{"feeds": ["https://feeds.bbci.co.uk/news/rss.xml","https://www.theverge.com/rss/index.xml"],"maxArticles": 3,"stateKey": "release-smoke"}
Run once for a snapshot. Schedule repeated runs with the same stateKey for change monitoring. Export the dataset as JSON, CSV or Excel; inspect the SUMMARY record for every source's completeness and baselineUpdated state.
What you receive
Article title, publisher, URL, description, authors, categories, explicit publication/update dates and an image URL when supplied. RSS 2.0, Atom and JSON Feed supported. Full article text is not fetched. Missing dates/images remain null. No article disappearance is treated as deletion because feeds have a rolling window. Up to 5,000 previously observed identities retained per feed.
Limits and accuracy
1–20 feeds; 1–1,000 articles per feed; four MB response limit. A feed is a finite source window, not exhaustive news coverage. Public feeds only, with robots checks, protected DNS/redirects, bounded reads and explicit errors. No authenticated or blocked content bypass.
Pricing
$0.001 per successfully observed article ($1/1,000), including unchanged checks even with onlyChanges. Errors and removal rows are not charged. Platform usage is included under the standard Apify pay-per-event model. A spending-limited run stops before an additional charge and preserves its previous history.
API
POST https://api.apify.com/v2/acts/hadi.kanj~feed-signal-proof/run-sync-get-dataset-items with your own Apify Bearer token and JSON input. For larger runs use /runs, poll /actor-runs/{id}, then fetch /datasets/{defaultDatasetId}/items. Never share your token. Source text is publisher-provided; downstream licensing remains your responsibility.