Bidda Gap Check =============== JS-free text mirror for AI crawlers. Canonical page: https://bidda.com/gap-check Last updated: 2026-08-04 COVERAGE FOR COMPLIANCE TEAMS & AGENTS The obligation you missed is the one underneath. Most coverage gaps are not the headline regulation. They are the prerequisite obligation it quietly rests on. Gap check starts from the list you already have and reports the prerequisites that are missing from it. It reads recorded dependency links, so the answer is scoped to your programme rather than to the whole registry. START FREE TRIAL → DEVELOPER DOCS → WHY IT MATTERS A programme can cover the rule everyone has heard of and still miss the obligation that rule depends on. Nothing in a spreadsheet surfaces that, because a spreadsheet does not know what depends on what. The registry records those links, so the difference between your list and the graph can simply be read off. How gap check works One call. You send your coverage, the registry returns the difference. 01 List what you already cover Send the obligations your programme already addresses. Just the identifiers, not the content. This is your own coverage list, in whatever shape your GRC tooling already holds it. 02 Bidda walks the dependency graph Every obligation in the registry records the prerequisite obligations it depends on. Gap check follows those recorded links outward from each rule you listed, one hop by default or deeper on request. 03 You get back what you did not list The response names the prerequisite obligations linked to your coverage that were absent from your list, plus any rule you did list that the registry now marks withdrawn. What comes back Findings, not a score. Gap check never ranks how well you are doing. MISSING PREREQUISITE A prerequisite you did not list An obligation the registry records as a prerequisite of something you already cover, which was absent from your list. This is the common blind spot: the headline rule is handled, the obligation it rests on is not. WITHDRAWN Something you cover was withdrawn A rule on your own list that the registry has since marked withdrawn. Worth reviewing, because effort spent maintaining it may now belong somewhere else. COVERED Nothing outstanding on that branch Every prerequisite the registry links to that rule already appears on your list. No action implied. WHAT GAP CHECK IS NOT Gap check is a coverage aid for a qualified reviewer. It reports the difference between the list you sent and the prerequisite links the registry records. It does not score your programme, rank obligations by importance, judge how well any obligation is met, or determine compliance. Those remain professional judgements, and the underlying obligations stay cited to their primary sources so a reviewer can check them directly. Call it from anywhere Available as an MCP tool and a REST endpoint. A free trial counts. MCP TOOL gap_check Call it directly from an agent framework that speaks MCP. REST ENDPOINT GET /api/v1/gap-check?nodes= Or POST a JSON body with a nodes array and an optional depth. Found a gap you now cover? Sign it as design-side evidence, with each obligation pinned to the version you relied on. CONTROL ATTESTATION → COMMON QUESTIONS What does gap check do? You send the obligations your programme already covers. Gap check returns the prerequisite obligations that the registry dependency graph links to them but that you did not list, plus any rule on your list that has since been withdrawn. It is a coverage aid for a qualified reviewer. Where do the prerequisites come from? Every node in the registry records the obligations it depends on, built as part of the same source-verification method behind the rest of the registry. That gives more than 26,000 recorded prerequisite links across the registry. Gap check reads those recorded links; it does not infer relationships on the fly. Does gap check tell me whether I am compliant? No. It reports coverage against recorded prerequisite links, nothing more. It does not rank, score, or determine compliance, and it makes no judgement about how well any obligation is met. A qualified professional still reviews the obligations themselves and how your systems meet them. How deep does it look? One hop by default, so you see the immediate prerequisites of what you listed. You can request a greater depth to follow the chain further out when you want the full picture rather than the next step. How is this different from browsing the registry? Browsing tells you what exists. Gap check starts from what you already have and reports only the difference, so the answer is scoped to your programme instead of the whole registry. How do I call it? Gap check is available as the gap_check tool over MCP and as a REST endpoint that accepts either GET with a comma-separated list or POST with a JSON body. Pass your Bidda key as api_key. A free trial counts. See what your coverage list is missing. Gap check is included with every subscription and a free trial counts. Send the obligations you cover and read the difference. START FREE TRIAL → SEE THE DEPENDENCY MAP →