AI for IP · 2026

Patent offices now run AI in examination, the useful unit of AI has moved from chat to agents, and MCP has become the way agents reach real data. Three reasons the IP stack has to change shape this year.

The question for IP teams in 2026 is no longer whether to use AI. It is whether the AI you have is shaped like the work you do, and three things that happened over the last eighteen months make the honest answer uncomfortable for most teams.

Patent offices moved first. The USPTO now requires examiners to run an AI similarity search on plant and utility applications, WIPO added an AI assistant to PATENTSCOPE in July 2026, and the EPO ships an AI classification tool inside Espacenet.1, 2, 3 At the same time the useful unit of AI stopped being a chat window and became an agent that runs a whole workflow, and MCP emerged as the standard way those agents reach real systems. Patsnap Eureka is built for that shape: agents that take a technical disclosure rather than a query, retrieve across 200M+ patents in 174 jurisdictions using semantic, Boolean, classification and citation-tracking routes together, and return feature-level mappings you can audit, with the same agents exposed as MCP servers so they can be called from whatever client your team already uses.4, 5

What follows is the case for why a patent stack has to be different from a general AI stack, and why the agent and MCP shift is the part worth acting on this year rather than next. Everything is sourced to patent office documents, published research and vendor documentation, accessed in August 2026.

In short
  • The asymmetry is now real. Examiners search your application with a citation-trained AI system. The free public tool states that it does not use semantic searching at all.
  • Generic AI does not transfer. Purpose-built legal research AI still hallucinates 17% to 33% of the time on a corpus far friendlier than patents, and cross-domain patent retrieval measures roughly five times worse than same-domain.
  • Chat is the wrong unit. Patent work is decided feature by feature, so the deliverable is a mapping, not an answer, and that requires an agent workflow rather than a prompt.
  • MCP is the 2026 integration layer. It lets patent search be called as a tool from the clients your team already runs, instead of being another tab.

What actually changed, and why it lands in 2026

Three separate shifts converged, and each one is documented rather than anecdotal.

The offices adopted AI in the examination process itself. The USPTO runs an AI-based Similarity Search inside PE2E Search that “uses trained AI models to output a list of domestic and foreign patent documents that are similar to the patent application being searched,” trained on “the disclosure text, patent classifications, document citations, and human-rated similarity.”1 An October 2025 memorandum made its use mandatory for examiners on plant and utility applications.6 WIPO followed on 2 July 2026, announcing that “an AI assistant is now available to help users build effective PATENTSCOPE search queries.”2 The EPO added a CPC text categoriser to Espacenet that it describes as “driven by artificial intelligence.”3

The unit of AI changed. A chat window answers a question. An agent runs a sequence: read the disclosure, extract the distinguishing features, derive search elements, run several retrieval routes, screen the results, produce a structured deliverable. For patent work that is not a nicety, because the legal question is decided element by element and a paragraph of prose does not answer it.

Integration stopped being bespoke. MCP is described by its maintainers as “an open-source standard for connecting AI applications to external systems,” and as “a USB-C port for AI applications,” with support across Claude, ChatGPT, Visual Studio Code and Cursor among others.7 The practical consequence for an IP function is that patent search no longer has to be a destination your team visits. It can be a tool your team’s existing assistant calls.

Why the timing matters
Each of these on its own is interesting. Together they move the bar: the counterparty in examination is AI-assisted, the technology to match that is generally available, and the integration cost of adopting it has collapsed. A stack designed before all three is now the wrong shape.

The asymmetry nobody planned for

Put two published facts side by side.

The first: examiners at the USPTO are required to run a citation-trained AI similarity search against your application, in an internal system.1, 6

The second: the free public search tool, Patent Public Search, states in its own FAQ that “unlike third party proprietary patent search databases, Patent Public Search does not use semantic searching,” and that “at this time, Patent Public Search does not have access to foreign patent databases.”8

