Semantic Scholar citing papers API

Use the Semantic Scholar citing papers API to retrieve citing works and the citation information published by the source. Identify a paper through a supported paper ID, DOI, arXiv reference or source URL, then filter citation intent and order to inspect later citing papers and their citation contexts. Trace later work citing a publication, inspect citation relationships, or expand a literature review from a known paper. Citation direction is forward from the selected work to later citing records, not the selected paper’s own bibliography. The detail page provides request and response examples, supported parameters, and usage pricing.

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
Paper id: a Semantic Scholar id (40 hex characters), `CorpusId:<n>`, `DOI:<doi>`, `ARXIV:<id>`, `PMID:<n>`, `PMCID:<id>`, `MAG:<n>`, `ACL:<id>`, `URL:<link>`, a bare DOI or arXiv id, or a semanticscholar.org / doi.org / arxiv.org link.
Optional parameters (8)
Order.
Only citations with this intent.
Page number, from 1.
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: Semantic Scholar (Allen Institute for AI)",
  "cached": false,
  "count": 10,
  "credits_used": 1,
  "id": "ARXIV:1706.03762",
  "intent": "all",
  "intent_counts": {
    "background": 42515,
    "methodology": 49574,
    "result": 896
  },
  "items": [
    {
      "abstract": "With recent advances in network architectures for Neural Machine Translation (NMT) recurrent models have effectively been replaced by either…",
      "authors": [
        {
          "author_id": "2120874",
          "name": "Tobias Domhan"
        }
      ],
      "citation_count": 81,
      "contexts": [
        {
          "intents": [],
          "text": "The Transformer sets itself apart from both standard RNN models and convolutional model by more than just the multi-head self-attention bloc…"
        },
        {
          "intents": [
            "methodology"
          ],
          "text": "…neural network as Source attention Using the source hidden vectors U , the source attentions are computed as Self-attention Self-attention …"
        },
        "… 13 more"
      ],
      "corpus_id": 51880415,
      "fields_of_study": [
        "Computer Science"
      ],
      "is_influential": true,
      "paper_id": "cf0545d9f171c8e2d88aed13cd7ad60ff2ab8fb5",
      "reference_count": 27,
      "title": "How Much Attention Do You Need? A Granular Analysis of Neural Machine Translation Architectures",
      "tldr": "This work takes a fine-grained look at the different architectures for NMT and introduces an Architecture Definition Language (ADL) allowing…",
      "url": "https://www.semanticscholar.org/paper/How-Much-Attention-Do-You-Need-A-Granular-Analysis-Domhan/cf0545d9f171c8e2d88aed13cd7ad60ff2ab8fb5",
      "venue": "ACL",
      "year": 2018
    },
    {
      "abstract": "Recent advancements in attention mechanisms have replaced recurrent neural networks and its variants for machine translation tasks. Transfor…",
      "authors": [
        {
          "author_id": "1557931630",
          "name": "Prakhar Thapak"
        },
        {
          "author_id": "1557917362",
          "name": "P. Hore"
        }
      ],
      "citation_count": 0,
      "contexts": [
        {
          "intents": [],
          "text": "We use the scaled dot-product attention that takes care of hard softmax problem [15] along with the proposed contextword attention."
        },
        {
          "intents": [],
          "text": "Transformer[15] introduced in 2017 achieved state-of-the-art results on machine translation task using only attention mechanism eschewing re…"
        },
        "… 8 more"
      ],
      "corpus_id": 212657723,
      "fields_of_study": [
        "Computer Science"
      ],
      "is_influential": true,
      "paper_id": "e42e3e09af8a56381c65aa8a8ddaee63fb321936",
      "reference_count": 37,
      "title": "Transformer++",
      "tldr": "This work argues that certain dependencies among words could be learned better through an intermediate context than directly modeling word-w…",
      "url": "https://www.semanticscholar.org/paper/Transformer++-Thapak-Hore/e42e3e09af8a56381c65aa8a8ddaee63fb321936",
      "venue": "ArXiv",
      "year": 2020
    },
    "… 8 more"
  ],
  "next_page": 2,
  "page": 1,
  "paper_id": "204e3073870fae3d05bcbc2f6a8e263d9b72e776",
  "sort": "relevance",
  "total": 201689,
  "total_pages": 20169
}

Response result

Response structure

Inferred from examples
  • attributionstring
  • cachedboolean
  • countinteger
  • credits_usedinteger
  • idstring
  • intentstring
  • intent_countsobject
    • backgroundinteger
    • methodologyinteger
    • resultinteger
  • items(object | string)[]
    • abstractstring
    • authorsobject[]
      • author_idstring
      • namestring
    • citation_countinteger
    • contexts(object | string)[]
      • intentsstring[]
      • textstring
    • corpus_idinteger
    • fields_of_studystring[]
    • is_influentialboolean
    • paper_idstring
    • reference_countinteger
    • titlestring
    • tldrstring
    • urlstring
    • venuestring
    • yearinteger
  • next_pageinteger
  • pageinteger
  • paper_idstring
  • sortstring
  • totalinteger
  • total_pagesinteger

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 Semantic Scholar citing papers API with your agent

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