CORE repository and journal search API

Use the CORE repository and journal search API to retrieve research-repository metadata, identifiers and harvest information. Search by repository or university name, or a CORE query expression, and page through data-provider records containing institutional identifiers, locations and harvesting endpoint references. Identify the repository holding a research record, inspect its harvesting details, or connect repository identifiers to indexed outputs. Harvesting information describes the indexed provider and should not be confused with downloading every paper held by that repository. The detail page provides request and response examples, supported parameters, and usage pricing.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Search terms, such as a university name.
Optional parameters (7)
Results per page, up to 100 (default 10).
Page number (1-based).
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON exports are not exposed.
Native CSV/NDJSON record selector; it has no effect on this JSON-only product.

Sample response

{
  "cached": false,
  "count": 2,
  "credits_used": 1,
  "items": [
    {
      "aliases": [],
      "country": "GB",
      "created": "2011-07-07T15:11:00+01:00",
      "email": "[email protected]",
      "homepage": "https://radar.brookes.ac.uk",
      "id": 93,
      "institution": "Oxford Brookes University",
      "latitude": 51.793,
      "logo": "https://api.core.ac.uk/data-providers/93/logo",
      "longitude": -1.2115,
      "metadata_format": "oai_dc",
      "name": "Oxford Brookes University: RADAR",
      "oai_pmh_url": "https://radar.brookes.ac.uk/radar/oai",
      "opendoar_id": 1680,
      "other_identifiers": [],
      "ror_id": null,
      "software": null,
      "type": "REPOSITORY",
      "url": "https://core.ac.uk/data-providers/93"
    },
    {
      "aliases": [],
      "country": "GB",
      "created": "2011-07-01T15:54:00+01:00",
      "email": "[email protected]",
      "homepage": "https://ora.ox.ac.uk",
      "id": 88,
      "institution": "University of Oxford ",
      "latitude": 51.7466,
      "logo": "https://api.core.ac.uk/data-providers/88/logo",
      "longitude": -1.2709,
      "metadata_format": "rioxx_terms_v3",
      "name": "Oxford University Research Archive",
      "oai_pmh_url": "https://ora.ox.ac.uk/oai2",
      "opendoar_id": 1064,
      "other_identifiers": [],
      "ror_id": null,
      "software": null,
      "type": "REPOSITORY",
      "url": "https://core.ac.uk/data-providers/88"
    }
  ],
  "next_page": null,
  "page": 1,
  "query": "oxford",
  "total": 2
}

Response result

Response structure

Inferred from examples
  • cachedboolean
  • countinteger
  • credits_usedinteger
  • itemsobject[]
    • aliasesunknown[]
    • countrystring
    • createdstring
    • emailstring
    • homepagestring
    • idinteger
    • institutionstring
    • latitudenumber
    • logostring
    • longitudenumber
    • metadata_formatstring
    • namestring
    • oai_pmh_urlstring
    • opendoar_idinteger
    • other_identifiersunknown[]
    • ror_idnull
    • softwarenull
    • typestring
    • urlstring
  • next_pagenull
  • pageinteger
  • querystring
  • totalinteger

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use CORE repository and journal search API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.