research.org

Resolve a research organization via the Research Organization Registry (ROR). Pass id (a ROR id like 056y0v115 or its full URL) to fetch one org, or name to search by free text. Returns the canonical ROR id and name, organization type, status, founding year, location (city, country, GeoNames coordinates), website, Wikipedia link, external identifiers (GRID, ISNI, Wikidata, Crossref Funder), parent/child relationships, and aliases/acronyms. Data: ROR, free and CC0. The canonical institution key in scholarly metadata — pair with /api/papers/search and /api/paper/doi-lookup (author affiliations) and /api/research/author (ORCID). Use to disambiguate an institution name to a stable id before joining datasets.

price
$0.0012 USDC per call
method
GET/api/research/org
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The org API is a pay-per-call research endpoint built for AI agents and autonomous software. Resolve a research organization via the Research Organization Registry (ROR).

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in org data source for an agent tool-use loop, an MCP host, or a backend that needs research data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
idstring
min 2 chars · max 120 chars
namestring
min 2 chars · max 200 chars
limitinteger
min 1 · max 20

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/research/org?id=xx&name=xx&limit=5'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/research/org?id=xx&name=xx&limit=5' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/research/org?id=xx&name=xx&limit=5'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.research.org({
  "id": "xx",
  "name": "xx",
  "limit": 5
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.research.org(id="xx", name="xx", limit=5)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "research.org",
    "arguments": {
      "id": "xx",
      "name": "xx",
      "limit": 5
    }
  }
}

Response

FieldTypeDescription
queryobject
totalnumber
countnumber
organizationsarray
sourcesarray
Example response datajson
{
  "query": {
    "id": "example",
    "name": "example"
  },
  "total": 1,
  "count": 1,
  "organizations": [
    {
      "id": "example",
      "name": "example",
      "established": 1,
      "status": "example",
      "types": [
        "example"
      ],
      "location": {
        "city": "example",
        "countryCode": "example",
        "countryName": "example",
        "subdivision": "example",
        "lat": 1,
        "lng": 1,
        "geonamesId": 1
      },
      "website": "example",
      "wikipedia": "example",
      "externalIds": [
        {
          "type": "example",
          "preferred": "example",
          "all": [
            "example"
          ]
        }
      ],
      "relationships": [
        {
          "type": "example",
          "id": "example",
          "label": "example"
        }
      ],
      "aliases": [
        "example"
      ]
    }
  ],
  "sources": [
    {
      "provider": "example",
      "url": "example",
      "license": "example"
    }
  ]
}

FAQ

Do I need an API key to use the org API?
No. research.org is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the org API cost?
$0.0012 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the org API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call research.org from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: org api · research org api · org api for ai agents · x402 research api · org api no api key · pay per call org api · research api