XML Feed Validator avatar

XML Feed Validator

Pricing

from $3.90 / 1,000 record profileds

Go to Apify Store
XML Feed Validator

XML Feed Validator

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.

Pricing

from $3.90 / 1,000 record profileds

Rating

0.0

(0)

Developer

junipr

junipr

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

4 days ago

Last modified

Share

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.