Google Research Tools: search API

Use Google Research Tools: search API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent 16 credits / call

Try online

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

Google Research Tools

What this API does

Use Google Research Tools: search API through Nexscope with documented parameters, structured results and API key authentication. The request accepts q, num, page, country, language. Its documented result includes errcode, errmsg, organicResults, searchParameters, searchInformation, searchMetadata, serpapiPagination, summary.

Google Research Tools: search API API use cases

Investigate a product IP question

To investigate a product ip question, a compliance analyst submits q and num to Google Research Tools: search API. The returned errcode, errmsg, organicResults help identify records relevant to the proposed product.

Collect records for an IP review

A compliance analyst uses Google Research Tools: search API 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 Research Tools: search API with q and num to document evidence for specialist assessment. The result helps document the records supporting an IP research question.

Google Research Tools: search API API FAQ

What does the Google Research Tools: search API API return?

Use Google Research Tools: search API through Nexscope with documented parameters, structured results and API key authentication. 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 Research Tools: search API 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 Research Tools: search API 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_data_patents_search. The same documented request parameters apply; use Online test to review a 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_data_patents_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"
}'

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	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

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.

Code example

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

Response example

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

{
  "code": 0,
  "cost": "-1",
  "data": {},
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

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	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

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_data_patents_search",
    "arguments": {
      "num": 10,
      "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

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

At least 10 credits / callAPI usage records

Try it

Send a real request with the same contract shown in the reference.

Endpoint

/patents/search

MCP method

nexscope_data_patents_search

API key*

JSON payload*

cURL

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

Response

No response yet. Run the request to see the response here.

Use Google Research Tools: google Search API through Nexscope with documented parameters, structured results and API key authentication.

Google Research Tools: get Trend By Keys API

Use Google Research Tools: get Trend By Keys API through Nexscope with documented parameters, structured results and API key authentication.

Google Research Tools: get Trend By Time API

Use Google Research Tools: get Trend By Time API through Nexscope with documented parameters, structured results and API key authentication.

What this API does

Google Research Tools: search API API use cases

Investigate a product IP question

Collect records for an IP review

Document evidence for specialist assessment

Google Research Tools: search API API FAQ

What does the Google Research Tools: search API API return?

How many credits does the Google Research Tools: search API API cost?

How do I call the Google Research Tools: search API API from my app or an MCP client?

Authentication

Run an API

Example request

Check the response

HTTP status codes

Run this API

Endpoint

Request parameters

Code example

Response example

Response fields

Responses

Data source, freshness, and limitations

MCP

Call a tool

Legacy MCP v1

Online test

Try it

Related APIs