Documentation

First verified answer in under a minute.

Three ways in: REST, the MCP server, or the TypeScript SDK. Same data, same provenance contract everywhere.

# no key needed for coverage

$ curl https://api.lawflow.dev/v1/statutes/coverage

# with a key: point-in-time statute text

$ curl "https://api.lawflow.dev/v1/statutes/lookup?jurisdiction=fl&citation=768.28&asOf=2019-03-01" \

-H "Authorization: Bearer lf_live_..."

REST API

Quickstart

Auth, pagination, the provenance envelope, and the explicit-miss contract. Everything is JSON over HTTPS.

API reference →

MCP server

For agents

https://api.lawflow.dev/mcp — streamable HTTP with an Authorization: Bearer header. Narrow tools, structured misses, citations your agent can hand to a human.

MCP quickstart →

TypeScript SDK

Typed end to end

npm i @lawflow/sdk — typed responses including the provenance envelope and miss discriminated union.

SDK guide →

Endpoint groups

GET /v1/statutes/coverageThe live coverage matrix — jurisdictions, corpora, and date ranges. Public and unmetered; no key required.

GET /v1/statutes/lookupResolve a citation to a section, with as_of point-in-time queries, validity windows, and supersession chains.

GET /v1/statutes/textFull section text for a resolved citation and version, wrapped in the provenance envelope (source_url · retrieved_at · sha256 · validity).

GET /v1/statutes/searchFull-text search across the corpus; filter by jurisdiction and corpus, ranked with citations you can follow.

?corpus=statutes|regulations|guidanceEvery /v1/statutes/* route takes a corpus parameter to select the body of law — statutes, administrative regulations, or dated agency guidance.

POST https://api.lawflow.dev/mcpStreamable-HTTP MCP server. Tools: statute_coverage, lookup_statute, get_statute_text, search_statutes. Authenticated with Authorization: Bearer.

Get a key, make a call, check the hash.

Get an API key Check coverage first