# XML Feed Validator (`junipr/xml-feed-validator`) Actor

Validate XML-based feeds for well-formedness, namespaces, required elements, repeated item structure, schema-like path rules, date/url fields, and item-level structural consistency.

- **URL**: https://apify.com/junipr/xml-feed-validator.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO tools, Developer tools
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.90 / 1,000 record profileds

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## XML Feed Validator

### Store Positioning

**Store title:** XML Feed Validator

**Short description:** Validate XML-based feeds for well-formedness, namespaces, required elements, repeated item structure, schema-like path rules, date/url fields, and item-level structural consistency.

**SEO title:** XML Feed Validator — data QA, validation, and cleanup utility

**SEO description:** Validate XML-based feeds for well-formedness, namespaces, required elements, repeated item structure, schema-like path rules, date/url fields, and item-level structural consistency. Use it to validate rows, schemas, duplicates, field quality, and delivery-readiness before handing data to clients or automations.

**Categories:** SEO\_TOOLS, DEVELOPER\_TOOLS

**Keywords:** xml, feed, validator, schema, data/schema qa utility

### Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

- Tier: U2 — Data/schema QA utility
- Primary event: `record-profiled` at $0.00390 base
- Default max charge: $5.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

- `actor-start`: base $0.00500, GOLD $0.00400. XML Feed Validator: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `record-profiled`: base $0.00390, GOLD $0.00312. XML Feed Validator: charged when record profiled is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `issue-detected`: base $0.00372, GOLD $0.00298. XML Feed Validator: charged when issue detected is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `qa-report-generated`: base $0.05000, GOLD $0.04000. XML Feed Validator: charged when qa report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

### Public Task Concepts

- Validate XML Feed records from a capped sample
- Find invalid XML Feed values before delivery
- Check XML Feed coverage against expected rules
- Prioritize XML Feed validation failures by severity
- Export XML Feed pass-fail rows with evidence

Validates generic XML feed structure for well-formedness, root/namespace expectations, item path coverage, duplicate item IDs, URL/date formats, and item-level issues.

### Inputs

- `feedUrls`
- `rawXmlInputs`
- `requiredPaths`
- `itemPath`
- `idPath`
- `urlPaths`
- `datePaths`
- `namespaceRules`
- `xsdUrl`
- `customRules`
- `maxItems`
- `includeItemSamples`
- `timeoutMs`
- `maxChargeUsd`

### Public source provenance

The starter input uses https://github.com/modelcontextprotocol/specification/commits/main.atom (bounded two-entry public Atom snapshot). The checked-in bounded snapshot keeps exact runs deterministic and avoids sending credentials or private data. Live URL inputs remain available when a current network check is required.

### Outputs

Dataset fields: `feedUrl`, `feedTypeHint`, `rootElement`, `namespaceUri`, `itemIndex`, `xmlPath`, `elementName`, `issueCode`, `severity`, `expected`, `actual`, `evidenceSnippet`, `recommendation`, `passed`.

Reports: `xml-feed-validation-report.md`, `xml-feed-issues.csv`, `xml-item-coverage-summary.json`, `xml-namespace-audit.json`, `xml-validation-samples.json`.

Use small capped runs first; live network checks should stay bounded and avoid secrets in inputs.

Live and local execution use the same pay-per-event billing guard: the actor-start event is accepted before analysis, each paid row is charged before dataset output, reports are charged before key-value-store output, and `maxChargeUsd` stops gracefully without leaking unpaid artifacts.

# Actor input Schema

## `feedUrls` (type: `array`):

Public feed URLs to fetch or inspect for XML Feed Validator.

## `rawXmlInputs` (type: `array`):

Optional supplied XML documents to validate without fetching remote feeds.

## `requiredPaths` (type: `array`):

Require required paths during validation and flag rows that do not meet the rule.

## `itemPath` (type: `string`):

Item Path controls XML Feed Validator processing for the supplied inputs; keep values conservative for first runs.

## `idPath` (type: `string`):

ID Path controls XML Feed Validator processing for the supplied inputs; keep values conservative for first runs.

## `urlPaths` (type: `array`):

URL Paths controls XML Feed Validator processing for the supplied inputs; keep values conservative for first runs.

## `datePaths` (type: `array`):

Date Paths controls XML Feed Validator processing for the supplied inputs; keep values conservative for first runs.

## `namespaceRules` (type: `object`):

Rules used by XML Feed Validator to classify findings and recommendations.

## `xsdUrl` (type: `string`):

Public XSD URL to fetch or inspect for XML Feed Validator.

## `customRules` (type: `object`):

Rules used by XML Feed Validator to classify findings and recommendations.

## `maxItems` (type: `number`):

Maximum items to process in one run; keep defaults low for safe first runs.

## `includeItemSamples` (type: `boolean`):

Include item samples in output rows or reports when available.

## `timeoutMs` (type: `number`):

Maximum time in milliseconds allowed for the XML Feed Validator operation before it is treated as timed out.

## `maxChargeUsd` (type: `number`):

Maximum estimated PPE charge allowed for the run before the actor stops gracefully.

## Actor input object example

```json
{
  "feedUrls": [],
  "rawXmlInputs": [
    "<feed xmlns=\"http://www.w3.org/2005/Atom\" xml:lang=\"en-US\">\n  <id>tag:github.com,2008:/modelcontextprotocol/modelcontextprotocol/commits/main</id>\n  <link type=\"text/html\" rel=\"alternate\" href=\"https://github.com/modelcontextprotocol/modelcontextprotocol/commits/main\"/>\n  <title>Recent Commits to modelcontextprotocol:main</title>\n  <updated>2026-07-11T19:41:17Z</updated>\n  <entry><id>tag:github.com,2008:Grit::Commit/2807f9d6d8ae2012e09377908f47cff16a2b9489</id><link href=\"https://github.com/modelcontextprotocol/modelcontextprotocol/commit/2807f9d6d8ae2012e09377908f47cff16a2b9489\"/><title>Merge pull request #3073</title><updated>2026-07-11T19:41:17Z</updated></entry>\n  <entry><id>tag:github.com,2008:Grit::Commit/082ef8eae0b14e95fb52b591c0bb11d0ec3bdabc</id><link href=\"https://github.com/modelcontextprotocol/modelcontextprotocol/commit/082ef8eae0b14e95fb52b591c0bb11d0ec3bdabc\"/><title>Resolve Markdown formatting error</title><updated>2026-07-11T01:30:06Z</updated></entry>\n</feed>"
  ],
  "requiredPaths": [
    "feed.entry.id"
  ],
  "itemPath": "entry",
  "idPath": "id",
  "urlPaths": [],
  "datePaths": [
    "updated"
  ],
  "namespaceRules": {
    "rootNamespace": "http://www.w3.org/2005/Atom"
  },
  "xsdUrl": "",
  "customRules": {},
  "maxItems": 2,
  "includeItemSamples": true,
  "timeoutMs": 5000,
  "maxChargeUsd": 1
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/xml-feed-validator").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/xml-feed-validator").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 '{}' |
apify call junipr/xml-feed-validator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/xml-feed-validator"
        }
    }
}

```

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/zTjoeDO5kjpxWn5Vm/builds/msnEE9UYqfcMbIEYY/openapi.json