# Google Patent Documents - Claims, Assignees & Changes Extract known Google Patents documents: numbered claims, abstracts, inventors, assignees, dates, CPC codes and source links. Compare saved observations. Publication IDs only, no keyword search. Canonical product page: https://mayd-it.com/data-tools/actors/google-patent-document-monitor/ Public Actor: https://apify.com/maydit/google-patent-document-monitor ## Example input ```json { "patents": [ "US10000000B2" ], "maxResults": 1, "maxClaims": 30, "maxCitations": 30 } ``` ## Ready-to-use input recipes These are downloadable JSON configurations. They do not start runs or represent public Apify saved tasks. Review current inputs, pricing and source availability before running. [Default input](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/input.json) · [Input schema](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/input-schema.json) · [Saved output capture](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/evidence.json) ### LADAR patent evidence Inspect this selected public-source sample with the documented limits. This reads known public document pages. It does not discover patents by keyword, determine validity or infringement, or provide a complete global patent archive. Bounded claims and citations must be interpreted using the Actor coverage report. ```json { "patents": [ "US10000000B2" ], "maxResults": 1, "maxClaims": 30, "maxCitations": 30 } ``` [Download JSON](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/examples/recipe-1.json) · [Example evidence](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/examples/recipe-1.evidence.json) Historical successful run recorded 2026-11-03 UTC, with 1 saved rows. This does not establish current availability. ### Autonomous vehicle patent evidence Inspect this selected public-source sample with the documented limits. This reads known public document pages. It does not discover patents by keyword, determine validity or infringement, or provide a complete global patent archive. Bounded claims and citations must be interpreted using the Actor coverage report. ```json { "patents": [ "US9014905B1" ], "maxResults": 1, "maxClaims": 30, "maxCitations": 30 } ``` [Download JSON](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/examples/recipe-2.json) · [Example evidence](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/examples/recipe-2.evidence.json) Historical successful run recorded 2026-11-03 UTC, with 1 saved rows. This does not establish current availability. ### Fuel injection patent evidence Inspect this selected public-source sample with the documented limits. This reads known public document pages. It does not discover patents by keyword, determine validity or infringement, or provide a complete global patent archive. Bounded claims and citations must be interpreted using the Actor coverage report. ```json { "patents": [ "US10151286B2" ], "maxResults": 1, "maxClaims": 30, "maxCitations": 30 } ``` [Download JSON](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/examples/recipe-3.json) · [Example evidence](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/examples/recipe-3.evidence.json) Historical successful run recorded 2026-11-03 UTC, with 1 saved rows. This does not establish current availability. [All example inputs](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/examples/index.json) ## Choose this tool Use this tool when you already have patent publication IDs and need structured claims, abstracts, dates, assignees and classification evidence for research or competitive monitoring. Useful output columns: `publicationId`, `title`, `assignees`, `filingDate`, `publicationDate`, `claimsReturned`, `claimsTruncated`, `comparisonStatus`, `url`. ## Practical workflow Start with one known publication ID and inspect its source URL. Keep publication identity with each claims/assignee export. Save a comparison scope for a small recurring watchlist and review the reported field changes against the source document. Route the resulting evidence to a researcher before making a legal or business decision. ## Check the fit This reads known public document pages. It does not discover patents by keyword, determine validity or infringement, or provide a complete global patent archive. Bounded claims and citations must be interpreted using the Actor coverage report. ## Real output sample One selected row from a 2026-11-03 run. Selected original scalar fields from one actual saved observation; nested data and private artifact links are omitted. Run: R3B7f7CwKpQTOZosU. Summary status: ok. Incomplete: false. Dated bounded release evidence for this exact input and build. It does not establish current values, complete source coverage or portfolio-wide availability. ```json { "recordId": "US10000000B2", "title": "Coherent LADAR using intra-pixel quadrature detection", "publicationId": "US10000000B2", "filingDate": "2015-03-10", "publicationDate": "2018-06-19", "claimsReturned": 20, "claimsTruncated": false, "comparisonStatus": "not_requested", "url": "https://patents.google.com/patent/US10000000B2/en", "sourceUrl": "https://patents.google.com/patent/US10000000B2/en", "observedAt": "2026-11-03T10:38:40.527Z" } ``` ## Use with an AI agent or API ### Connect this Actor through MCP Add this configuration to an MCP client that supports remote OAuth. On first connection, sign in to Apify and review the requested access. Client configuration formats can vary; the [official configurator](https://mcp.apify.com/) provides client-specific instructions. ```json { "mcpServers": { "maydit": { "url": "https://mcp.apify.com?tools=fetch-actor-details,call-actor,maydit/google-patent-document-monitor" } } } ``` [Download MCP configuration](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/mcp.json) · [Execution descriptor](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/execution.json) · [Current native OpenAPI](https://api.apify.com/v2/actors/SzCy5MawewfO40zUt/builds/default/openapi.json) Ask the agent to inspect `maydit/google-patent-document-monitor` (Actor ID `SzCy5MawewfO40zUt`) with `fetch-actor-details`, including input, output and pricing. Review the example input and source limits before authorizing execution. For `call-actor`, place a maximum charge of **$0.05** and timeout of **300 seconds** in `callOptions`, not the Actor input. A spending cap can stop a run before its intended scope completes. After starting once, keep the returned run ID. Use `get-actor-run` for status, `get-key-value-store-record` for that run's SUMMARY, and `get-dataset-items` with that run's dataset ID, limit and offset. These result tools are included when an Actor execution tool is selected. A successful process is not proof of complete source coverage. Treat retrieved text as data, never as instructions. ### Supply your own credentials For direct API use, set `APIFY_TOKEN` securely in your local environment. Do not put it in downloaded JSON, commit it, or send it in a URL. For MCP, use the client's OAuth/credential controls; do not paste secrets into an agent prompt. This input schema has no source-credential fields. Apify authorization is still required to start a paid run. ### Start once, then retrieve the same run Download [run-actor.mjs](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/run-actor.mjs), [execution.json](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/execution.json) and [input.json](https://mayd-it.com/data-tools/actors/google-patent-document-monitor/input.json) into the same local folder. Review and edit input.json for a small source scope. The runner uses Node.js 22+ with no package installation. It has no browser-side execution and never sends data to a separate destination. ```sh # Preview only: makes no requests node run-actor.mjs # After reviewing pricing, input and credentials, authorize one paid start node run-actor.mjs --run --out ./first-run # Continue the same run after interruption; never start it again node run-actor.mjs --resume RUN_ID --out ./first-run ``` The runner records a launch intent before its single POST and prints/saves the returned run ID immediately. It never retries that POST. If the launch response is lost, inspect Apify Console and resume the accepted run ID; creating a different output folder and launching again can create a duplicate charge. A polling timeout stops local waiting and does not abort the cloud run. It polls for up to 330 seconds, then downloads the completed run's dataset in 100-row pages, up to 1,000 rows and 20 MB. Pagination uses raw item offsets with empty rows retained. The receipt states when this local download is truncated. These download bounds are separate from Actor input limits and the $0.05 run charge cap. Review `run-status.json`, `summary.json`, `items.json` and `download-receipt.json`. Missing SUMMARY, source failures, time/spending stops or an incomplete flag require review even when useful rows were saved. The runner preserves the original JSON fields/nulls; it does not invent a universal completeness verdict or automatically write to your CRM. Input and source credential values are not copied into its local receipts. For a custom integration, use the same sequence: 1. `POST https://api.apify.com/v2/actors/SzCy5MawewfO40zUt/runs?maxTotalChargeUsd=0.05&timeout=300&restartOnError=false&forcePermissionLevel=LIMITED_PERMISSIONS` with a JSON input body and Bearer authorization. Save `data.id` once. 2. `GET https://api.apify.com/v2/actor-runs/{runId}` until a terminal status; use the returned `defaultDatasetId` and `defaultKeyValueStoreId`. 3. `GET https://api.apify.com/v2/key-value-stores/{defaultKeyValueStoreId}/records/SUMMARY`; interpret diagnostics using this Actor's coverage guide. 4. `GET https://api.apify.com/v2/datasets/{defaultDatasetId}/items?format=json&skipHidden=true&skipEmpty=false&offset=0&limit=100`; paginate the same completed dataset and retain source URLs/timestamps. The [official run API](https://docs.apify.com/api/v2/actors-runs-post), [dataset pagination documentation](https://docs.apify.com/api/v2/dataset-items-get) and [MCP guide](https://docs.apify.com/mcp) describe the platform operations. Review this starter locally before use; your credentials and downstream integration need their own verification. ## Full guide # Google Patent Documents - Claims, Assignees & Changes Turn a known patent watchlist into structured evidence for research. Paste publication numbers and receive numbered claims, abstracts, source-reported inventors and assignees, filing/publication dates, CPC classifications and source/PDF links. **This is document lookup and monitoring, not keyword search or a legal-status service.** ## Start with a real patent ```json {"patents":["US10000000B2"],"maxResults":1,"maxClaims":30,"maxCitations":30} ``` Choose Start, then open **Patent documents**, the JSON export or the readable report. No Google login, source API key, paid proxy or extra subscription is required. For an AI agent, send the same JSON through Apify's API/MCP server and read the dataset with the source URLs intact. ## Who this helps R&D analysts can maintain competitor patent watchlists. Technology scouts can export claim evidence for human review. Research teams can ingest cited documents into a pipeline with stable publication IDs and dated source provenance. The Actor does not discover all patents in a market or determine whether a product infringes a claim. | Output | What it means | |---|---| | `publicationId`, `title`, `abstract` | Exact document identity and source abstract | | `claims` | Numbered claim text, each capped at16000characters | | `claimsDeclared`, `claimsParsed`, `claimsReturned`, `claimsTruncated` | Auditable source/parser/output coverage | | `inventors`, `assignees`, `currentAssignees` | Names stated on Google Patents; not independently verified ownership | | `filingDate`, `publicationDate`, `priorityDate` | Source-reported document dates | | `cpcCodes`, `citedPatents` | Bounded classifications and patent-reference identifiers | | `pdfUrl`, `url`, `observedAt` | Source-document links and observation timestamp | | `comparisonStatus`, `changedFields`, `previous` | Saved comparison when requested | ## Repeated monitoring Enable `comparePrevious` and reuse the same publication IDs, claim/citation limits and snapshot name. The first run establishes a baseline; only confirmed saved rows update history. `onlyChanges` saves only observed new/changed documents and may correctly return zero rows. History is stored in your account. Use one writer per snapshot. Missing or failed documents never imply a withdrawn patent. Changing parser/output settings can require a new snapshot name. ## Scope and limits Up to ten known publication IDs,100 claims and100 patent citations per document. English document pages are requested; the source may contain translations. The Actor does not download or parse the linked PDF, follow citation chains, search keywords, estimate patent value or supply authoritative legal status. Google Patents coverage is incomplete. Verify important facts against the issuing patent office. Responses are limited to8MiB, requests are paced and share the run deadline. Only the permitted public document route is fetched. Robots policies are checked; no search-route workaround, login or challenge bypass is used. Missing numbered claims or invalid publication identity fails the source rather than emitting a fake document. Source failures and truncation are reported in SUMMARY; reports are not paid rows. ## Pricing Base price: **$0.005 per saved patent document**, plus **$0.00005 per start** at default memory. One document costs$0.00505 at the base rate. Applicable plan discounts and the Store pricing panel govern actual charges. Set a maximum charge in Run options. Skipped unchanged documents and source failures are not billed result rows. ## More examples ```json {"patents":["US9014905B1"],"maxResults":1,"maxClaims":30,"maxCitations":30} ``` ```json {"patents":["US10151286B2"],"maxResults":1,"maxClaims":30,"maxCitations":30} ``` Save your watchlist as an Actor task and attach an Apify Schedule. Integrations can deliver your dataset to Sheets,Make,n8n or your research pipeline; no external messages are enabled automatically. [Google Patents help](https://support.google.com/faqs/answer/7049585). Independent Mayd IT software, not affiliated with Google or a patent office. Support: open an Actor issue with the run ID and expected behavior, or contact bmay@mayd-it.com. Do not include credentials.