Regulatory Check API · Layer 3

The same determination, inside your product.

Pass a tool, a use case and a footprint. Receive structured, cited obligations from the Meridian™ — so you can show deploying customers what they are walking into, or license that intelligence into what you already sell.

Talk about licensing What it returns

Transport

REST / JSON over TLS

Access

Scoped keys, audit-logged

Provenance

Cited to the Meridian™

What it returns

Structured records, not prose about the law.

Everything the endpoint returns is machine-readable and carries the citation it was determined from. If you have to parse a paragraph to find the obligation, we have handed you the wrong thing.

Instruments

Laws, regulations and guidance

Organised into structured records with jurisdiction, regulator, status and commencement — the identity fields you need to store them, not just display them.

Pinpoints

Article-level citations

Each obligation carries the provision it came from, resolving to the official text. The same pin our own reports are sealed against.

Scope

Jurisdiction × industry mapping

Countries, regions and US states mapped to sector applicability for the deployment described in the request.

What this is not. LegisGate produces regulatory intelligence and assessment-preparation materials. Nothing we produce is legal advice, a legal opinion, a certification, or a determination of compliance, and no document we deliver satisfies a legal obligation on its own. Sufficiency is determined by your counsel. A response tells your customer what attaches. It does not tell them they are compliant, and your product should not imply that it does.

The shape of a call

Five axes in. A determination out.

The same five axes the report uses, because it is the same engine. Illustrative — your licensed schema is agreed during scoping.

POST /v1/determination

{
  "tool": "applicant-screening-model",
  "use_case": "hiring",
  "jurisdictions": ["US-IL", "US-NY", "EU"],
  "industry": "healthcare",
  "data_types": ["personal", "health"]
}

200 application/json

{
  "obligations": [
    {
      "obligation_id": "OBL-04",
      "title": "Bias audit before use",
      "statutory_citation": "NYC Admin. Code § 20-871",
      "jurisdiction": "US-NY",
      "severity": "High",
      "owner_role": "People Operations",
      "deadline_band": "Near-term",
      "meridian_ref": "nyc-ll144:provision:2"
    }
  ],
  "assessed_not_applicable": 7,
  "corpus_version": "2026-08-28"
}

Note assessed_not_applicable. The instruments that were evaluated and did not attach are part of the answer, not noise stripped out of it — the absence of a duty is only worth anything if you can show it was looked for.

How licensing works

A conversation, then credentials.

Access is scoped rather than self-serve, because what you are licensing is a corpus with terms attached, not a rate limit.

01 · License

Scope the license

We agree the datasets, instruments, jurisdictions, volume, and how determinations will be presented inside your product — including what your interface must not imply.

02 · Connect

Authenticate and call

Scoped credentials against versioned endpoints and documented schemas. Audit-logged on our side, so both parties can reconstruct what was served and when.

03 · Stay current

Stay live without re-authoring

The Meridian is maintained continuously from official sources. Optional change notifications when a licensed instrument moves, so your product ages the way the law does rather than the way your last release did.

Build on it

Your customers are asking your product this question.

If you sell software that touches AI deployments, the deployer-burden question arrives at your support queue whether or not you have an answer. License one.

Talk about licensing Talk to us