An applicant relying on the free tool is searching with keywords, in one jurisdiction, against an examiner searching with AI trained on what examiners actually cite, across domestic and foreign collections. That gap is not a marketing argument, it is arithmetic, and it is the clearest single reason to look at your own retrieval capability this year rather than next.

AI for IP · Eureka

Search the way the examination process now works

Paste a technical disclosure. Eureka extracts the distinguishing features, runs semantic, Boolean, classification and citation-tracking routes together, screens the results and maps each feature to the passage that discloses it.

Try Eureka free

10,000 free credits to get started

Why a general AI stack does not transfer to patents

The temptation is to point whatever AI the business already licensed at the patent problem. The corpus is what defeats that, in four specific ways.

Scale and growth. WIPO counted an estimated 3.7 million patent applications filed worldwide in 2024, up 4.9%, with an estimated 19.7 million patents in force.9 PATENTSCOPE alone indexes 128.8 million patent documents across 123 national and regional collections.10

Most of it is not full text. This is the property that surprises people. The EPO’s DOCDB, the worldwide backbone behind much of the tooling, holds “bibliographic data, abstracts, citations and the DOCDB simple patent family, but no full text or images.”11 The EPO’s national full-text extracts “cover France, Spain, Switzerland and the United Kingdom.”12 Google Patents indexes over 120 million publications from 100+ offices, with full text for 22 of them.13 A system searching abstracts is not doing the same job as one searching claims.

It is multilingual by default. WIPO offers cross-lingual expansion across 14 languages precisely because the same technical concept carries different names across languages, and a monolingual search misses it silently.14

It is written to resist search. Claim language is drafted broadly, which in practice means abstractly. A heat sink becomes a thermally conductive member.

The measured consequences are consistent. A 2025 family-level benchmark of cross-domain prior art retrieval, running 249 controlled experiments across BM25, dense retrieval and rank fusion, found that “OUT-domain performance remains roughly five times lower than IN-domain across all configurations,” and answered “none” when asked which method closes the gap.15 A multi-task evaluation of 22 embedding models over 46,069 citation-graph queries reported a best result of roughly nDCG@10 = 0.197.16 Cross-field retrieval is exactly where prior art hides, and it is where general-purpose embeddings are weakest.

For context on how far domain fit carries: Stanford researchers measured general-purpose LLMs hallucinating between 58% and 88% on verifiable questions about real court cases, and purpose-built commercial legal research tools with retrieval augmentation still hallucinating between 17% and 33%, on a corpus that is public, English-language and full text.17, 18 Those studies measure legal research rather than patent search, but they establish the shape of the problem: retrieval augmentation helps a lot and domain fit still decides the outcome.

From chat to agents: why the output shape has to change

Ask a chat interface whether an invention is novel and you get a paragraph. That is the wrong artefact, and no amount of model improvement fixes it.

Novelty is assessed one reference at a time, feature by feature: does this single document disclose every element of the claim? Inventive step is a separate analysis under a named jurisdictional test. Freedom to operate asks the mirror question against live claims. In every case the working document is a mapping between claim elements and specific passages. A ranked list of relevant documents has done part of the job and left the expensive part on your desk.

This is what an agent changes. Eureka’s novelty agent extracts the technical features from the disclosure, builds several search strategies in parallel, screens the results and returns a feature-by-feature comparison table with references tagged for their citation role and each mapping linked to the passage it came from, with every step visible and editable before it runs.4 The FTO agent runs from feature extraction through screening to claim charting, and a design agent converts product photographs into patent-standard line drawings for visual comparison. On the drafting side, the agents work to CNIPA, USPTO and EPO standards with jurisdiction-specific rule libraries and a compliance review as a required final step.19

The test to apply to any tool is simple: ask to see the output, not the interface. If what comes back is prose with citations, it is a research assistant. If it is a feature mapping you can hand to an attorney, it is built for patent work.

Why MCP is the part to act on this year

Every previous wave of IP software asked your team to go somewhere. MCP inverts that, and it is the reason the 2026 stack looks different from the 2024 one.

