LegalScout developer resources — OpenAPI, MCP, auth, and webhooks

LegalScout publishes machine-readable APIs so agents can search participating law firms, start confidential intake, and connect over the Model Context Protocol. This page is the named index of LegalScout developer resources (OpenAPI, MCP, auth, webhooks, versioning).

When to use LegalScout

Find a firm associate or run intake

Use LegalScout to find a participating firm's AI associate, run confidential intake for attorney review, or wire Claude / ChatGPT / another MCP host to https://legalscout.net/api/mcp. Do not use LegalScout to give legal advice or to call dashboard billing APIs.

OpenAPI, MCP, auth, and webhooks

LegalScout OpenAPI and MCP URLs

Public discovery tools need no authentication. Client matter tools use OAuth 2.1 + PKCE when the host supports it. Inbound Vapi/Stripe/Twilio webhooks are dashboard integrations, not a public agent webhook catalog — use MCP tools instead.

REST versioning and deprecation

LegalScout rate limits

The current public HTTP API is v1 at /api/v1/. Unversioned /api/ routes are permanent aliases. Breaking changes ship as /api/v2/. Deprecated operations are marked in OpenAPI and send Deprecation plus a Sunset HTTP-date at least 180 days before removal. JSON errors use { "error": { "code", "message", "hint" }, "status", "path", "docs" }. Public responses include RateLimit and RateLimit-Policy (120 requests / 60 seconds). HTTP 429 includes Retry-After. Policy JSON: https://legalscout.net/api/v1/deprecation.

LegalScout product manual

Redacted attorney-app walkthrough (associates, briefs, matters, products, dashboard): LegalScout product manual for attorneys, PDF, and Markdown.