# RSS Atom JSON Feed Normalizer (`muntasir2000/rss-atom-json-feed-normalizer`) Actor

Normalize RSS 2.0, Atom and JSON Feed into clean article records with dates, links, authors and summaries. Deduplicate items and filter by keyword or publication date. No browser or AI API required.

- **URL**: https://apify.com/muntasir2000/rss-atom-json-feed-normalizer.md
- **Developed by:** [Muntasir Salim](https://apify.com/muntasir2000) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 processed feeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## RSS Atom JSON Feed Normalizer

Normalize RSS 2.0, Atom and JSON Feed into clean article records with dates, links, authors and summaries. Deduplicate items and filter by keyword or publication date. No browser or AI API required.

### Who is it for?

Content monitoring, newsletters and research pipelines. This Actor runs automatically on Apify; use schedules, API calls or integrations to repeat a workflow.

### Quick start

1. Enter public URLs in the input form.
2. Set a maximum output record limit and spending cap.
3. Run the Actor and export the dataset as JSON, CSV or Excel. A CSV file and run summary are also saved in the key-value store.

Example input:

```json
{
  "urls": [
    "https://www.nasa.gov/news-release/feed/"
  ],
  "maxResults": 10,
  "timeoutSeconds": 15
}
```

### Output

Each successfully processed source emits one summary record followed by its data records. Records include source URL and recordType. Failed sources are listed in REPORT.errors and do not produce a paid result. A valid source with no matching records still produces a clear summary, rather than an ambiguous empty run.

### Pricing

$0.005 per feed processed ($5.00 per 1,000), including platform usage. Each successfully processed URL is charged once, including its summary and all data rows within your output limit. A valid source with no matching data still counts as processed. Failed or robots-blocked sources are not charged. Set a maximum cost per run to control spending; requests stop when the remaining processing budget is exhausted.

### What it does not do

Direct feed URLs only. RSS 2.0, Atom 1.0 and JSON Feed 1.x. No persistent cross-run state; deduplication applies within each run. Does not fetch full articles.

### Responsible operation

Public URLs only. No logins, private networks, CAPTCHA bypass, stealth proxies or LLM API keys. DNS is checked and connections are pinned to a public address. Robots.txt is respected, including each redirect target. Requests and decompressed responses are bounded. At most 50 sources, 1,000 records, and 5 MB per response. No external $ref or arbitrary URL discovered inside a document is fetched. UTF-8 input only. Respect data licenses and source terms.

### Maintenance and data

Outputs remain in the calling Apify account under its retention settings. Source content is untrusted and treated as data. Monitoring results can change when websites change; check important decisions against the source. No warranty of continued source availability, customer demand or revenue.

# Actor input Schema

## `urls` (type: `array`):

Enter 1 to 50 public HTTP(S) URLs. No credentials, private hosts or nonstandard ports.

## `maxResults` (type: `integer`):

Global limit across all URLs; 1 to 1000. Each successfully processed URL returns a summary record, even when no matching data is found.

## `timeoutSeconds` (type: `integer`):

Timeout per DNS lookup and request, in seconds (3 to 30).

## `keyword` (type: `string`):

Case-insensitive literal text match in title or summary. Empty means no filter.

## `publishedAfter` (type: `string`):

Optional ISO date or timestamp. Undated items are omitted when a date filter is set.

## Actor input object example

```json
{
  "urls": [
    "https://www.nasa.gov/news-release/feed/"
  ],
  "maxResults": 100,
  "timeoutSeconds": 15,
  "keyword": "",
  "publishedAfter": ""
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `report` (type: `string`):

No description

## `csv` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://www.nasa.gov/news-release/feed/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("muntasir2000/rss-atom-json-feed-normalizer").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["https://www.nasa.gov/news-release/feed/"] }

# Run the Actor and wait for it to finish
run = client.actor("muntasir2000/rss-atom-json-feed-normalizer").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "https://www.nasa.gov/news-release/feed/"
  ]
}' |
apify call muntasir2000/rss-atom-json-feed-normalizer --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,muntasir2000/rss-atom-json-feed-normalizer"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/eG3EJOnDVfzglnuD8/builds/EXAzGuVVKuBewIfhe/openapi.json