Not a law firm. No legal advice, no attorney-client relationship — the published math, with its source.legalbythenumbers.com is not a law firm and does not provide legal advice. Using this site does not create an attorney-client relationship. We publish the guideline formulas, statutory requirements, and filing deadlines that states and counties publish themselves, and we link the official source for every figure. For advice about your own situation, consult a lawyer licensed in your state.

Developers

Legal by the Numbers exposes four developer surfaces: an MCP server for AI assistants, public versioned rule packs, embeddable calculator widgets, and llms.txt. Everything is backed by the same verified data our own pages use — every response and every pack carries its provenance. No consumer legal site publishes its underlying figures; this one does.

MCP server

Streamable-HTTP Model Context Protocol endpoint:

https://api.cosyslabs.com/legalbythenumbers/mcp

Tools are generated from the same registry that powers the site’s calculators, so the live list is always the server’s own tools/list response. Every tool response cites the rule pack it computed from — packId, verifiedDate, and the official sourceUrl — and carries the estimate-only disclaimer, so an assistant can never present a figure without the caveat and the source that belong to it. Coverage follows the wings of the site, with tools landing as each wing’s rule packs are verified:

Injury Settlement Math
Child Support Guidelines
Alimony & Custody Schedules
Will Requirements by State
Property Tax Appeals

See the MCP quickstart for Claude Desktop and ChatGPT setup.

Public rule packs

Every changing figure on this site (state child support guideline parameters, comparative-negligence rules, damage caps, filing deadlines, spousal-support formulas, will execution requirements, county assessment-appeal windows) lives in a versioned JSON rule pack, published read-only:

https://legalbythenumbers.com/rulepacks/index.json   — pack directory
https://legalbythenumbers.com/rulepacks/<packId>.json — individual packs

Each pack includes provenance fields: packId, effectiveYear, sourceUrl (the statute, guideline, or county notice it was transcribed from), verifiedDate, and status (verified or update-pending). If you consume a pack, honor status — stale law should fail loud, not silently. A jurisdiction with no pack means we could not open an official source for it, not that it has no rule. The data page describes the dataset in full.

llms.txt

AI crawlers and agents should start at /llms.txt, which maps the site’s tools, rule packs, and compliance notes in a machine-friendly format.

Embeddable widgets

Embed any calculator with a single iframe using the /embed/<slug> pattern:

<iframe
  src="https://legalbythenumbers.com/embed/<tool-slug>"
  width="100%"
  height="620"
  style="border:none;border-radius:12px"
  title="Calculator name"
></iframe>

No API key required.

Attribution requirements

Embeds include an attribution link back to legalbythenumbers.com — it and the disclaimer beneath it must remain visible and unmodified.
If you republish figures from our rule packs, cite both the official source (sourceUrl) and this site as the transcription source.
Bulk scraping or redistribution of the site or rule packs without written permission is not allowed — ask us instead.
Anything you build on this data inherits our framing: estimate ranges only, not legal advice, no attorney-client relationship, and no prediction of a settlement, award, or court order.

Contact

Integration or partnership inquiries: support.cosyslabs@gmail.com