# ORCID Researcher Registry API

> ORCID: 20M+ researcher iDs searchable by name or institution, with each person's profile and works

- Vendor: `orcidresearcherregistryapi` · version 1.0 · category Science · tags orcid api, researcher id api, scholarly authors api, research works api, academic profiles api, publications api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/orcidresearcherregistryapi
- This document: https://apiclay.com/docs/orcidresearcherregistryapi.md
- OpenAPI 3.1: https://apiclay.com/api/orcidresearcherregistryapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `orcidresearcherregistryapi`
- Updated: 2026-11-18

## About

## ORCID Researcher Registry API

The public API of ORCID, the registry of persistent identifiers for researchers: search ORCID iDs with Solr queries on name, institution, keywords or other identifiers, and read a researcher's public record: their person section (names, other names, biography, keywords, websites, countries, external IDs) and their works (articles, books, datasets and more, with titles, types, dates, DOIs and other identifiers).

Data comes from **orcid.org** (https://orcid.org). Every route calls the source's own public API and returns it unchanged.

Typical flow: `/search?q=family-name:curie&amp;rows=10`, then `/person?orcid=` and `/works?orcid=`.

### Routes

#### GET `/search` - Search researchers
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| q | query | string | yes | Solr query, e.g. `family-name:curie`, `affiliation-org-name:"MIT"`, `einstein`. |
| start | query | number | no | Results to skip. |
| rows | query | number | no | Results per page, up to 1000. |

Returns: `num-found` and `expanded-result`: `orcid-id`, `given-names`, `family-names`, `credit-name`, `other-name`, `email`, `institution-name`.

#### GET `/person` - Person
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| orcid | path | string | yes | ORCID iD, e.g. `0000-0002-1825-0097`. |

Returns: `name`, `other-names`, `biography`, `researcher-urls`, `emails`, `addresses`, `keywords`, `external-identifiers`, `last-modified-date`.

#### GET `/works` - Works
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| orcid | path | string | yes | ORCID iD. |

Returns: `group` of works, each `work-summary` with `title`, `type`, `publication-date`, `journal-title`, `external-ids` (DOI, PMID, ISBN...), `url`, `source`.

### Caveats

- Records hold what each researcher made public on ORCID, including any public email.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by orcid.org.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /search — Search researchers
- Gateway: `GET https://api.apiclay.com/v1/api/orcidresearcherregistryapi/search`
- Public query params: `q` (string, required), `start` (number), `rows` (number)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /person — Person
- Gateway: `GET https://api.apiclay.com/v1/api/orcidresearcherregistryapi/person`
- Public query params: `orcid` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /works — Works
- Gateway: `GET https://api.apiclay.com/v1/api/orcidresearcherregistryapi/works`
- Public query params: `orcid` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/orcidresearcherregistryapi/search?q=<q>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
