Skip to main content
The Lexera Protocol exposes its capabilities as Model Context Protocol (MCP) tools invoked with JSON-RPC 2.0 messages over a Server-Sent Events connection. This page summarizes every tool, its authentication requirement, and how to invoke it.

​
Invocation pattern

Every MCP tool is called through the same JSON-RPC method: tools/call. The params.name field selects which tool to run, and params.arguments carries the tool-specific payload.
JSON-RPC skeleton
Send this payload as a POST to the session URL you receive from the SSE stream. The POST returns HTTP 202 Accepted, and the tool’s execution result is streamed back over the open SSE connection.
For the full transport walkthrough, see Execution Lifecycle.

​
Available tools

lexera_local_statutory_audit

Free, unauthenticated statutory compliance check. Part of the anonymous PLG funnel.

lexera_check_jurisdiction_rates

Query the AED wallet hold required for a given jurisdiction before dispatch.

lexera_route_to_specialist

Dispatch a document to a human attorney queue. Places a temporary AED wallet hold.

lexera_get_order_status

Poll a dispatched order for status and, once complete, certified artifact URLs.

​
Authentication requirements

Even for unauthenticated tools, the same SSE + JSON-RPC transport applies. See Authentication for header formatting.

​
Typical flow

1

Preflight pricing

Call lexera_check_jurisdiction_rates to see the required AED hold for the target jurisdiction.
2

Dispatch the document

Call lexera_route_to_specialist with the document text, jurisdiction, and specialist instructions. Capture the returned order_id.
3

Poll for completion

Call lexera_get_order_status with the order_id until current_status becomes verified_executed.
4

Download the artifact

Fetch certified_redline_url with your Bearer token to receive the law firm-certified .docx.

Wallet and pricing

How AED holds and jurisdiction tiers work.

Errors

HTTP codes and streamed JSON error payloads.