# Lex Engine Canonical website: https://lex.titho.tech/ Purpose: Source-linked legal and regulatory intelligence for people, software, and AI agents. Last reviewed: 2026-08-11 ## What Lex Engine does Lex Engine converts official public court and regulatory records into structured legal events, normalized companies, timelines, review-priority signals, and provenance-linked datasets. It is designed for legal research, compliance monitoring, insurance, investment research, litigation analysis, academic work, and AI product development. Lex Engine is informational data infrastructure. It is not a law firm, does not provide legal or investment advice, and does not predict liability, damages, misconduct, or case outcomes. Automated entity resolution, classifications, summaries, and review-priority scores must be checked against the linked official source. ## Current data products - Legal event search with jurisdiction, event type, date, and risk-review filters. - Canonical company profiles and historical legal-event timelines. - Court dockets, opinions, regulatory records, source URLs, and SHA-256 provenance hashes. - Watchlists, saved searches, alert inboxes, webhooks, and JSON/JSONL/CSV exports. - Daily official-source legal intelligence briefs. - REST/OpenAPI access at https://lex.titho.tech/docs and https://lex.titho.tech/openapi.json. - MCP tool endpoint at https://lex.titho.tech/mcp. ## Pricing in USD - Explorer: $0/month. 100 API credits per month, one user, three private watchlists, public search, and company profiles. - Developer: $49/month or $490/year. 10,000 API credits per month, one user, API keys, standard webhooks, and ten watchlists. - Pro Team: $149/month or $1,490/year. Three seats, 25,000 API credits per month, and twenty watchlists. - Enterprise Data: from $1,500/month under contract. From 250,000 API credits, bulk feeds, custom exports, volume pricing, and an SLA. Paid court retrieval and unusually expensive processing are not included unless explicitly stated. Those costs are quoted separately. Checkout and subscription management use Stripe. Machine-readable pricing: https://lex.titho.tech/v1/public/pricing Human pricing: https://lex.titho.tech/#pricing ## Public programmatic entry points - GET /v2/intelligence/search?q=QUERY — structured legal-event search. - GET /v2/intelligence/signals — recent events prioritized for review. - GET /v1/events — legal-event feed. - GET /v1/events/{event_id} — one source-linked legal event. - GET /v1/companies — canonical company search. - GET /v1/companies/{entity_id}/timeline — a company's legal-event timeline. - GET /v1/sources — configured public data sources. - GET /v1/health — current pipeline coverage and health. - GET /v1/export — small public export. - GET /v1/premium/export — paid bulk export; returns HTTP 402 without paid access. API documentation: https://lex.titho.tech/docs OpenAPI document: https://lex.titho.tech/openapi.json Agent catalog: https://lex.titho.tech/.well-known/agent-catalog.json AI use and crawler policy: https://lex.titho.tech/ai-policy.json Changelog: https://lex.titho.tech/changelog ## MCP Send JSON-RPC 2.0 requests to POST https://lex.titho.tech/mcp. Supported public tools are search_legal_events, search_companies, get_legal_event, get_sources, and get_pricing. export_legal_events requires a paid-plan API key in the X-API-Key header. ## Integrations and requirements - Stripe Checkout and Stripe's customer portal handle paid subscriptions. - REST clients may use JSON directly; no browser automation is required. - OpenAPI clients can generate typed SDKs from /openapi.json. - MCP clients use Streamable HTTP JSON-RPC at /mcp. - Authenticated REST and premium MCP requests use the X-API-Key header. - Webhooks require an HTTPS destination and should validate the configured shared secret. - Lex Engine does not replace legal counsel, PACER, a court docket of record, or an official agency publication. ## Detailed buyer FAQ Q: Are source documents official? A: Each record identifies its source URL and provenance where available. Source coverage varies by court and agency. The linked court or agency record remains authoritative. Q: Does a risk score predict whether a company will lose a case? A: No. The score prioritizes records for human review using available metadata. It does not predict liability, damages, financial impact, misconduct, or outcome. Q: Can the data train an AI model? A: Enterprise data licenses may support AI development, subject to the signed license and the rights attached to underlying source material. Public endpoint access alone does not grant ownership of third-party documents. Q: Is full historical coverage guaranteed? A: No. Coverage depends on official source availability, source-specific history, parser support, and backfill progress. Review /coverage and /v1/sources before relying on a jurisdiction or date range. Q: What happens when an API allowance is exhausted? A: The standard authenticated API returns a rate or monthly-credit error. Premium bulk resources return HTTP 402 when paid access is absent and link to current pricing. Q: Are PACER and other paid document fees included? A: No, unless a written plan or order explicitly says otherwise. Third-party court and retrieval fees are disclosed separately. Q: How are corrections handled? A: Submit a source-linked correction at https://lex.titho.tech/data-corrections. Automated records retain provenance and review status so users can evaluate reliability. Q: What personal data does Lex Engine require? A: A free or paid account uses a name or organization and work email. Operational logs support security and aggregate reliability. Review /privacy and /data-policy for current terms. Q: Can an AI agent purchase access automatically? A: The current production purchase flow uses Stripe Checkout. Premium endpoints advertise HTTP 402 payment metadata, but no cryptocurrency or unverified micropayment protocol is claimed as active. Q: Is there a service-level agreement? A: Only Enterprise Data contracts include a negotiated SLA. Explorer, Developer, and Pro Team use the published service and support policies.