MCP is “an open-source standard for connecting AI applications to external systems,” and its own documentation offers the useful analogy: “Just as USB-C provides a standardized way to connect electronic devices, MCP provides a standardized way to connect AI applications to external systems.” It is supported across Claude, ChatGPT, Visual Studio Code, Cursor and others, so a server built once is reachable from all of them.7

For an IP function this changes three things at once. Patent search becomes callable from wherever the work already happens rather than requiring a context switch. The engineering cost of connecting patent data to an internal assistant collapses from an integration project to an API key. And the analysis stops being trapped in one vendor’s interface, because the outputs arrive in whatever workflow you built around them.

The Patsnap Open Platform publishes 31 MCP servers described as connecting “Patsnap’s domain-specific AI agents to LLM platforms such as Claude or custom models using the Model Context Protocol,” covering patent research including novelty and both invention and design freedom to operate, a cross-domain TRIZ case library, a workspace reader and 3GPP TDoc tools. Setup is an API key plus a generated connection link, and the Starter tier is free with 10,000 credits valid for 90 days.5, 20 Elsewhere in the market the pattern is appearing too: at least one drafting vendor publishes a REST API for the same reason.21

The practical read
If your 2026 plan has a line for an internal AI assistant, the patent question is not which portal to buy. It is which patent capabilities that assistant should be able to call, and whether your provider exposes them as tools rather than only as screens.

Patent work has an answer key, so ask for the measurement

This is the most underused advantage in the field. Most AI claims are hard to test because there is no objective right answer. Patent search is different: when an examiner cites a reference as an X document, a trained professional has recorded a judgment that this document defeats novelty. Those citations exist in the millions, across offices, and they work as labels.

That makes patent AI measurable. Patsnap publishes a benchmark methodology, PatentBench, in which ground truth is taken from X references cited by examiners at different patent offices, deduplicated and normalised by patent family, over 340 cross-jurisdiction samples, with the novelty agent recording an 85% X Hit Rate and a 37% X Recall Rate in July 2026.22 The sample size, the ground-truth definition and the metric definitions are published alongside the result.

Whatever you are evaluating, ask for those three things. A percentage without a sample size, a ground-truth definition and a metric definition is not interpretable, and in a domain that has an answer key there is no excuse for not using it.

What the 2026 stack looks like

Four layers, in the order they constrain each other.

  • A licensed corpus with known coverage. Which offices, which years, full text or bibliographic, which languages, how current. Every accuracy claim above this layer depends on it.
  • Multi-route retrieval. Semantic, Boolean, classification and citation tracking running together, plus non-patent literature. Classification deserves particular attention: the International Patent Classification is a language-independent scheme covering every patent document in the world, which makes it the one retrieval route that survives the terminology problem.23
  • Agent workflows with feature-level output. Extraction of claim elements and mapping to passages, producing comparison tables and claim charts rather than prose. Plus the data that decides clearance questions: simple and INPADOC extended family views and legal event data.24
  • An interface layer that is callable, not just visitable. MCP servers or an API, so the capability reaches the assistant your team already uses.

The audit trail runs through all four and is a regulatory requirement rather than a preference. The USPTO’s guidance states that “simply relying on the accuracy of an AI tool is not a reasonable inquiry,” and under 37 CFR 11.18(b) the person who signs certifies that contentions have evidentiary support after a reasonable inquiry.25, 26 A system that cannot show its sources makes that certification impossible to give honestly.

What to do this quarter

  • Run one live comparison. Take five disclosures you already filed, where you know what the examiner cited, and put them through whatever AI you are considering. You have the answer key already.
  • Ask every vendor the coverage question in writing. Which offices, which of them in full text, which languages, and is retrieval cross-lingual. A document count is not an answer.
  • Ask to see a claim chart, not a demo. The output shape tells you more in thirty seconds than an hour of feature walkthrough.
  • Check whether the capability is callable. If you are standing up an internal assistant this year, ask for the MCP server or the API before you commit to the interface.
  • Get the data terms in writing. Zero retention, no training on your data, documented residency and published certifications. The USPTO warns that AI use for prior art searching may result in inadvertent disclosure of client-sensitive information and that AI systems may retain what users enter.25 The ABA requires informed client consent before inputting representation information into a generative AI tool.27
