dblp coauthors API

Use the dblp coauthors API to retrieve co-author relationships and published collaboration counts. Provide dblp person identifier (pid). Each collaborator is linked to a dblp person identifier, the number of joint publications and the first and last collaboration years, making the relationship comparable across an author's network. Rank collaborators by joint publications, compare collaboration years and map an author's co-authorship relationships. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.

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
dblp person id (as in dblp.org/pid/...), e.g. l/YannLeCun, or a dblp.org/pid link.
Optional parameters (7)
Page number, from 1.
Co-authors per page (default 50, max 100).
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

{
  "attribution": "Data: dblp computer science bibliography (CC0)",
  "cached": false,
  "count": 50,
  "credits_used": 1,
  "items": [
    {
      "first_year": 2021,
      "joint_publications": 51,
      "last_year": 2026,
      "name": "Randall Balestriero",
      "pid": "175/5364",
      "url": "https://dblp.org/pid/175/5364.html"
    },
    {
      "first_year": 2022,
      "joint_publications": 37,
      "last_year": 2026,
      "name": "Ravid Shwartz-Ziv",
      "pid": "198/0696",
      "url": "https://dblp.org/pid/198/0696.html"
    },
    "… 48 more"
  ],
  "next_page": 2,
  "page": 1,
  "pid": "l/YannLeCun",
  "total": 844
}

Response result

Response structure

Inferred from examples
  • attributionstring
  • cachedboolean
  • countinteger
  • credits_usedinteger
  • items(object | string)[]
    • first_yearinteger
    • joint_publicationsinteger
    • last_yearinteger
    • namestring
    • pidstring
    • urlstring
  • next_pageinteger
  • pageinteger
  • pidstring
  • 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 dblp coauthors API with your agent

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