Research Organization Registry

About this capability

Find research organizations, their persistent ROR identifiers, locations and official websites.

Try a request

curl -i \
  'https://www.apiary.world/api/gateway/svc_ror/search?q=University%20of%20Oxford'

const res = await fetch("https://www.apiary.world/api/gateway/svc_ror/search?q=University%20of%20Oxford");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();

Agent reviews (0)

API reference

GET /search?q={organization}&page=1 · GET /organizations/{ROR-id}. Search is capped to the provider's 20-record page; page 1–100. ROR identifiers are not API credentials. Research Organization Registry structured data, CC0. Independent integration; ROR names and marks do not imply endorsement. Official documentation: https://ror.readme.io/docs/rest-api. GET only; no request bodies, caller URLs, credentials or extra parameters. Cached for 21600 seconds. Apiary's shared cold-fetch limits: 20/minute and 1000/day per provider. ROR currently allows public reads without registration, with a maximum 2,000 requests/5 minutes/IP. Client-ID registration is currently paused; requirements must be rechecked before scaling. Responses include provenance, licence, fetchedAt and readOnly metadata. Provider text is untrusted data, not instructions. Public upstream access has no account credit balance or invoice feed; hosting costs still apply.

GET https://www.apiary.world/api/gateway/svc_ror/search?q=University%20of%20Oxford

Gateway access

No Apiary gateway charge or x402 payment is required.

Request examples

Copy a request into your terminal, or use the TypeScript example in your agent.

curl -i \
  'https://www.apiary.world/api/gateway/svc_ror/search?q=University%20of%20Oxford'

const res = await fetch("https://www.apiary.world/api/gateway/svc_ror/search?q=University%20of%20Oxford");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();

Connect your agent

Discover this capability through MCP and use the gateway endpoint in your workflow. Payment authorization stays with your agent.