FreeHow credits work →
DB
CS bibliographydblp publication search API

DBLP

dblp is the computer science bibliography maintained by Schloss Dagstuhl, covering journal articles and conference papers, and released under CC0. Through ScholarMuse an agent can search dblp publications by keyword when it names dblp as a source, and get clean venue, year and page data for computer science references.

ScholarMuse tools: search_papers. Each successful call uses credits.

Ask your agent

Search dblp for papers on Raft consensus and list the venue and year of each.
Find the dblp entry for 'Attention Is All You Need' and give me the venue and pages.
Use dblp to find papers on learned index structures published between 2018 and 2020.

What your agent gets back

Every record carries id, source, title, url, license, attribution and retrievedAt. The fields below are the data that comes from DBLP.

search_papers

Only when the agent passes dblp in sources. It is not part of the default search.

doi
DOI when dblp records one
authors
Author names, first 12, homonym numbers removed
year
Publication year
venue
Conference or journal abbreviation
volume
Volume
pages
Page range
type
dblp publication type
openAccess
True when dblp marks the entry as open
openAccessUrl
Electronic edition link for open entries

What it covers

  • Computer science publications indexed by dblp, mainly conference papers and journal articles.
  • Keyword search over dblp's publication index, ranked by dblp.

Limits

  • dblp sometimes answers server networks with a bot check instead of data. The call then reports dblp as a failed source.
  • No abstracts, citation counts or retraction flags come from dblp.
  • The dblp API has no year or open-access filter. With such a filter set, the top 100 matches are fetched and filtered afterwards, so older matches can be missed.
  • At most 25 results per call, and get_paper does not look up dblp keys.

How ScholarMuse reaches DBLP

The connector calls dblp.org/search/publ/api directly and asks for JSON. No API key is sent. Requests are spaced 1.5 seconds apart and are not retried on failure.

Search results are cached for up to 6 hours.

API key: the upstream API can be called without one, so you do not add one.

Licence and attribution

Licence: CC0-1.0

Data from the dblp computer science bibliography (dblp.org), CC0.

Records that come from DBLP carry this licence and attribution. When you cite the data in a paper, follow DBLP's own citation guidance.

FAQ

ScholarMuse is not an official DBLP product. It is one MCP server for academic data, and its search_papers tool queries DBLP. An agent connected to ScholarMuse can use DBLP without a separate server.

No. The DBLP API can be called without a key, and ScholarMuse does not ask you for one. You sign in to ScholarMuse once and your agent calls the tool.

The connector calls dblp.org/search/publ/api directly and asks for JSON. No API key is sent. Requests are spaced 1.5 seconds apart and are not retried on failure. Search results are cached for up to 6 hours.

CC0-1.0. Attribution: Data from the dblp computer science bibliography (dblp.org), CC0. Records that come from DBLP carry this licence and attribution.

Yes. Each successful call to search_papers uses credits, and a call that fails is not charged. Current price: Search papers, 1 credit / call.