# Crossref DOI Citation Export — CSL JSON Metadata (`jpmarketdata/crossref-doi-citation-export`) Actor Resolve DOI lists to citation metadata and CSL JSON. Preserve author order and date precision, with source provenance for research and citation workflows. - **URL**: https://apify.com/jpmarketdata/crossref-doi-citation-export.md - **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community) - **Categories:** Developer tools, Automation - **Security:** Limited permissions - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing $1.00 / 1,000 delivered records This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Crossref DOI Citation Export Resolve a selected DOI bibliography into structured metadata and CSL JSON for citation managers and research agents. ### Input `dois` accepts 1–20 DOI strings or https://doi.org URLs. The default resolves `10.1038/s41586-020-2649-2`. Blank, malformed, unknown input keys, or more than 20 entries fail before retrieval. DOI identity is case-insensitive and duplicate identifiers are fetched and charged once. All selected DOIs must resolve; a missing record fails the batch. ### Output One row per unique DOI: title, ordered authors, container titles, source work type, publisher, publication date-parts, separate print/online date-parts, deposited/indexed timestamps, separate outgoing-reference and incoming-citation counts, and a CSL JSON projection. CSL issued uses the source published date-parts and never pads an absent month/day. Source-specific types map to CSL standard types; unsupported types use `document` and remain visible in `workType`. Null/empty optional metadata means the source did not provide it. Every row also includes source relation/update metadata and publisher license links. Every row includes DOI/API URLs, Crossref attribution, metadata reuse guidance, and retrieval time. No abstract, reference text, PDF, or full text is copied. Source relation/update-to metadata, update-policy URL and publisher license links are retained. These are source assertions, not a derived retraction/currentness/reuse verdict; no linked text is fetched. SUMMARY metadata in key-value storage records requested/unique/delivered counts and limits. ### Limits 20 input entries and 20 unique output rows per run; sequential HTTP with at least one second between API requests; 429/5xx fail with sanitized actionable errors, with no automatic retry. Requests stop at the configured budget. Acquisition has a 180-second deadline and delivery a 90-second deadline; each HTTP request has a 30-second timeout. No discovery search, cursor pagination, OpenAlex, private API key, or external paid service is used. Timeout, source schema change, rate-limit exhaustion, and missing DOI fail visibly. This is metadata retrieval; it does not assess evidence quality or make citation recommendations. ### Pricing One `doi-delivered` event per validated unique dataset row at $0.001; no start fee and no trial events. Source records are collected and coverage checked before output. Apify's configured maximum chargeable event budget caps selection before source requests; if it permits fewer rows than unique DOI inputs, the run fails before requests and charges. Repeated runs are charged again for delivered records. No charge for duplicate inputs, failed retrievals, or SUMMARY. ### Privacy Public author names are retained only as required bibliographic attribution. Affiliations, contact addresses, publisher abstracts, credentials, cookies, contributor profiles, and source response headers are excluded. The Actor does not fetch DOI landing pages or linked documents. # Actor input Schema ## `dois` (type: `array`): 1–20 DOI strings or https://doi.org URLs. Each unique canonical DOI becomes one citation record and one billable event. All selected identifiers must resolve; unsupported values fail the run. ## Actor input object example ```json { "dois": [ "10.1038/s41586-020-2649-2" ] } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("jpmarketdata/crossref-doi-citation-export").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("jpmarketdata/crossref-doi-citation-export").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call jpmarketdata/crossref-doi-citation-export --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/crossref-doi-citation-export" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/8E2PlazXzN5RIxdpT/builds/vqAVcLunLXSl8rSyS/openapi.json