Bidda Sovereign Intelligence · 10,108 Verified Nodes · 39 Sovereign Pillars

Drift Check for AI Agents

Drift check tells an AI agent which of its cached compliance rules have changed or been withdrawn at the primary source. Submit cached fingerprints, get back fresh, drifted or withdrawn, and re-ground before acting on stale law. MCP tool and REST API.

CACHE FRESHNESS
FOR AGENTS & PIPELINES
Know when the law you cached has changed.

Agents and pipelines cache compliance rules to move fast. Drift check tells you which of those cached rules changed or were withdrawn at their primary source, so your agent re-grounds before it acts on stale law.

It is the freshness gate you call at the moment it matters, right before an agent relies on a rule it cached earlier.

START FREE TRIAL →
DEVELOPER DOCS →

WHY IT MATTERS

An agent that cached a rule six months ago will keep citing it as if nothing has moved. When the regulation is amended, that cached citation becomes a silent risk. Drift check turns that silent risk into a clear signal your agent can act on.

How drift check works

One round trip. Your agent asks, the registry answers, the agent re-grounds if it needs to.

01
Send your cached fingerprints

Your agent or pipeline sends the fingerprints of the compliance rules it has cached. You do not resend the content, just the identifiers and the version each copy is pinned to.

02
Bidda compares to the live registry

Each fingerprint is checked against the current source-verified registry, which is fingerprinted weekly against its primary legal sources.

03
You get a status for each rule

Every rule comes back as fresh, drifted, or withdrawn, so the agent knows exactly which cached copies to keep using and which to re-fetch before it acts.

Three answers, no guessing

Every rule you check comes back as exactly one of these.

FRESH
Fresh

The rule is unchanged since you cached it. The version your agent holds still matches the current registry. Safe to keep using.

DRIFTED
Drifted

The primary source behind this rule has changed since your copy was pinned. Re-fetch the current version before the agent relies on it again.

WITHDRAWN
Withdrawn

The rule has been retired from the registry. Stop relying on the cached copy and review what replaced it.

Wire it into the agent loop

Available as an MCP tool and a REST endpoint. A free trial counts, and the batch size scales with your plan.

MCP TOOL

drift_check

Call it directly from an agent framework that speaks MCP.

REST ENDPOINT

POST /api/v1/drift-check

Pass your Bidda key as api_key. A free trial counts.

Want to hear about changes early, before an agent even runs? Pair drift check with push-based change alerts.

CHANGE ALERTS →
COMMON QUESTIONS
What does drift check do?

Drift check tells you which of the compliance rules your agent has cached have changed or been withdrawn at their primary source. You submit the fingerprints of your cached rules and get back a status for each, so the agent can re-ground before acting on a stale copy.

What are the possible results?

Each rule returns one of three statuses. Fresh means it is unchanged since you cached it. Drifted means the primary source changed and you should re-fetch the current version. Withdrawn means the rule was retired from the registry and you should stop relying on the cached copy.

How is drift detected?

The registry fingerprints the primary legal source behind every rule on a weekly cycle, recording a content hash and the certificate fingerprint of the source. Drift check compares the version your agent cached against the current registry state, so a change at the source surfaces as drift.

How is this different from change alerts?

Change alerts push you a message when a source changes for the rules you subscribe to. Drift check is a pull: your agent asks, at the moment it matters, whether the specific copies it holds are still current. Many teams use both, alerts to hear early and drift check as the freshness gate right before an agent acts.

How do I call it?

Drift check is available as the drift_check tool over MCP and as a REST endpoint. Pass your Bidda key as api_key; a free trial counts. The number of rules you can check per call scales with your plan.

Does drift check guarantee my agent is compliant?

No. Drift check tells you whether the rules you cached are still current. It is a freshness signal, not a determination of compliance. A qualified professional still reviews the obligations themselves and how your systems meet them.

Stop your agents citing stale law.

Drift check is included with every subscription and a free trial counts. Add one call to the agent loop and re-ground with confidence.

START FREE TRIAL →
DEVELOPER DOCS →

⚠ Important: Human Verification Required

Bidda compliance nodes are reference intelligence, not legal advice. Every node must be reviewed by a qualified compliance professional or legal counsel before implementation in any enterprise workflow, regulated system, or compliance programme. See bidda.com/disclaimer for full terms.