Patsnap Open Platform

Make patent search callable from your own agent

31 MCP servers covering patent research, novelty and freedom to operate, a cross-domain TRIZ case library, a workspace reader and 3GPP TDoc tools. An API key and a generated connection link is the whole setup.

Get an API key

Free Starter tier, 10,000 credits for 90 days

What does not change

  • No search proves a negative. Coverage differs by office, by year, by full-text depth and by language. WIPO publishes an office-by-office coverage table precisely because coverage is uneven. A search establishes what was found under a documented scope.
  • The certification stays with the person who signs. Agents make review faster by linking conclusions to passages. They do not move the duty of reasonable inquiry.
  • Novelty and inventive step remain separate analyses. Novelty is assessed one reference at a time; inventive step is a distinct test under a named jurisdictional framework. No output performs either for you.
  • Confidentiality follows the disclosure. WIPO warns that organisations using generative AI tools “may inadvertently give away trade secrets or waive confidentiality in commercially sensitive information.”28 The mitigation is contractual and technical, not procedural.

Frequently asked questions

Why do IP teams need a different AI stack from the rest of the business?
Because the corpus is different in four ways that break general-purpose retrieval. It is very large and growing, with an estimated 3.7 million applications filed in 2024 and 19.7 million patents in force, and PATENTSCOPE alone indexing 128.8 million documents. Most of it is not machine-readable full text: the worldwide bibliographic backbone carries abstracts and citations but no full text, and national full-text extracts cover only a handful of countries. It is multilingual by default, which is why WIPO provides cross-lingual expansion across 14 languages. And claim language is drafted abstractly, so the terminology in the decisive document rarely matches the terminology in your query.
Does the USPTO use AI to search my patent application?
Yes, and since October 2025 it is mandatory for examiners on plant and utility applications. The USPTO operates an AI-based Similarity Search inside PE2E Search, its internal examiner system, which uses trained AI models to output a list of domestic and foreign patent documents similar to the application being searched, with models trained on disclosure text, patent classifications, document citations and human-rated similarity. The free public tool, Patent Public Search, states in its own FAQ that it does not use semantic searching and has no access to foreign patent databases. That asymmetry is the practical reason applicants increasingly run their own AI-assisted search before filing.
What is MCP and why does it matter for IP teams in 2026?
MCP, the Model Context Protocol, is described by its maintainers as an open-source standard for connecting AI applications to external systems, and compared to a USB-C port for AI applications: build a server once and it is reachable from Claude, ChatGPT, Visual Studio Code, Cursor and other clients. For an IP function it matters because it turns patent search from a destination into a callable tool. The integration cost of connecting patent data to an internal assistant falls to an API key, the analysis stops being trapped in one vendor interface, and the capability reaches whatever workflow your team already uses. The Patsnap Open Platform publishes 31 MCP servers covering patent research, novelty and freedom to operate, with a free Starter tier of 10,000 credits for 90 days.
What is the difference between an AI patent agent and an AI chat assistant?
A chat assistant answers a question in prose. An agent runs the workflow and returns an artefact. For patent work that distinction is decisive, because novelty, inventive step and freedom to operate are all decided element by element, so the working document is a mapping between claim elements and specific passages rather than a paragraph. A patent agent reads the technical disclosure, extracts the distinguishing features, derives search elements, runs semantic, Boolean, classification and citation-tracking routes in parallel, screens the results and produces a feature-by-feature comparison table or a claim chart, with every step visible and editable. The quickest test of any tool is to ask for the output rather than the demo.
Can we just use ChatGPT or Claude for prior art search?
They are useful for reasoning over documents you supply, and they are not a substitute for patent retrieval, because the constraint is the corpus rather than the model. Most patent documents are not available as machine-readable full text, the decisive reference is often not in English, and cross-field retrieval measures roughly five times worse than same-field retrieval in a 2025 benchmark of prior art search. Stanford researchers measured general-purpose models hallucinating between 58% and 88% on verifiable questions about real court cases, and purpose-built legal research tools with retrieval augmentation still hallucinating between 17% and 33%. The productive pattern in 2026 is to keep the assistant and give it a patent-native tool to call, which is what MCP is for.
How do we evaluate an AI patent tool objectively?
Use examiner citations as the answer key, because patent search is one of the few AI applications that has one. When an examiner cites a document as an X reference, a trained professional has recorded a judgment that it defeats novelty, and those citations exist in the millions across offices. Take five or ten of your own filed applications where you already know what the examiner cited, and run them through the tool. Then ask any vendor for three things: the sample size, the ground-truth definition and the metric definition. Patsnap publishes a benchmark methodology, PatentBench, using examiner-cited X references deduplicated by family over 340 cross-jurisdiction samples, reporting an 85% X Hit Rate and a 37% X Recall Rate in July 2026.
Is it safe to put unfiled inventions into an AI tool?
It depends entirely on the contractual terms, and the test is the same whichever tool you use. The USPTO has warned that using AI systems for prior art searches or application drafting may result in inadvertent disclosure of client-sensitive or confidential information to third parties, and that AI systems may retain what users enter and use it to train models or provide it to third parties. ABA Formal Opinion 512 requires a client’s informed consent before inputting information relating to the representation into a generative AI tool. Look for written zero-retention terms, an explicit commitment not to train on customer data, documented data residency and published certifications such as SOC 2 Type II and ISO 27001.
Where should an IP team start if it is behind?
Start with a measured comparison rather than a procurement process. Take five disclosures you already filed where the examiner citations are known, run them through whatever you are considering, and compare against your own answer key. In parallel, ask every vendor the coverage question in writing, which offices and which of them in full text and in which languages, and ask to see a claim chart rather than a feature walkthrough. If you are standing up an internal AI assistant this year, ask for the MCP server or the API before committing to an interface, because that decision is harder to reverse than the choice of vendor.

