Google Patent Search

Search Google patent and related scholarly records with structured results, pagination details, and search summaries. Available via REST API or MCP.

CostRecent 16 credits / call

Try online

POST · https://api.nexscope.ai/patents/searchMCP · nexscope_google_patent_search

What this API does

Search Google patent and related scholarly records with structured results, pagination details, and search summaries. The request accepts q, num, page, country, language. Its documented result includes errcode, errmsg, organicResults, searchParameters, searchInformation, searchMetadata, serpapiPagination, summary.

Google Patent Search API use cases

Investigate a product IP question

To investigate a product ip question, a compliance analyst submits q and num to Google Patent Search. The returned errcode, errmsg, organicResults help identify records relevant to the proposed product.

Collect records for an IP review

A compliance analyst uses Google Patent Search with q and num to collect records for an ip review. The returned errcode, errmsg, organicResults help collect bibliographic evidence for a specialist review.

Document evidence for specialist assessment

For this workflow, a compliance analyst calls Google Patent Search with q and num to document evidence for specialist assessment. The result helps document the records supporting an IP research question.

Google Patent Search API FAQ

What does the Google Patent Search API return?

Search Google patent and related scholarly records with structured results, pagination details, and search summaries. The documented output includes errcode, errmsg, organicResults, searchParameters, searchInformation, searchMetadata, serpapiPagination, summary. It corresponds to the supplied q, num, page, country, language. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Google Patent Search API cost?

The current documented cost is Recent 16 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Google Patent Search API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/patents/search with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_google_patent_search. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/patents/search

MCP method

nexscope_google_patent_search

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/patents/search

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/patents/search' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "num": 10,
  "q": "wireless earbuds"
}'

Code example

{
  "num": 10,
  "q": "wireless earbuds"
}

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

Code	Description
200	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

View parameters & response Try online

All categories/ Google Research Tools

POSThttps://api.nexscope.ai/patents/search

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Open tester

Endpoint

Method	`POST`
Path	`https://api.nexscope.ai/patents/search`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`q`	`string`	required	Google Patents search query supports official advanced query syntax (such as `owner:"Company"`, `inventor:"Name"`, date operator). Maximum 1000 characters.
`num`	`integer`	optional	Number of results per page, range 10–100. Example: 10
`page`	`integer`	optional	Page number, starting from 1. Example: 1
`country`	`string`	optional	Country code, multiple values separated by commas, for example `US,CN,WO`.
`language`	`string`	optional	Language, multiple values separated by English commas, use Google Patents official language value.
`before`	`string`	optional	Maximum date, format `priority\\|filing\\|publication:YYYYMMDD`.
`after`	`string`	optional	Minimum date, the format is the same as `before`.
`sort`	`string`	optional	Sorting method: `new` (latest) or `old` (earliest); if not transmitted, sorted by relevance.
`type`	`string`	optional	Result type: `PATENT` or `DESIGN`.
`status`	`string`	optional	Patent status: `GRANT` or `APPLICATION`.
`patents`	`boolean`	optional	Whether to include patent results. Example: true
`scholar`	`boolean`	optional	Whether to include Google Scholar results. Example: false
`litigation`	`string`	optional	Litigation Status: `YES` or `NO`.
`inventor`	`string`	optional	Inventor, multiple values are separated by commas.
`assignee`	`string`	optional	Assignee, multiple values separated by commas.
`clustered`	`boolean`	optional	Whether to aggregate by category; upstream currently only supports `true`.
`dups`	`string`	optional	Deduplication method; when not uploading, deduplication is based on patent family, `language` means deduplication is based on public text.

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

No response example is published for this API. Refer to the response fields below.

Response fields

Response field reference (39 fields)

