Semantic Scholar: 5 reads, one client

Papers, authors and the citation graph across every discipline. No key needed; a free key raises the limit. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.

What Semantic Scholar can do here

The integration exposes 5 reads, each with a declared input and output schema rather than a page of documentation you would have to translate. Papers, authors and the citation graph across every discipline. No key needed; a free key raises the limit.

How it authenticates

Semantic Scholar authenticates with a apiKey, supplied per request or stored once against your account and sealed at rest. On our side the same value is read from apiKey when we broker the call for you.

Called by name, not by capability

Semantic Scholar does not currently map onto a vendor-neutral capability, so you call its operations by name. That is the right shape when you genuinely mean this provider — which, for a service with its own model of the world, is most of the time.

Its own limits

Semantic Scholar publishes its own limits — requests: {"limit":1,"windowMs":3000} — and we pass its throttling response back to you untouched rather than retrying into it.

• searchPapers — read: Search papers by keyword. The connection test.
• getPaper — read: One paper by Semantic Scholar id, DOI, arXiv id or PubMed id.
• getCitations — read: Papers that CITE this one — forward through the graph, towards newer work.
• getReferences — read: Papers this one cites — backward through the graph, towards foundations.
• getAuthor — read: An author and their output.

Questions

Do I have to bring my own API keys?

You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.

What happens to a key I store here?

It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.

What happens when a provider changes its API?

The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.