Sources and verification

Disclosure & disclaimer

Who published this. This article is published by Patsnap, which develops and sells Patsnap Eureka and the Patsnap Open Platform, patent-specific AI products of the kind advocated above. It is an editorial overview written by a participant in this market. It is not an independent or third-party review, and it has not been commissioned, sponsored, reviewed or endorsed by any other company named here.

How the information was gathered. Agency guidance, coverage figures, research findings and protocol documentation are taken from the published pages, papers and regulatory documents cited, as accessed on August 14, 2026. They are not the result of hands-on testing or benchmarking by Patsnap. The hallucination figures cited come from published academic studies of legal research tools and general-purpose models; they were measured on legal research tasks, not on patent search, and are cited as context for domain fit rather than as measurements of any patent product. Coverage figures, guidance and product capabilities change frequently and may have changed since publication.

Scope and limitations. This article describes structural differences between general-purpose AI stacks and patent-specific systems; it does not evaluate or rank any individual product, and nothing here is intended to assert that any named or unnamed product is inferior to any other. Research results cited measure specific tasks on specific datasets and do not generalise to every system. Performance figures attributed to a product are that vendor’s own published results, obtained under that vendor’s own methodology, and have not been independently verified. No warranty is given as to the accuracy, completeness or currency of any information here.

Trademarks. All trademarks, service marks, product names and company names are the property of their respective owners and are used here solely for identification and descriptive purposes. Their use does not imply any affiliation with, sponsorship by, endorsement by or approval from their respective owners.

