lawflow.dev

Pricing

Metered by request. Provenance included at every tier.

Full provenance — source, hash, validity dates — is the product, not an enterprise add-on. Every tier gets it on every response. The coverage endpoint is free and unmetered for everyone.

Explorer

$0

no card required

1,000 requests / monthAll datasets, full provenanceCurrent-law queriesCommunity support
Get a key

Build

most popular

$99 /mo

then $2 per 1K requests

50,000 requests / monthPoint-in-time (as_of) queriesMCP server accessEmail support
Start building

Scale

$499 /mo

then $1 per 1K requests

500,000 requests / monthBulk export & syncSupersession webhooksPriority support · 99.9% SLA
Start scaling

Enterprise

Custom

annual agreements

Unlimited requestsIngestion priority for your jurisdictionsDPA, security review, custom SLADedicated engineer
Talk to us

Attorneys and law firms reviewing their own records never pay — that's not a tier, it's a principle.

Pricing shown is draft and subject to change.

Common questions

What counts as a request?

One API call or one MCP tool invocation. Explicit misses are billed at one-tenth of a request — you shouldn't pay full price to learn we don't have something.

Is provenance really on every tier?

Yes. Source URL, retrieval time, content hash, and validity dates on every response, including the free tier. Trust isn't an upsell.

What happens when I hit my limit?

Overage is metered at your tier's per-1K rate, with a spend cap you set. We never silently degrade results.

Can you prioritize my jurisdiction?

Yes — ingestion order is driven by customer demand on Build and above; Enterprise agreements can pin specific jurisdictions to a delivery date.

lawflow.dev

Point-in-time US law with the receipt attached. Source URL, retrieval time, content hash, and validity dates on every answer.

curl api.lawflow.dev/v1/statutes/coverage

© 2026 lawflow.dev · a do.dev productAttorneys and firms never pay. Ever.