Crossref DOI Metadata QA
Pricing
from $33.50 / 1,000 metadata qa checks
Crossref DOI Metadata QA
A per-DOI QA verdict from official Crossref metadata — each DOI returns valid, not_found, or metadata_incomplete with every missing required field named. Billed per definitive verdict.
Pricing
from $33.50 / 1,000 metadata qa checks
Rating
0.0
(0)
Developer
NexGen Watch
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
20 hours ago
Last modified
Categories
Share
A per-DOI verdict product — not a metadata dump. Submit DOIs, get one deterministic QA verdict each: valid, not_found, or metadata_incomplete (with every missing required field named). Billed per definitive verdict.
How it behaves
Each DOI is canonicalized (https://doi.org/…, doi: prefixes stripped) and syntax-validated. A syntactically valid DOI is looked up once against the official keyless Crossref REST API (contact-bearing UA, polite rate limit, bounded retries). The buyer-selected required-field profile (requiredFields, default: title, author, issued, type, container-title, publisher) is tested against the record:
- all present → valid;
- some missing → metadata_incomplete, with the missing fields named;
- DOI not registered in Crossref → not_found.
Input order is preserved. The verdict record carries minimal identifying context only (title, type, publisher) — the payload is the verdict, never a metadata dump.
Billing
| Event | FREE | BRONZE | SILVER | GOLD+ |
|---|---|---|---|---|
apify-actor-start (one-time actor start) | $0.02 | $0.02 | $0.02 | $0.02 |
metadata-qa-check (per definitive verdict) | $0.05 | $0.045 | $0.04 | $0.0335 |
A definitive verdict (valid / not_found / metadata_incomplete) is charged once. Locally-invalid DOI syntax and Crossref outages are emitted but never charged. Start fee $0.02.
Differentiation
- vs our
crossref-citation-mcp: this is batch QA verdicts for metadata operations, not per-call retrieval for agents. - vs the store comparators: deterministic, order-preserving verdicts with named missing fields, not search exports.
Source
https://api.crossref.org/works
