Documentation Overview
Entry point for the Lagrange trademark data API docs: quickstart, data model, search and screening, coverage and AI Agent integration.
Lagrange provides a unified trademark data API: a single integration to search, screen and monitor trademark records across multiple jurisdictions. The data structure is normalised, status semantics are consistent, and both an OpenAPI spec and an MCP Server are available.
Start here
| Goal | Page |
|---|---|
| Get your first result in five minutes | Quickstart |
| Understand authentication and key management | Authentication & keys |
| See the structure of one trademark record | Data model |
| Learn how statuses are normalised across offices | Status taxonomy |
| Look up search and similarity parameters | Trademark search |
| Check coverage and sync cadence per office | Coverage & freshness |
| Import into Postman / generate an SDK | OpenAPI spec |
| Connect Claude Desktop / Cursor | MCP Server |
Machine-readable entry points
Everything on this site is available in three forms for crawlers and AI agents:
/en/llms.txt— page index for the English docs (title + link + summary)/llms.txt— page index for the full Chinese documentation- Use Copy Markdown / More AI actions above every page, or replace the page path with
/llms.mdx/en/docs/<slug>/content.md
Authentication & billing
All endpoints use API key authentication. Search endpoints cost 10 credits per call, other endpoints 1 credit, and failed requests cost nothing. See Authentication & keys.
Conventions
- Responses use the
{ code, msg, data }envelope;code="0000"means success - Timestamps are Unix milliseconds;
0means unknown - Pagination uses
current/sizein requests anddata.current/size/total/recordsin responses - Only original office data is stored, with no translation; records join directly on the official registration number (
externalId)