Publishers
Drop-in, standards-first
Batch minting, a tiny update badge, JSON-LD on every page, and OAI-PMH for harvesters—plus signed receipts and mirror fixity for editorial assurance.
What you get
Batch/API minting with versioning (root + v1…vN)
DOI import (optional) to bridge legacy content
Update-Checker widget (≤12 KB, SRI/CSP-ready)
Machine-readable outputs: JSON-LD + CSL-JSON/BibTeX/RIS
OAI-PMH Identify/GetRecord; nightly snapshots
Nightly fixity checks across primary↔mirror storage
Disputes: visible banner + audit line, with fast triage
Typical integration path (1–2 days)
1
DNS TXT verification
Verify publisher domain ownership
2
API key
Scoped, rate-limited access
3
Mint on acceptance
Or at publication time
4
Add the badge
Update-Checker to article pages
5
Expose JSON-LD
We emit; keep canonical links consistent
6
Enable OAI-PMH
Endpoint for your catalogue
Editorial assurance
- • Every version has a receipt you can inspect
- • Nightly fixity checks across primary↔mirror storage
- • Disputes render visibly; decisions publish an audit line
Technical features
- • Lightweight widget (≤12 KB)
- • SRI/CSP-ready implementation
- • JSON-LD structured data
Standards support
- • OAI-PMH compliance
- • Multiple export formats
- • DOI interoperability
FAQ
Will this conflict with DOIs?
No. Use both; we add sameAs pointers to avoid duplication.
Who hosts landing pages?
We can host resolver pages, or you can deep-link to your own.
Any cost?
Individual minting is free; publisher tiers add quotas, tooling, and support.