Documentation

What lawfirm.dev gives you

lawfirm.dev is a data API for the legal world with one rule: every answer can prove where it came from. There are two data domains behind one base URL and one API key.

Attorneys & firms

Who is licensed, where they work, and how to reach them — built from official bar records and state filings, kept accurate by the attorneys themselves. Every field tells you its source, when it was asserted, and at what confidence.

Attorney & firm docs →

Statutes, point-in-time

The authoritative text of a state statute as it was in force on any date — so AI tools can prove a citation is real and correctly quoted instead of trusting the model. Versioned, hashed, and traced to the state's own publication.

Statute docs →

Sixty-second start

  1. Get a key — email hello@lawfirm.dev (free tier: 100 lookups/month). Keys look like lf_live_….
  2. Send it as a Bearer token to https://api.lawfirm.dev/v1:
    # Is this person a licensed Florida attorney?
curl "https://api.lawfirm.dev/v1/bar-admissions/verify?jurisdiction=FL&barNumber=112233" \
  -H "Authorization: Bearer lf_live_..."

# What did § 768.28, Fla. Stat. say on March 14, 2020?
curl "https://api.lawfirm.dev/v1/statutes/lookup?jurisdiction=fl&citation=768.28&asOf=2020-03-14" \
  -H "Authorization: Bearer lf_live_..."
  3. Read the response's provenance before you trust it — that habit is the whole product. Attorney data carries _meta.fieldSources; statute text carries a source URL, retrieval time, and content hash.

The one idea to understand

Legal data providers usually hand you a value. lawfirm.dev hands you a value and its receipt: which official source produced it, the URL, the timestamp, and a confidence score — with the losing values preserved in an append-only log you can audit. For statutes the same idea becomes time travel: instead of “the law,” you ask for “the law as of a date” and get the exact text in force then, or an honest “not on file” — never a nearest guess.

Where to go next

  • Attorneys — lookup & search, licensing verification, and the provenance audit trail.
  • Firms — how firm records are inferred and confirmed, rosters, entity status.
  • Statutes — the asOf model, temporal honesty, search, coverage.
  • Auth, errors & spec — keys, scopes, rate limits, error codes, OpenAPI downloads.
  • SDK & MCP — the TypeScript client and agent tool definitions.