Prior-art and freedom-to-operate research
Usa los endpoints de USPTO PPUBS para convertir prior-art and freedom-to-operate research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Turn USPTO Patent Public Search's full-text index into structured JSON — granted patents and published applications by keyword, with normalized bibliographic results: title, applicant/assignee, inventors, filing and publication dates, application number, IPC/CPC classifications. A result's guid and database feed directly into the detail endpoint for that document's full abstract, description, and claims text. Credential-free.
Search USPTO's own full-text patent index and get normalized bibliographic results plus full patent detail as structured JSON.
Familias de endpoints
2
Parámetros documentados
8
Ejemplos
2
Snapshot en vivo del catálogo
Endpoints activos
2
Métodos
GET
Parámetros obligatorios
5
Referencias de esquema
2
{
"platform": "USPTO PPUBS",
"endpoint": "usptoppubs-search",
"method": "GET",
"path": "/usptoppubs/search",
"auth": "apiKey"
}Casos de uso
Search USPTO's own full-text patent index and get normalized bibliographic results plus full patent detail as structured JSON.
Usa los endpoints de USPTO PPUBS para convertir prior-art and freedom-to-operate research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de USPTO PPUBS para convertir us patent filing and applicant tracking en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de USPTO PPUBS para convertir ip landscape and competitive research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de USPTO PPUBS — 2 endpoints, 8 parámetros de solicitud documentados y 2 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
2 documented USPTO PPUBS endpoints, grouped into 2 request families — Detail and Search.
8 request parameters are documented across those USPTO PPUBS endpoints, 5 of them required — the full input contract is public before you write any integration code.
2 of the 2 USPTO PPUBS endpoints ship a recorded example response, and 2 carry a documented response schema — you can code against the real JSON before the first request.
USPTO PPUBS 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.
2 hosted MCP tools back the USPTO PPUBS endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Mapa de cobertura
Estas tarjetas se generan a partir del catálogo de endpoints activo, así que la landing page refleja la misma superficie de API que usan Docs y Playground.
/usptoppubs/detail
/usptoppubs/search
Catálogo de endpoints
/usptoppubs/searchSearches USPTO Patent Public Search's full-text index of granted patents and published applications, returning normalized bibliographic results (title, applicant/assignee, inventors, filing and publication dates, application number, IPC/CPC classifications, page count). q accepts USPTO's full Advanced Search query syntax -- field-specific search (e.g. battery.ti., Microsoft.as.), date ranges (@pd>=20200101<=20241231), boolean and proximity operators, and wildcards -- see the markdown doc for the full field-code table and syntax reference. Public data, sourced from USPTO's own official search tool.
Herramienta MCP usptoppubs_search
/usptoppubs/detailFetches a single USPTO Patent Public Search record's full text -- bibliographic data, abstract, description, and claims -- by GUID and source database. guid and source normally come straight from a prior /usptoppubs/search result's guid and database fields. Public data, sourced from USPTO's own official search tool.
Herramienta MCP usptoppubs_detail
APIs relacionadas
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.
Cómo hacer scraping de USPTO PPUBS
Crawlora's /usptoppubs/search and /usptoppubs/detail endpoints return USPTO's own full-text patent search results and per-document detail as normalized JSON with one API key — no USPTO account required.
Send a free-text query to /usptoppubs/search for normalized bibliographic results — title, applicant/assignee, inventors, filing and publication dates, application number, IPC/CPC classifications. Accepts USPTO's full BRS query syntax (field codes, date ranges, boolean and proximity operators).
Use the response's page count to page through a query's full result set.
Pass a result's guid and database (source) to /usptoppubs/detail for that document's full abstract, description, and claims text.
Preguntas frecuentes
Send a free-text query to Crawlora's /usptoppubs/search endpoint and get normalized bibliographic results — title, applicant/assignee, inventors, dates, classifications — as structured JSON, sourced from USPTO's own official search tool.
No USPTO account or login is required from the caller — only your Crawlora API key.
Yes — pass a search result's guid and database to /usptoppubs/detail for that document's full abstract, description, and claims text alongside its bibliographic data.
This endpoint searches USPTO's own full-text index directly — US patents only. Crawlora's separate Google Patents API (/googlepatents/*) covers Google Patents' broader multi-country index plus per-patent citations and family data.