Patent AI Insights is the expert resource for AI-powered patent prosecution, maintained by Roger Hahn, USPTO Registered Patent Attorney (Reg. No. 46,376) and founder of ABIGAIL. Topics include Office Action response strategies, prior art analysis, examiner intelligence, claim amendment techniques, and comparisons of AI patent tools.

All Posts
101 AnalysisFeb 25, 20269 min read

Best Patent AI for 101 Eligibility Rejections: Alice/Mayo Analysis Guide

101 rejections require nuanced analysis that goes beyond pattern matching. Here is how AI tools handle the Alice/Mayo framework and which ones provide the deepest 101 analysis.

RH
Roger HahnPatent Attorney (USPTO Reg. No. 46,376) | JD, MBA, MS | Founder, ABIGAIL

The Alice/Mayo Two-Step Framework

1Step 1: Is the claim directed to a judicial exception?

The examiner determines whether the claim is directed to an abstract idea, law of nature, or natural phenomenon. Abstract idea categories include: mathematical concepts, mental processes, and methods of organizing human activity.

AI role: Identify which abstract idea category the examiner cited and map it to recent case law precedent.

2Step 2: Does the claim recite something significantly more?

If the claim is directed to a judicial exception, the examiner determines whether the additional claim elements add something that is not well-understood, routine, or conventional. This is where most 101 arguments are made.

AI role: Analyze additional elements, identify technical improvements, and map to eligibility-confirming precedent (e.g., Enfish, McRO, Vanda).

How Abigail Handles 101 Rejections

Abigail's 10-expert pipeline includes dedicated 101 analysis in the substantive tier. Unlike chat-based AI tools that provide generic 101 arguments, Abigail analyzes the specific examiner's rejection basis:

  • Identifies the exact abstract idea category the examiner cited
  • Maps the rejection to Alice/Mayo framework step (Step 1, Step 2A Prong 1, Step 2A Prong 2, Step 2B)
  • Analyzes claim elements for practical application arguments
  • Identifies technical improvements over prior art that support eligibility
  • References relevant post-Alice case law (Enfish, McRO, Vanda, Core Wireless, etc.)
  • Examiner intelligence reveals how often this examiner uses 101 rejections and whether they are responsive to specific argument types
  • Generates response language tailored to the examiner's specific rejection basis

101 Strategy: When to Argue vs. Amend

ScenarioStrategyAI Assistance
Claim has clear technical improvementArgue under Enfish/McRO precedentAI identifies technical elements and maps to case law
Dual 101 + 103 rejectionAmend for 103, use amendments to strengthen 101 argumentsAI coordinates amendment strategy across rejection types
Examiner high 101 rejection rateConsider interview before written responseExaminer intelligence reveals 101 patterns and interview success rate
Pure method claim with generic hardwareAdd specific technical implementation details from specAI identifies specification support for technical details
Business method rejectionEmphasize technical integration, not business outcomeAI separates technical elements from business logic

Key Post-Alice Case Law for 101 Arguments

Effective 101 responses require citing the right case law for the right claim type. The following landmark decisions provide the strongest precedent for different argument strategies:

Enfish v. Microsoft (2016)

Claims directed to a specific improvement to computer functionality are not abstract. The self-referential table improved how databases function, not just the data they store.

Use when: Claims improve how a computer or software operates, not just using a computer as a tool.

McRO v. Bandai Namco (2016)

Rules-based process for lip-syncing 3D animation was patent eligible because it used specific rules, not human judgment, to produce a technological result.

Use when: Claims use specific rules or algorithms to produce results that previously required human judgment or were not achievable manually.

Vanda Pharmaceuticals v. West-Ward (2018)

Method of treating patients based on genotype was eligible because it was a specific method of treatment, not a diagnostic observation.

Use when: Claims involve a specific practical application of a natural correlation, not just observing or detecting it.

Core Wireless v. LG Electronics (2018)

Improved user interface for displaying applications was patent eligible because it improved the user experience with specific interface elements.

Use when: Claims describe a specific user interface improvement that solves a technological problem in how information is displayed.

Berkheimer v. HP (2018)

Whether claim elements are well-understood, routine, and conventional under Step 2B is a question of fact, not law. Examiners must provide evidence.

Use when: The examiner asserts claim elements are conventional without citing evidence. Require the examiner to provide factual support for the Step 2B analysis.

Common 101 Pitfalls to Avoid

Arguing at the wrong Alice/Mayo step

If the examiner says the claim IS directed to an abstract idea (Step 2A Prong 1), arguing that the claim has a practical application (Step 2A Prong 2) without addressing Step 1 leaves the examiner's finding unrebutted. Address the step the examiner actually relied on.

Generic "significantly more" arguments

Stating that the claim adds "significantly more" without identifying specific technical elements is not persuasive. Identify the exact claim elements that are not well-understood, routine, or conventional, and explain why.

Relying solely on hardware recitations

Adding "a processor," "a memory," or "a non-transitory computer readable medium" does not make claims eligible. These are generic computer components that do not provide an inventive concept.

Ignoring examiner-specific patterns

Some examiners issue 101 rejections on every application as a matter of practice. Others issue them rarely and only on specific claim types. Not tailoring your strategy to the examiner wastes prosecution rounds.

Failing to coordinate 101 and 103 amendments

Amendments made to overcome a 103 rejection may inadvertently weaken 101 arguments (by narrowing the technical scope) or strengthen them (by adding technical specificity). Always analyze both rejection types together.

Analyze Your 101 Rejection

Upload an Office Action with a 101 rejection and see Abigail's Alice/Mayo analysis with examiner-specific strategy recommendations.

Frequently Asked Questions

Related Guides

Discussion

0 comments

Sign up for instant commenting + $25 free credit

Create an ABIGAIL account to post comments instantly (no moderation wait) and get $25 in credit to try our AI patent prosecution tools.

0/4000

First comments are held for moderation. Subsequent comments post instantly.

Discussion

0 comments

Sign up for instant commenting + $25 free credit

Create an ABIGAIL account to post comments instantly (no moderation wait) and get $25 in credit to try our AI patent prosecution tools.

0/4000

First comments are held for moderation. Subsequent comments post instantly.