DOI Lookup — Crossref Titles, Venues, Dates and Citation Counts avatar

DOI Lookup — Crossref Titles, Venues, Dates and Citation Counts

Pricing

from $1.04 / 1,000 doi resolveds

Go to Apify Store
DOI Lookup — Crossref Titles, Venues, Dates and Citation Counts

DOI Lookup — Crossref Titles, Venues, Dates and Citation Counts

Crossref DOI lookup: Publication titles, venues, dates and citation counts. $0.0013 per DOI resolved; start extra; usage included; failed results uncharged.

Pricing

from $1.04 / 1,000 doi resolveds

Rating

0.0

(0)

Developer

Logan Parker

Logan Parker

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Features

Limited permissions

Share

Crossref DOI lookup returns publication titles, venues, dates and citation counts for reference checks, without authors, abstracts or full text. AI agents can call and pay through Apify MCP. List event rates are $0.0013 per DOI resolved; start is extra, usage is included and failed results are uncharged.

Example result

Example record for the minimal input under How to use it, as this Actor returned it on 2026-10-28 in a run of its production image; the record is kept unchanged with the release.

{
"doi": "10.1038/nphys1170",
"ok": true,
"resolvedDoi": "10.1038/nphys1170",
"titles": [
"Measured measurement"
],
"containerTitles": [
"Nature Physics"
],
"workType": "journal-article",
"publicationDateParts": [
2009,
1
],
"citationCount": 11,
"source": "Crossref"
}

How to use it

Start a run in Apify Console, by API or from an agent with an input like this one — it is the input Apify runs every day to test this Actor:

{"dois": ["10.1038/nphys1170"]}

Start with the minimal JSON example above, then adjust the fields in the table below. Read the Example result and Output fields sections for the returned record, Errors for failure codes, and Events and prices for result events and the separate platform start.

FieldTypeMeaning
doisarray1–100 DOI strings; one metadata record per DOI; no author search, abstract extraction or full text. Use the public pool without a key, obey current rate headers, cap to one request per second and back off on 429.

Events and prices

EventTitleCharged whenFREE / BRONZESILVERGOLD / PLATINUM / DIAMOND
doi-resolvedDoi ResolvedOne successful input processed and its readable result stored.$0.0013$0.00117$0.00104

Platform usage is not passed through. Apify's automatic actor-start event remains $0.00005 per started GB (one GB or less counts once). The synthetic dataset-item event is absent. Charge limits stop further paying work; unprocessed inputs receive uncharged errors. Completed readable pending events are settled on abort.

Worked cost example: ten successful doi resolved events cost $0.013 at list, plus actor start. Failures are not included in that count.

Call it from an agent

Through Apify's MCP server (https://mcp.apify.com) use call-actor:

{
"actor": "hermeskd/crossref-doi-metadata",
"input": {
"dois": [
"10.1038/nphys1170"
]
},
"callOptions": {
"maxTotalChargeUsd": 0.01,
"timeout": 600
},
"waitSecs": 30
}

Then call get-dataset-items with the returned defaultDatasetId. Dedicated tool URL: https://mcp.apify.com?tools=hermeskd/crossref-doi-metadata

Output fields

FieldMeaning
doiThe caller supplied input, carried unchanged.
okTrue for a returned result; a failure is never charged.
resolvedDoiDOI from the Crossref response.
titlesTitle strings exactly as deposited.
containerTitlesVenue title strings.
workTypeCrossref work type.
publicationDatePartsDate parts as deposited; missing month/day are not invented.
citationCountis-referenced-by-count; Crossref coverage, not a universal citation count.
sourceCrossref attribution.
errorFailure, always uncharged.

Limits and run time

The revised result price clears the retained conservative cold/default model on the measured successful cases at BRONZE, SILVER and GOLD. Actual platform costs, cold startup, source smoke and the deploy pricing floor remain release gates; local measurements do not prove hosted costs.

Complete serialized results must fit an 8 MB delivery budget, including input identity and JSON escaping. Oversized results are refused without a result charge. Invalid Unicode in failure echoes is escaped. Failure input echoes longer than 8,192 characters are shortened; blank list entries refuse the whole input without silently dropping entries.

1–100 DOI strings; one metadata record per DOI; no author search, abstract extraction or full text. Use the public pool without a key, obey current rate headers, cap to one request per second and back off on 429.

The default run timeout is 600 seconds. Local production-image smoke on 2026-10-28: 5.41 seconds at 256 MB and one CPU (the smallest configured memory). Platform cold start, billing and pricing-floor verification remain deploy gates.

Errors

CodeMeaning
http_errorThe source answered an unsuccessful HTTP status.
download_failedThe request or connection failed within its bounded deadline.
source_schema_changedThe Crossref envelope, allowlisted field types or returned DOI identity changed; no raw response is returned.
source_rate_limitedCrossref asked for backoff; no result event charged.
robots_disallowedrobots.txt forbids fetching the URL; no request was made to it.
blocked_hostThe host is on the deny-list or resolves to a private or local address; no request was made.
too_largeThe response exceeded the size cap.
timeoutThe input did not finish within the run's time budget.
invalid_inputThe run input passed the input schema but cannot be used; the message names the field.
internal_errorUnexpected failure; the message carries the error class.
charge_limit_reachedThe run reached its maximum total charge; this input was not processed.

No failure record is charged. A run fails only when all input outcomes are Actor-side failures; caller errors and a mixture of caller/Actor failures do not fail the run.

Sources and terms

Only process content you have the right to process. URL fetches obey HermesBot robots-group selection, the shared deny-list, public-address checks on connections and redirects, honest identity, deadlines and rate limits. No caller credentials, cookies, CAPTCHA solving, residential proxies or evasion. Crossref public REST works endpoint, bibliographic metadata usable for any purpose per its REST documentation. Authors, ORCIDs, affiliations, abstracts, references and raw response excluded. No third-party full text fetched.

Not affiliated

This Actor is not affiliated with the source providers named here. Process only content you have the right to process.

Changelog

  • 1.0 (2026-10-28) — Initial implementation, main-path fixtures and local production-image examples verified; publication awaits the scheduled merge.