Analyze Office Action
Paid Endpoints
Analyze Office Action
POST
Analyze Office Action
This is the core endpoint. Submit the full text of a USPTO office action and receive a structured analysis with claim-by-claim breakdown, rejection bases, prior art mapping, and strategic recommendations. Every response includes Glass Box transparency metadata.Documentation Index
Fetch the complete documentation index at: https://docs.abigail.app/llms.txt
Use this file to discover all available pages before exploring further.
Typical workflow
- Call
/lookup/{app_number}to get the examiner name - Call
/analyzewith the office action text - Use the returned
analysis_idto call/draft-roa
Office action types
| Code | Meaning |
|---|---|
CTNF | Non-final rejection (default) |
CTFR | Final rejection |
CTED | Restriction requirement |
CTRS | Requirement for information |
Examiner intelligence
Wheninclude_examiner_intel is true (default), the analysis includes examiner
behavior patterns that inform the strategy recommendations. Set to false to skip
this step and reduce processing time.Authorizations
API key for paid endpoints. Create in your account Settings at https://abigail.app
Headers
Your Abigail API key (format: abi_sk_...).
Body
application/json
USPTO application number.
Full text of the office action.
Office action type code. Common: CTNF (non-final), CTFR (final), CTED (restriction).
Include examiner intelligence in the analysis.
