Documentation
Wire XML validation into the place it breaks
Everything here exists so a broken document fails in CI, next to the change that broke it — rather than in production, next to nothing.
Validation API
4 rules
POST a document, get a verdict as JSON or SARIF 2.1.0. Well-formedness, optional XSD validation, and namespace checks. No ingestion — documents are validated in memory and never reach a workspace or a log.
CI and integrations
GitHub code scanning
A copy-paste GitHub Actions workflow that turns a malformed sitemap into an annotation on the pull request that broke it, rather than a line in a build log nobody reads.
API keys
Account required
Keys are issued per account and only a SHA-256 hash is stored, so a key is shown exactly once and cannot be recovered by anyone. Guests cannot issue them.
Limits
Stated here rather than discovered in a 413. The caps exist because parsing is the one thing a stranger can make expensive.
- Free tools
- 2 MB
- Per document, no account
- Signed in
- 5 MB
- Per ingested document
- Schema
- 2 MB
- Per XSD or RELAX NG grammar
Schema validation runs libxml2 with no network access, so an XSD that imports a remote schema will not fetch it. More of what these tools do not do
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.