Read researcher publication and identity data from an ORCID record via the Public API
domain: pub.orcid.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use the production Public API base URL https://pub.orcid.org/v3.0/ (sandbox: https://pub.sandbox.orcid.org/v3.0/) for testing without touching real records.
Request a record with GET /v3.0/{orcid-id}/record, or narrower sections like /person or /works, using the /read-public scope.
For data visible only to trusted parties, use the Member API (api.orcid.org) with the /read-limited scope instead -- this requires an ORCID member API client registration.
Parse responses per the ORCID v3.0 message schema documented in the ORCID-Source and orcid-model GitHub repos.
Register a client via ORCID's developer tools to obtain credentials for authenticated Member API access when public data isn't sufficient.
Known gotchas
The Public API only returns data the researcher has marked public; trusted-party-only fields require Member API access and the record owner's OAuth consent.
Sandbox and production ORCID iDs/records are entirely separate test data -- production IDs will not resolve in sandbox or vice versa.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?