openalex.org valid

OpenAlex Help

Unified help, documentation, API reference, and tutorials for OpenAlex,

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T18:44:28.806Z. Cached copy · Source on openalex.org

# OpenAlex Help

> Unified help, documentation, API reference, and tutorials for OpenAlex,
> the open catalog of the global research system.

Every page on this site has a raw-markdown sibling: append `.md` to its path.

New here? Start with the [Quickstart](https://help.openalex.org/quickstart/): get real data out of
OpenAlex in five minutes ([markdown](https://help.openalex.org/quickstart.md)).

No API key? An AI agent can get a free one for its user in one call (ask the user for their email; never invent one):
`POST https://api.openalex.org/api-keys` with `{"email": "<your user's email>"}`. We email the user a link,
and the key works ($1 a day) once they click it. Details: [Authentication](https://help.openalex.org/api/authentication/#getting-a-key-for-your-user)
and [auth.md](https://help.openalex.org/auth.md).

Record pages on openalex.org are open to agents and scripts. Every OpenAlex ID is a URL
(https://openalex.org/W2741809807) that returns the record as server-rendered HTML with schema.org
JSON-LD, or as Markdown when you send `Accept: text/markdown`. Search and list pages on openalex.org
are not served to scripts. The API has more data and is faster: the same record is
https://api.openalex.org/works/W2741809807 (single-record lookups are free), and one call can fetch
100 records by ID, or filter, search, group and page. Details: [Reading openalex.org pages](https://help.openalex.org/access/agents/#reading-openalexorg-pages).

Field and vocabulary semantics (what each entity is, where its records come from,
what every attribute means, controlled-vocabulary definitions) are canonical under
`/data/` — e.g. the works field dictionary at `/data/works/` and work types
at `/data/work-types/`. The `/access/` pages cover access to OpenAlex in both directions —
read access (querying, ways to get the data, pricing) and write access (fixing errors);
the `/api/` pages cover endpoint mechanics (filtering,
sorting, grouping, query syntax).

## How-to

- [Using OpenAlex with an AI assistant](https://help.openalex.org/how-to/ai-assistants/): Most of what you'd do with OpenAlex, an AI assistant can do for you. In Claude, the free OpenAlex connector makes it easiest: add it from Claude's connector directory in about two minutes. Any assistant can also use OpenAlex with your API key, and a ChatGPT connector is coming soon. ([markdown](https://help.openalex.org/how-to/ai-assistants.md))
- [Analyzing your institution](https://help.openalex.org/how-to/analyzing-your-institution/): Count an institution's outputs on the OpenAlex website and break them down by type, subject, SDG, open access, citations, collaborators, and journals — plus APC spend and open-access trends. ([markdown](https://help.openalex.org/how-to/analyzing-your-institution.md))
- [API recipes](https://help.openalex.org/how-to/api-recipes/): Copy-paste URL patterns for the most common OpenAlex API questions — finding works, filtering, grouping, batch-fetching, sampling, and following citations
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=openalex.org · GET /v1/domain/openalex.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for openalex.org:
1. POST https://agentwebmap.com/v1/sites/openalex.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://openalex.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/openalex.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/openalex.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.