Prior-art and freedom-to-operate research
Use Google Patents endpoints to turn prior-art and freedom-to-operate research into repeatable API requests with documented inputs and JSON responses.
Turn Google Patents' public search and detail pages into structured IP data — full-text search by keyword, inventor, assignee, and other filters with top-assignee/inventor/classification breakdowns; a single patent's complete bibliographic detail, abstract, claims, description, citations, and family members; CPC classification lookup; recently indexed publications by ISO week; inventor/assignee autocomplete; and per-country per-year index coverage, all as normalized JSON. Credential-free.
Search Google Patents and get bibliographic detail, claims, citations, family members, autocomplete, and index coverage as structured JSON.
Endpoint families
6
Documented params
25
Examples
6
Live catalog snapshot
Active endpoints
6
Methods
GET
Required params
12
Schema refs
6
{
"platform": "Google Patents",
"endpoint": "googlepatents-search",
"method": "GET",
"path": "/googlepatents/search",
"auth": "apiKey"
}Use cases
Search Google Patents and get bibliographic detail, claims, citations, family members, autocomplete, and index coverage as structured JSON.
Use Google Patents endpoints to turn prior-art and freedom-to-operate research into repeatable API requests with documented inputs and JSON responses.
Use Google Patents endpoints to turn competitive ip and r&d landscape tracking into repeatable API requests with documented inputs and JSON responses.
Use Google Patents endpoints to turn patent portfolio and citation analysis into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Google Patents endpoint catalog — 6 endpoints, 25 documented request parameters, and 6 published response schemas — the same catalog Docs and Playground run against.
6 documented Google Patents endpoints, grouped into 6 request families — Classification, Coverage and Detail, plus 3 more.
25 request parameters are documented across those Google Patents endpoints, 12 of them required — the full input contract is public before you write any integration code.
6 of the 6 Google Patents endpoints ship a recorded example response, and 6 carry a documented response schema — you can code against the real JSON before the first request.
Google Patents endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
6 hosted MCP tools back the Google Patents endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/googlepatents/classification
/googlepatents/coverage
/googlepatents/detail
/googlepatents/recent
/googlepatents/search
/googlepatents/suggest
Endpoint catalog
/googlepatents/searchSearches Google Patents' full index by free-text query, with optional inventor, assignee, patent office, status, type, language, and date filters. Returns a page of normalized hits plus top-assignee/top-inventor/top-classification breakdowns over the full result set. Public data, sourced from Google Patents' own search API.
MCP tool googlepatents_search
/googlepatents/detailReturns a single patent's normalized detail: title, abstract, inventors, assignees, dates, legal status, CPC/IPC classifications, claims, description, patent citations, cited-by patents, family members, and similar documents. `number` is a publication number such as `US10758101B2`, `EP1000000A1`, or `WO2020123456A1`. Public data, sourced from Google Patents' server-rendered detail pages. To search or browse by keyword, inventor, or assignee instead of a known publication number, use `/googlepatents/search`.
MCP tool googlepatents_detail
/googlepatents/classificationReturns a CPC classification symbol's official title, its position in the classification tree (parent/child symbols), related symbols, and its full scope-note description. Accepts a symbol at any level, e.g. a section ("A"), a class ("A61"), a subclass ("A61K"), or a full group/subgroup ("A61K31/00"). Public data, sourced from Google Patents' own search API.
MCP tool googlepatents_classification
/googlepatents/recentReturns the patent publications Google Patents' bulk sitemap indexes for one ISO 8601 week (format YYYY-Www, e.g. "2026-W20"): publication number, title, and detail-page URL for each. Useful for browsing recently published patents without a search query. Public data, sourced from Google Patents' own sitemap.
MCP tool googlepatents_recent
/googlepatents/suggestReturns Google Patents' own autocomplete suggestions for an inventor or assignee name as the user types, the same suggestions shown by the Inventor/Assignee fields on Google Patents' advanced search page. Public data, sourced from Google Patents' own search API.
MCP tool googlepatents_suggest
/googlepatents/coverageReturns how many patent grants and applications Google Patents has indexed, per patent office/country, per year, across every authority it covers. Public data, sourced from Google Patents' own search API.
MCP tool googlepatents_coverage
Related APIs
Business & Market Intelligence
Turn public GitHub ecosystem signals into structured data for developer-market research, open-source intelligence, recruiting, and AI-agent workflows.
Business & Market Intelligence
Collect public TrustMRR startup marketplace and leaderboard data as normalized JSON for startup research, SaaS discovery, and market intelligence workflows.
Business & Market Intelligence
Add website and competitive intelligence signals from SimilarWeb to research pipelines.
How to scrape Google Patents
Crawlora's Google Patents endpoints return search, patent detail, classification lookup, recent publications, autocomplete, and index coverage as normalized JSON with one API key — no Google account required.
Send a free-text query to /googlepatents/search, with optional inventor, assignee, patent office, status, type, language, and date filters, for normalized hits plus top-assignee/inventor/classification breakdowns.
Pass a publication number (e.g. US10758101B2) to /googlepatents/detail for that patent's full bibliographic data, abstract, claims, description, citations, cited-by patents, and family members.
Pass a symbol at any level (a section like A, a class like A61, or a full group like A61K31/00) to /googlepatents/classification for its official title, position in the classification tree, related symbols, and scope note.
Pass an ISO 8601 week (e.g. 2026-W20) to /googlepatents/recent for every publication Google Patents' bulk sitemap indexed that week — publication number, title, and detail-page URL — without a search query.
Send a partial inventor or assignee name to /googlepatents/suggest for the same autocomplete suggestions shown on Google Patents' advanced search page.
Call /googlepatents/coverage for how many grants and applications Google Patents has indexed, per patent office/country, per year.
FAQ
Send a free-text query to Crawlora's /googlepatents/search endpoint, with optional inventor, assignee, office, status, type, language, and date filters, and get normalized results as structured JSON.
No Google account or login is required from the caller — only your Crawlora API key.
Yes — /googlepatents/detail returns a patent's claims, description, patent citations, cited-by patents, and family members alongside its bibliographic data, given a publication number like US10758101B2.
Pass an ISO 8601 week like 2026-W20 to /googlepatents/recent for every publication Google Patents' bulk sitemap indexed that week — publication number, title, and detail-page URL.
Send a partial name to /googlepatents/suggest and get Google Patents' own autocomplete suggestions — the same ones shown on its advanced search page's Inventor/Assignee fields.