Developers

Every fact we serve carries the identifier of the document it came from, so your users can check it and your agent can cite it:

• Act-derived facts carry numac, the Belgian gazette publication number, plus the publication date.
• Mandates carry the numac and publication date of the act that established them.
• Register facts (name, legal form, seat, status, NACE) come from the KBO/BCE open data.
• Financial figures are the lines as filed with the National Bank; ratios are derived from them and labelled as derived.

The other half of the promise is admitting what is missing. Deep act extraction does not cover the whole corpus yet, so the MCP surface exposes get_extraction_status: it tells you how many gazette acts are on file for a company and how many have been extracted, so an empty timeline is explainable rather than mysterious. Sector-inapplicable financial ratios come back as an explicit not-applicable marker with a reason, never as a misleading number.

Send your key in the X-Api-Key header. There is no bearer-token form and no query-string form. Keys are issued by hand today: mail enterprise@checked.be and say what you are building. There is no self-service key page yet, and this reference will not pretend otherwise.

curl -sS -H "X-Api-Key: $CHECKED_API_KEY" \
  https://checked.be/api/v1/companies/0400378485

The gate is fail-closed: if no keys are provisioned on the server, every call gets 401, including calls that carry a key.

Four endpoints. The {kbo} path segment accepts any form whose digits end in a 10-digit enterprise number: 0400378485, 0400.378.485 and BE0400378485 all resolve to the same company.

The dossier spine: identity, seat, risk band, insolvency rollup and the mandate list. risk is never null (an unscored company gets band Unknown with score 0); rollup and address are null when we hold nothing. band is PascalCase and one of Unknown, Low, Moderate, Elevated, High, Severe.

{
  "enterprise_number": "0400378485",
  "legal_name": "COLRUYT GROUP",
  "legal_form": "610",
  "primary_nace": "47110",
  "status": "active",
  "address": { "street": "...", "zip": "1500", "city": "Halle" },
  "risk": {
    "band": "Low", "score_out_of100": 88, "probability": 0.0121,
    "altman_z": 3.42, "model_version": "...", "evaluated_at": "2026-07-30T02:11:04+00:00"
  },
  "rollup": null,
  "insolvency_event_count": 0,
  "admin_event_count": 4,
  "mandates": [
    { "role": "...", "role_kind": "...", "name": "...", "address": null,
      "from": "2019-05-14", "to": null, "source": "...", "source_numac": "2019..." }
  ]
}

A bare JSON array of legal-lifecycle events, no envelope. source is one of faillissement, reorg, insolvency_interim, kbo_admin; severity is low, med or high. Not paginated: you get the whole timeline.

[
  { "source": "faillissement", "severity": "high", "numac": "2026...",
    "pub_date": "2026-05-20", "event_kind": "...", "court": "...",
    "event_date": "2026-05-14", "detail": "..." }
]

The compact insolvency aggregate on its own, for cheap screening of a portfolio. Returns 404 when the company exists but has no rollup on file.

{
  "total_events": 3, "interim_signals": 1, "reorg_events": 1,
  "faillissement_events": 1, "first_signal_date": "2026-01-05",
  "last_signal_date": "2026-05-20", "has_open_faillissement": true
}

Company lookup by name, enterprise number, VAT number or NACE code. limit defaults to 20 and is clamped to 1..50. A blank or missing q returns [] with status 200, not an error. Not paginated and no total count: this is a resolver, not a corpus dump. match_kind tells you which lane matched (name, address, kbo, nace). On this endpoint kind is always company and href/subtitle are always null; they exist so the shape matches the internal omni-search wire format.

curl -sS -H "X-Api-Key: $CHECKED_API_KEY" \
  'https://checked.be/api/v1/search?q=colruyt&limit=5'

[
  { "enterprise_number": "0400378485", "legal_name": "COLRUYT GROUP",
    "slug": "colruyt-group-0400378485", "city": "Halle", "primary_nace": "47110",
    "match_kind": "name", "matched_address": null, "kind": "company",
    "href": null, "subtitle": null }
]

Every error carries a JSON body with a single error string. Match on the status code, not on the wording.

One caveat worth knowing before you build a batch job: the REST budget is per IP and is shared with the unauthenticated /internal/search and /health/status endpoints. If you need sustained throughput, higher limits are a mail away rather than something to work around.

https://checked.be/mcp speaks MCP over streamable HTTP: JSON-RPC 2.0 on POST, an event stream on GET, session id in the Mcp-Session-Id header. Protocol versions 2024-11-05 through 2025-11-25 are negotiated at initialize. Server identity is Checked.be version 1.0.0. The legacy HTTP+SSE transport is disabled, so that one path is the entire surface: there are no separate stream or message endpoints to configure. Six tools, no resources, no prompts, nothing that writes.

The endpoint requires the same X-Api-Key header as the REST API. A client configuration without it will fail at initialize with a 401.

{
  "mcpServers": {
    "checked": {
      "type": "http",
      "url": "https://checked.be/mcp",
      "headers": { "X-Api-Key": "your-key" }
    }
  }
}

Key name and nesting differ per client (some use servers rather than mcpServers); the URL, the transport type and the header are what matter.

Every tool result carries a source attribution string and, where relevant, a dossierUrl a human can open. National register numbers are stripped from every field before serialization.

Breaking changes get a new path version and are announced to every key holder by mail before they ship. Additive changes (new fields, new MCP tools) land in v1 and are listed here, so write tolerant parsers.

Short marketing overview of the same API: the API page. Where the data comes from: sources. How we score: methodology. Browse the corpus: company search.