Name	Type	Required	Description
`errcode`	`integer`	optional	`200` indicates success.
`errmsg`	`string`	optional	`ok` indicates success, otherwise it is an error description.
`organicResults`	`array`	optional	List of patent search results.
`searchParameters`	`object`	optional	Echoed query parameters (`q`/`engine`/`num`/`patents`/`page`/`scholar`, etc.).
`searchInformation`	`object`	optional	Retrieve meta information, including `total_results` (total number of hits), `total_pages` (total number of pages), `page_number` (current page).
`searchMetadata`	`object`	optional	Retrieve processing metadata.
`pagination`	`object`	optional	Paging information (`next`, `current`).
`serpapiPagination`	`object`	optional	Upstream paging information.
`summary`	`object`	optional	Result summary (including `cpc` classification aggregation, etc., only part of it is returned during classification aggregation).
`costToken`	`integer`	optional	Consume token.
`message`	`string`	optional	Upstream prompt information; successful but may appear under special circumstances. Most successful responses do not contain this field.
`publicationNumber`	`string`	optional	Public account.
`patentId`	`string`	optional	Patent ID.
`title`	`string`	optional	Patent or academic result titles.
`snippet`	`string`	optional	Abstracts of patent or academic results.
`inventor`	`string`	optional	Inventor.
`assignee`	`string`	optional	Assignee.
`filingDate`	`string`	optional	Application date.
`publicationDate`	`string`	optional	Publication or release date.
`grantDate`	`string`	optional	Authorization date.
`priorityDate`	`string`	optional	Priority date.
`language`	`string`	optional	Patent language.
`cpc`	`string`	optional	Collaborative patent classification (returned only when classification is aggregated).
`cpcDescription`	`string`	optional	Description of cooperative patent classification.
`countryStatus`	`object`	optional	The legal status of each country.
`position`	`integer`	optional	Search result location.
`rank`	`integer`	optional	Result ranking (may differ from `position` when aggregated).
`patentLink`	`string`	optional	Google Patents patent link.
`pdf`	`string`	optional	Patent PDF link.
`thumbnail`	`string`	optional	Patent thumbnail.
`figures`	`array`	optional	Patent image list, elements containing `thumbnail`, `full`.
`scholar`	`boolean`	optional	Whether it is a Google Scholar result.
`scholarId`	`string`	optional	Scholar result ID.
`scholarLink`	`string`	optional	Google Scholar results link.
`author`	`string`	optional	Scholar result author.
`authorEtal`	`boolean`	optional	Whether the Scholar result contains three or more authors.
`publicationVenue`	`string`	optional	Scholar results publication venue.
`urlHostname`	`string`	optional	Scholar result source domain name.
`serpapiLink`	`string`	optional	Result details API link.

Responses