Not professional advice. This article is general information about software tools and patent workflows. It is not legal advice, it does not create an attorney-client or any other professional relationship, and it should not be relied on in place of advice from qualified patent counsel on your specific circumstances. Patentability, freedom to operate and infringement conclusions depend on claim construction, live legal status and the applicable jurisdiction, and remain professional judgments.

  1. USPTO, AI-based Similarity Search in PE2E Search (PDF): model description and training data.
  2. WIPO, PATENTSCOPE AI-Assisted Search Now Available, 2 July 2026.
  3. EPO, Espacenet release notes: CPC text categoriser described as driven by artificial intelligence, release 1.47.3, 28 July 2024.
  4. Patsnap Eureka, IP Search agents: Novelty, FTO and Design FTO agents; 200M+ patents across 174 jurisdictions; SOC 2, ISO 27001, GDPR and CCPA; no AI training on user data.
  5. Patsnap Open Platform, MCP Servers marketplace: 31 servers and client setup instructions.
  6. USPTO Official Gazette notice, AI Similarity Search in PE2E, 30 December 2025: mandatory use on plant and utility applications.
  7. Model Context Protocol, introduction: open-source standard, the USB-C analogy, and supported clients.
  8. USPTO, Patent Public Search FAQs: no semantic searching, no access to foreign patent databases.
  9. WIPO, World Intellectual Property Indicators 2025, patents highlights: 2024 filings, grants and patents in force.
  10. WIPO PATENTSCOPE, search home and data coverage: 128.8 million documents across 123 collections.
  11. EPO, DOCDB bulk data: worldwide bibliographic data, abstracts, citations and simple families, no full text or images.
  12. EPO, National full-text data: character-coded extracts for France, Spain, Switzerland and the United Kingdom.
  13. Google Patents, Coverage: document counts and the offices indexed in full text.
  14. WIPO PATENTSCOPE, Cross Lingual Expansion: 14 languages, automatic and supervised modes.
  15. DAPFAM: A Domain-Aware Family-level Dataset to benchmark cross domain patent retrieval, Ayaou, Cavallucci and Chibane, arXiv:2506.22141, 2025.
  16. Benchmarking Patent Embeddings: A Multi-Task Evaluation of 22 Models, arXiv:2605.24297.
  17. Large Legal Fictions: Profiling Legal Hallucinations in Large Language Models, Dahl, Magesh, Suzgun and Ho, arXiv:2401.01301; peer-reviewed in the Journal of Legal Analysis, vol. 16 (2024).
  18. Hallucination-Free? Assessing the Reliability of Leading AI Legal Research Tools, Magesh, Surani, Dahl, Suzgun, Manning and Ho, arXiv:2405.20362; peer-reviewed in the Journal of Empirical Legal Studies (2025).
  19. Patsnap Eureka, IP Drafting agents: CNIPA, USPTO and EPO standards, jurisdiction-specific rule libraries, compliance review.
  20. Patsnap Open Platform, pricing: Starter tier, 10,000 credits for 90 days.
  21. DeepIP, Security and DeepIP homepage: Word integration, published API and data handling commitments.
  22. Patsnap, PatentBench for Novelty Search: metric definitions, 340-sample cross-jurisdiction dataset, examiner-cited ground truth, test date July 2026.
  23. WIPO, International Patent Classification: hierarchical, language-independent classification of patents and utility models.
  24. EPO, Simple patent families (DOCDB) and EPO, Extended patent families (INPADOC).
  25. USPTO, Guidance on Use of Artificial Intelligence-Based Tools in Practice Before the USPTO, 89 FR 25609, 11 April 2024.
  26. 37 CFR 11.18(b), eCFR: certifications made by the party presenting a paper to the USPTO.
  27. ABA Formal Opinion 512, Generative Artificial Intelligence Tools (PDF), 29 July 2024.
  28. WIPO, Generative AI: Navigating Intellectual Property (PDF), 2024.

Match the stack to the work

Agents built for the patent corpus, feature-level outputs you can audit, and the whole thing callable from the assistant your team already uses.

Try Patsnap Eureka free