Skip to main content
Abigail gives AI assistants and engineering teams programmatic access to patent prosecution: office action analysis, response drafting, USPTO forms, examiner intelligence, and docket management. The integration path is the Model Context Protocol. Point a compatible assistant at one URL and it gains 55 tools backed by the same system that runs abigail.app.
The older REST developer API at /v1/openclaw/* was retired on 2026-07-18 and its endpoints now return 404. Its pages remain under the Legacy REST API tab for reference only. New integrations use MCP.

​
Who is this for?

  • AI assistant users connecting Abigail to ChatGPT, Claude, or Cursor
  • Law firm engineering teams integrating prosecution AI into existing docketing systems
  • Product teams building patent workflows on top of an MCP client

​
What you get

​
Quick example

Every request to /mcp requires a valid Bearer token, including the protocol handshake and the tool listing. Without one the server answers HTTP 401 and a WWW-Authenticate header naming the protected resource metadata document, which is the signal a compliant client uses to start the OAuth flow automatically. You sign in once with your Abigail account; the client handles the rest.

Connect via MCP

Add Abigail to ChatGPT, Claude, or Cursor in a couple of minutes.

Tool reference

All 55 tools, what each needs, and what it maps to.

Match the web app

Reproduce every Abigail screen as a tool sequence, gaps included.

Glass Box

The AI transparency metadata behind every result.