No API key is required for the PatentsView API — send POST requests to https://search.patentsview.org/api/v1/patent/ with a JSON body containing a q (query) object, an f (fields) array specifying which fields to return, and optional s (sort) and o (options) objects
Construct the query using PatentsView's query DSL: combine _and, _or, and field-specific predicates such as {"patent_title": {"contains": "solar cell"}} or {"cpc_group_id": {"equals": "H01L31"}}
Request fields including patent_id, patent_date, patent_title, patent_abstract, inventor details, assignee_organization, and claims to get the full document context
Paginate results using the per_page and page parameters in the o object; PatentsView returns granted patents only — published applications are not included
To retrieve full claim text, include the claims field in your fields array; the response nests each claim as a separate object with claim_sequence and claim_text
For bulk analysis, PatentsView also provides downloadable bulk data files at patentsview.org/download — prefer bulk downloads for full-corpus processing over repeated API calls
Known gotchas
PatentsView covers granted US patents only; published patent applications (pre-grant publications, US PGPUB) are not in this dataset — use the USPTO ODP for application-level data
The PatentsView dataset is updated weekly, not daily or in real time; very recently issued patents may not appear until the next weekly update cycle
CPC codes in PatentsView reflect the classification at time of data ingestion; reclassified patents may have stale CPC assignments — cross-reference with USPTO ODP for authoritative current classification
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp