JATS XML package quality control.

JATS XML quality control

Catch broken packages
before delivery.

JATS is the XML format publishers use to exchange journal articles. Upload a package you already have. JATS Verify checks the XML, linked files, references, identifiers, and release-to-release changes, then tells you exactly what needs attention.

Check one package free See pricing and deliverables

01 XML structure

02 Assets and links

03 IDs and references

04 Version changes

A final technical check

Your XML can validate and still ship broken.

A schema can confirm that tags are allowed. It does not always catch a missing figure file, a broken cross-reference, a duplicate ID, a journal-specific requirement, or an unexpected change from the approved version.

Input

Your existing package

One JATS XML file, plus an optional ZIP of figures and other linked assets. No conversion and no workflow migration.

Check

Production-level validation

We inspect structure, IDs, references, local assets, tables, identifiers, journal rules, and differences from a previous XML version.

Output

A decision you can hand off

Receive a clear pass or fail, prioritized findings with exact locations, a canonical hash, and paid downloadable evidence.

Built for: journal publishers, XML production vendors, typesetting teams, managed OJS providers, and publishing platforms that already create or receive JATS XML.

See it on a real package: our public, reproducible PMC example shows an XML-to-PDF filename mismatch that a schema-only check cannot prove. Browse the JATS validation guide library for asset, namespace, OJS, CI, scope, and pricing questions.

No account or card

Check one package free.

Upload one existing JATS XML file and see a release verdict plus up to five prioritized findings. No account, email, card, or sales call. Your source file is removed when the check finishes.

Free package diagnostic

Upload first. See the result before we ask for anything.

The free diagnostic includes one XML package, optional assets, a clear release verdict, and up to five findings. Complete evidence, journal rules, version comparison, and downloads use paid credits.

No JATS package handy? Download the synthetic test package

Ready now Up to 10 MiB XML
25 MiB assets ZIP
Input manifest

Choose your XML now. No account, email, or card is required.

Max 10 MiB
Max 25 MiB
Max 10 MiB
Max 256 KiB
Paste the key from your Access Center to unlock complete findings, downloads, journal rules, and version comparison.

Uploaded source files are removed when the request completes. Validation makes no external registry calls.

Select a JATS XML file to begin.

What gets checked

More than “the XML opened.”

01

Structure and metadata

Well-formed XML, the trusted JATS DTD, required article metadata, article types, tables, and journal-specific rules.

02

Package integrity

Missing figures, filename case mismatches, unsafe paths, duplicate IDs, broken cross-references, and identifier syntax.

03

Release evidence

Prioritized findings, semantic counts, a canonical SHA-256, version comparison, and a reproducible release ZIP.

Constrained by design

Evidence without an external lookup.

Document parsing disables network access, document-declared DTD loading, and entity expansion. A supplied DTD remains local and explicit.

DOI, PMID, and ORCID checks examine syntax and checksums only. Registry results are visibly reported as not run, never guessed.

Simple, one-time pricing

See the problem free.
Fix the release with full evidence.

No subscription is required. Start free, unlock one complete package for $12.99, or buy durable production credits from $1.49 per package. Paid credits last 12 months and include complete findings, evidence downloads, comparison, and API access. See exactly what each price includes.

Free diagnostic

$0 one package

For seeing whether JATS Verify finds useful issues in your current output.

  • One JATS XML package
  • Optional assets ZIP
  • Clear pass or fail
  • Up to five prioritized findings
  • No card and no account
Check one package free

Package Pass

$12.99 per package

One complete release decision

For an urgent handoff or a complete check before choosing a production pack.

  • Choose 1 to 7 package credits at checkout
  • Every finding, not a five-item preview
  • Journal rules and previous-version comparison
  • Downloadable JSON evidence and release ZIPs
  • API key, documentation, usage, and recovery
Buy a complete check Secure checkout by Stripe. Adjust the quantity before payment.

Production value

Team Credits

$149 one-time payment

100 packages at $1.49 each

For a production team checking recurring batches before delivery or publication.

  • 100 unique package credits, valid 12 months
  • Every finding, not a five-item preview
  • Use one journal-rules profile per check
  • Comparison with previous XML versions
  • Downloadable JSON evidence and release ZIPs
  • API key, documentation, usage, and recovery
Buy 100 credits for $149 Secure self-service checkout by Stripe. Paid access is delivered by email after payment.

API Credits

$499 one-time payment

1,000 packages at about $0.50 each

For OJS providers, XML vendors, and automated production pipelines.

  • 1,000 unique package credits, valid 12 months
  • Every finding and evidence download
  • Journal rules and version comparison
  • Server-to-server API key and usage view
  • GitHub Action and OJS integration support
Buy 1,000 API credits

Need more than 1,000 packages, several journals, or a custom profile rollout? Discuss production pricing.

Already purchased

One place for your key, usage, and next step.

Enter the email used at checkout. We send a secure link that opens your paid access without a password. From there you can see package slots, expiry, copy the API key, open the workspace, or follow the API guide.

Recover access

Email my secure access link.

No purchase yet? Buy one urgent check for $12.99, 100 team credits for $149, or 1,000 API credits for $499.

Compare plans

Plain answers

What you are buying, without the XML jargon.

What is JATS?

JATS means Journal Article Tag Suite. It is a standardized XML format used by publishers and archives to describe journal articles, including titles, authors, sections, references, tables, figures, and identifiers.

How do I know whether I have a JATS file?

You probably have JATS if your production workflow produces an .xml article file with elements such as article, front, body, back, article-meta, or ref-list. If your starting point is only Word or PDF, JATS Verify is not the conversion service you need.

Does JATS Verify create XML from Word or PDF?

No. It checks JATS XML you already receive or produce. It works after conversion and before delivery, publication, or archival submission.

Why pay when free JATS validators exist?

Free schema and destination validators are useful. JATS Verify checks a broader package layer: linked assets, cross-references, IDs, journal rules, version changes, and reproducible handoff evidence. It does not replace destination-specific checks.

What exactly happens after I pay?

Stripe confirms the one-time payment, then JATS Verify emails a secure Access Center link and API key for the package credits purchased. Credits remain valid for 12 months. Use the same key in the browser workspace or in a server-to-server API request.

Do you keep my article files?

Uploaded XML and assets are processed for the request and removed when it completes. Limited hashed usage records and finding counts are retained to enforce access limits.

Does a pass guarantee PubMed Central or journal acceptance?

No. A pass means the package satisfied the configured technical checks. Editorial policies and destination-specific review can add requirements outside this service.

Can our production system call this through an API?

Yes. Every paid option includes a server-to-server key for the JSON inspection and release-bundle endpoints. The public API guide explains authentication, upload fields, limits, responses, and usage checks. Ongoing higher-volume integrations are scoped after the first batch proves useful.