# eMPEP — Full LLM Context

> eMPEP is a professional MPEP platform for patent practitioners and AI agents, providing structured access to all USPTO MPEP content, 35 U.S.C., and 37 C.F.R. via web UI, REST API, and MCP server.

## About eMPEP

eMPEP (empep.com) hosts and enhances the Manual of Patent Examining Procedure — the definitive guide governing U.S. patent examination practice. The platform is built for:
- Patent attorneys and agents performing prior art and procedure research
- In-house IP teams managing patent portfolios
- AI agents and LLM applications that need programmatic access to patent law
- Law school and academic researchers

The content is sourced from official USPTO publications, stored in a structured database, and served with enhanced formatting, cross-referencing, and search.

## Content Coverage

- MPEP Chapters 100–2900 (all chapters, all subsections)
- Appendix II — Patent Laws
- Appendix L — Patent Rules (37 C.F.R.)
- Appendix R — Rules of Practice
- Appendix T — Patent Cooperation Treaty
- Appendix AI — Administrative Instructions
- Appendix P — PCT
- 35 U.S.C. — full statutory text (§§ 1–390)
- 37 C.F.R. — full regulatory text

## REST API

Base URL: https://empep.com

### Authentication
Option A — API Key (rate-limited, subscription-based):
  Authorization: Bearer empep_<your_key>

Option B — x402 micropayment (no sign-up, $0.005 USDC per call):
  Network: Base Sepolia (eip155:84532)
  Facilitator: https://x402.org/facilitator
  First call without payment returns HTTP 402 with payment requirements.

### Endpoints

GET /api/section/:id
  Retrieve a single MPEP section by ID.
  :id examples: 101, 2106, 2106.01, 706.07
  Returns: { id, title, chapter, sectionType, content (HTML) }

GET /api/chapter/:chapter
  Retrieve all sections in a chapter.
  :chapter examples: 100, 2100, 2700
  Returns: array of section records

GET /api/chapter/:chapter/subsections
  List subsection metadata for a chapter (no full content).
  Returns: array of { id, title, chapter }

GET /api/search/:query
  Full-text search across all MPEP section titles and content.
  Returns: up to 50 matching sections

GET /api/mpep/section/:sectionNumber
  Alias for /api/section/:id

GET /api/mpep/chapter/:chapterNumber
  Alias for /api/chapter/:chapter

GET /api/appendix/:appendixId/subsections
  List subsections for an appendix.
  :appendixId examples: II, L, R, T, AI, P

GET /api/appendix/search/:query
  Full-text search across appendix content.

### Response Format
All endpoints return JSON:
  { success: true, data: <payload> }
  { success: false, error: "<message>" }

## MCP Server

The eMPEP MCP (Model Context Protocol) server exposes MPEP content as tools that AI agents can invoke directly.

Endpoint: https://empep.com/mcp (Streamable HTTP transport)

Full MCP instructions: https://empep.com/mcp.txt

### Tools Available
- search_mpep — Full-text search across all MPEP content
- get_section — Retrieve a specific MPEP section by ID
- get_chapter — Retrieve all sections in a chapter
- get_chapter_subsections — List subsections in a chapter

## Pricing

- Free tier: 5 req/min, 100 req/day — no credit card needed
- Developer: $29/mo — 60 req/min, 10,000 req/mo included
- Enterprise: $199/mo — 300 req/min, 100,000 req/mo included
- x402 pay-per-call: $0.005 USDC per request (no subscription)

Details: https://empep.com/api-pricing

## Company

Managed by the team at Wysebridge (https://wysebridge.com).
Contact: support@empep.com | enterprise@empep.com