Code	Description
200	Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429	Execution admission rate limit; honor Retry-After when present.
503	Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-in	X-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing or invalid API key (code 11209, including an incomplete or corrupted copy) or an expired website login session (code 12001), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json

Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_google_patent_search",
    "arguments": {
      "num": 10,
      "page": 1,
      "q": "wireless earbuds"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

What can you do with this API?

Data explained and practical use cases

AI Guide

Question

What data can Google Patent Search provide, and how might I use it?

AI answer

Google Patent Search returns matching patent records and, when requested, related scholarly results. You can narrow a query by country, date, document type, status, inventor, or assignee. Individual fields are optional, so inspect each result before relying on it.

Data category	Documented fields	What the values mean
Result identity and description	`organicResults`, `publicationNumber`, `patentId`, `title`, `snippet`	Matching records, their identifiers, titles, and short descriptions.
People and organizations	`inventor`, `assignee`	The named inventor and assignee when supplied.
Patent chronology	`filingDate`, `publicationDate`, `grantDate`, `priorityDate`	Dates associated with a patent record; each may be absent.
Classification and country status	`cpc`, `cpcDescription`, `countryStatus`, `summary.cpc`	Classification information and reported country-specific status. CPC aggregation is returned only in relevant results.
Documents and images	`patentLink`, `pdf`, `thumbnail`, `figures`	Links to a patent page or PDF and available preview images.
Scholarly matches	`scholar`, `scholarId`, `scholarLink`, `author`, `publicationVenue`	Identifies and describes related Scholar results when scholar searching is enabled.
Result counts and paging	`searchInformation.total_results`, `searchInformation.total_pages`, `searchInformation.page_number`, `pagination`, `serpapiPagination`	Reported hit counts and navigation information for reviewing more pages.

Search for wireless-earbud inventions and review titles, snippets, and linked patent documents to identify records worth reading.
- Prompt example: “I am researching a product design before launch. Could you search for wireless-earbud inventions and review titles, snippets, and linked patent documents to identify records worth reading? Show matching records and source links where the API provides them; ask me for any required identifier or filter.”
Filter by an assignee or inventor to examine the matching records attributed to that name.
- Prompt example: “I am researching a product design before launch. Could you filter by an assignee or inventor to examine the matching records attributed to that name? Show matching records and source links where the API provides them; ask me for any required identifier or filter.”
Compare filing, priority, publication, and grant dates across returned records when those dates are present.
- Prompt example: “I am researching a product design before launch. Could you compare filing, priority, publication, and grant dates across returned records when those dates are present? Show the returned values behind the comparison, and mark missing data.”
Use classification summaries to spot CPC groups represented in a clustered result set.
- Prompt example: “I am researching a product design before launch. Could you use classification summaries to spot CPC groups represented in a clustered result set? Show the relevant returned evidence and tell me what input you need from me.”
Include Scholar results to find related academic records alongside patent matches.
- Prompt example: “I am researching a product design before launch. Could you include Scholar results to find related academic records alongside patent matches? Show matching records and source links where the API provides them; ask me for any required identifier or filter.”

Data Example

Sample request and response

Request parameters

{
  "q": "USD1074038S1",
  "num": 10,
  "page": 1,
  "country": "US"
}

Response

{
  "code": 0,
  "msg": null,
  "data": {
    "summary": {
      "cpc": [
        {
          "percentage": 100,
          "key": "Total",
          "frequency": [
            {
              "year_range": "2022-2025",
              "percentage": 0.1
            }
          ]
        }
      ],
      "inventor": [
        {
          "percentage": 100,
          "key": "Dan Zhang",
          "frequency": [
            {
              "year_range": "2022-2025",
              "percentage": 0.1
            }
          ]
        },
        {
          "percentage": 100,
          "key": "Total",
          "frequency": [
            {
              "year_range": "2022-2025",
              "percentage": 0.1
            }
          ]
        }
      ],
      "assignee": [
        {
          "percentage": 100,
          "key": "Dan Zhang",
          "frequency": [
            {
              "year_range": "2022-2025",
              "percentage": 0.1
            }
          ]
        },
        {
          "percentage": 100,
          "key": "Total",
          "frequency": [
            {
              "year_range": "2022-2025",
              "percentage": 0.1
            }
          ]
        }
      ]
    },
    "searchMetadata": {
      "raw_html_file": "https://serpapi.com/searches/ZsPXbn5fOkjtjElJ5-ohwbWOOkSOGZonm17z_DvhSCk/6ac7ce0c6adf276862bcb5ec.html",
      "markdown_endpoint": "https://serpapi.com/searches/ZsPXbn5fOkjtjElJ5-ohwbWOOkSOGZonm17z_DvhSCk/6ac7ce0c6adf276862bcb5ec.md",
      "created_at": "2026-10-08 17:08:28 UTC",
      "processed_at": "2026-10-08 17:08:28 UTC",
      "id": "6ac7ce0c6adf276862bcb5ec",
      "prettify_html_file": "https://serpapi.com/searches/ZsPXbn5fOkjtjElJ5-ohwbWOOkSOGZonm17z_DvhSCk/6ac7ce0c6adf276862bcb5ec.prettify",
      "total_time_taken": 1.47,
      "json_endpoint": "https://serpapi.com/searches/ZsPXbn5fOkjtjElJ5-ohwbWOOkSOGZonm17z_DvhSCk/6ac7ce0c6adf276862bcb5ec.json",
      "google_patents_url": "https://patents.google.com/xhr/query?url=q%3DUSD1074038S1%26country%3DUS%26page%3D0%26num%3D10%26patents%3Dtrue",
      "status": "Success"
    },
    "pagination": {},
    "organicResults": [
      {
        "snippet": "CLAIM The ornamental design for a table lamp, as shown and described.",
        "thumbnail": "https://patentimages.storage.googleapis.com/9e/cb/f0/dfbcb343ca0f95/USD1074038-20250506-D00000.png",
        "filingDate": "2024-11-20",
        "figures": [
          {
            "thumbnail": "https://patentimages.storage.googleapis.com/85/be/61/2327d1a5c507fd/USD1074038-20250506-D00000.png",
            "full": "https://patentimages.storage.googleapis.com/e6/5c/ea/2ef941b70da025/USD1074038-20250506-D00000.png"
          },
          {
            "thumbnail": "https://patentimages.storage.googleapis.com/8d/c6/2a/53557c28643e9d/USD1074038-20250506-D00001.png",
            "full": "https://patentimages.storage.googleapis.com/cf/15/b3/9e5c34b92a4a51/USD1074038-20250506-D00001.png"
          },
          {
            "thumbnail": "https://patentimages.storage.googleapis.com/01/7a/d3/4ca5bb6e1cfc9e/USD1074038-20250506-D00002.png",
            "full": "https://patentimages.storage.googleapis.com/83/fa/64/d19e4c96742c5d/USD1074038-20250506-D00002.png"
          },
          {
            "thumbnail": "https://patentimages.storage.googleapis.com/c5/a8/b4/443ae0caac812d/USD1074038-20250506-D00003.png",
            "full": "https://patentimages.storage.googleapis.com/20/62/9c/e0b162379c75de/USD1074038-20250506-D00003.png"
          },
          {
            "thumbnail": "https://patentimages.storage.googleapis.com/9d/53/f6/caff2c397f07e7/USD1074038-20250506-D00004.png",
            "full": "https://patentimages.storage.googleapis.com/65/b3/02/72c6481a93eb44/USD1074038-20250506-D00004.png"
          },
          {
            "thumbnail": "https://patentimages.storage.googleapis.com/2b/67/94/d2d4e0f1a22d97/USD1074038-20250506-D00005.png",
            "full": "https://patentimages.storage.googleapis.com/f2/30/82/581d43b48873d6/USD1074038-20250506-D00005.png"
          },
          {
            "thumbnail": "https://patentimages.storage.googleapis.com/ec/8e/0d/2e5b5716269f30/USD1074038-20250506-D00006.png",
            "full": "https://patentimages.storage.googleapis.com/54/51/99/d7989f1cf7ecf1/USD1074038-20250506-D00006.png"
          },
          {
            "thumbnail": "https://patentimages.storage.googleapis.com/19/6b/95/ca5e977f4c3605/USD1074038-20250506-D00007.png",
            "full": "https://patentimages.storage.googleapis.com/6a/ca/4a/e22f805009b834/USD1074038-20250506-D00007.png"
          },
          {
            "thumbnail": "https://patentimages.storage.googleapis.com/f1/0c/90/119d3b92c82b24/USD1074038-20250506-D00008.png",
            "full": "https://patentimages.storage.googleapis.com/01/1a/48/e33bb8b348f812/USD1074038-20250506-D00008.png"
          }
        ],
        "grantDate": "2025-05-06",
        "language": "en",
        "patentLink": "https://patents.google.com/patent/USD1074038S1/en",
        "title": "Table lamp",
        "pdf": "https://patentimages.storage.googleapis.com/67/b7/c4/26c3819bb6ee66/USD1074038S1.pdf",
        "patentId": "patent/USD1074038S1/en",
        "rank": 0,
        "priorityDate": "2024-11-20",
        "inventor": "Dan Zhang",
        "position": 1,
        "assignee": "Dan Zhang",
        "countryStatus": {
          "US": "ACTIVE"
        },
        "publicationDate": "2025-05-06",
        "serpapiLink": "https://serpapi.com/search.json?engine=google_patents_details&patent_id=patent%2FUSD1074038S1%2Fen",
        "publicationNumber": "USD1074038S1"
      }
    ],
    "serpapiPagination": {},
    "searchParameters": {
      "q": "USD1074038S1",
      "country": "US",
      "engine": "google_patents",
      "num": "10",
      "patents": true,
      "page": "1",
      "scholar": false
    },
    "searchInformation": {
      "page_number": 1,
      "total_pages": 1,
      "total_results": 1
    }
  }
}