Use case
CI validation gates
Fail the build, not the customer
The problem
XML is usually generated, so it breaks in generated ways: a template change escapes an ampersand wrongly, a schema bump lands in staging, a feed loses a required element. None of it is caught by unit tests, and all of it is found in production.
What you get
- The person who broke it finds out on their own pull request
- A schema change is a reviewable diff rather than a production incident
How XMLDir helps
- Validate any document from one POST, with the verdict as the process exit code
- Return SARIF 2.1.0 so failures become annotations on the pull request that caused them
- Pin a saved policy revision so a build validates against an agreed contract rather than whatever the schema says today
- Compare a generated document against a known-good version and fail only on structural change, not reformatting
Other use cases
Sitemap operations
Keep sitemap.xml healthy at scale
Vendor integrations
Catch contract drift before it breaks orders
XML to data workflows
Turn XML into clean, repeatable pipelines
Sample payload vault
A searchable memory for tricky XML
Regulated messaging
Schema-valid is necessary, not sufficient
Localization pipelines
Catch what translation quietly changed
Document archives
Prove the document did not change
Get started
Bring order to the XML your team can't afford to ignore.
Create a free account and get a private workspace to search, validate, diff, and monitor your XML feeds, sitemaps, schemas, and vendor integrations.