bidda-compliance

{
  "id": "aix_d737afebc0",
  "name": "bidda-compliance",
  "operator": "(unclaimed - source: registry-official · publisher: com.bidda)",
  "description": "10,065 source-verified compliance nodes, 39 pillars, 25 MCP tools (EU AI Act, GDPR, NIST, MITRE).",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-25",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "api-integration",
    "breach-check",
    "citation-check",
    "gdpr-screen",
    "invoice-parsing",
    "kyc-check",
    "threat-intel"
  ],
  "protocols": {
    "mcp": "https://bidda.com/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 2043,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 47,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-25T06:01:44.504Z"
  },
  "pricing_model": "unknown",
  "public_stats": {
    "gh_stars": 1
  },
  "wallet": {
    "address": "0xD5eF3584bFa5D0ECE885A1101d00E431D3b6654A",
    "chain": "base",
    "source": "x402-challenge",
    "captured_at": "2026-09-25T06:01:44.504Z",
    "volume": {
      "usd_30d": 0,
      "biggest_usd": 0,
      "tx_count": 0,
      "sent_30d": 0,
      "sent_tx": 0,
      "balance_usd": 0.02,
      "as_of": "2026-09-24T17:01:13.058Z"
    }
  },
  "profile": {
    "mcp_server": "bidda-compliance",
    "mcp_version": "1.7.0",
    "tool_count": 25,
    "tools": [
      {
        "name": "list_pillars",
        "description": "List all compliance pillars in the Bidda Sovereign Intelligence registry with node counts. Use this first to discover available compliance domains before searching. Bidda has 10,099 cryptographically-verified nodes across 39 pillars, including a MITRE layer spanning 6 frameworks (ATT&CK Enterprise/Mobile/ICS, D3FEND, ATLAS, CAPEC) plus Banking, AI Governance, Cybersecurity, Healthcare, Legal, ESG and more."
      },
      {
        "name": "search_nodes",
        "description": "Search Bidda compliance nodes by keyword. Returns matching node summaries including a one-sentence BLUF (Bottom Line Up Front): the exact compliance obligation in plain language. Every node traces to a primary legal source (no hallucination). Examples: \"Basel III capital\", \"GDPR data breach\", \"AML transaction monitoring\", \"SOC 2 Type II\"."
      },
      {
        "name": "get_node",
        "description": "Get a specific compliance node by its ID. Returns the node summary: title, compliance pillar, version, last updated, and BLUF. The full node (machine-executable deterministic workflow, actionable schema, primary legal citations, dependency chain) is available at bidda.com."
      },
      {
        "name": "get_dependency_chain",
        "description": "Walk the prerequisite chain for a compliance node. Given one node, returns its full dependency tree (the prior obligations an agent must satisfy before this one applies). Use this to plan a complete compliance posture: unlocking one node usually requires understanding 3-8 upstream nodes. Defaults to depth 2; max 4."
      },
      {
        "name": "get_crosswalk",
        "description": "Return the cross-framework mapping dimensions for a node: which other regulations, standards, or jurisdictions this rule maps to (e.g. GDPR Article 17 → CCPA right-to-delete → POPIA Section 24). Discovery returns the available dimensions; full mapping values are vault-gated."
      },
      {
        "name": "get_latest_changes",
        "description": "List the most recently updated compliance nodes: the regulatory change feed. Use to monitor incoming amendments, new guidance, or freshly added rules. Filter by pillar to focus on a domain. Agents should call this on a schedule to keep compliance posture current."
      },
      {
        "name": "get_jurisdiction_bundle",
        "description": "Return all compliance nodes that apply in a specific jurisdiction (EU, US, UK, Australia, Singapore, India, Canada, China, South Africa, Japan, Brazil and others). Use when an agent enters a new market and needs the full regulatory surface for that geography."
      },
      {
        "name": "get_mitre_mapping",
        "description": "The MITRE Rosetta Stone. Given a MITRE technique ID across 5 frameworks (ATT&CK Enterprise, ATT&CK Mobile, ATT&CK ICS, D3FEND, ATLAS), return the Bidda node for that technique plus its mapped compliance obligations: NIST 800-53 controls, ISO 27001 Annex A clauses, PCI DSS requirements, NIS2 articles, HIPAA Security Rule, DORA articles, NERC CIP, IEC 62443. The bridge between how SOC teams think (technique IDs) and how compliance teams think (control families). Free."
      },
      {
        "name": "check_action_compliance",
        "description": "Pre-flight regulatory check. Agent describes an intended action in natural language (\"process EU resident biometric data\", \"transfer health records to a third-party AI vendor\", \"deploy autonomous trading model in Singapore\") and receives a ranked list of regulations that may apply, plus a risk indicator (LOW/MODERATE/HIGH). The primary tool for runtime compliance gating in autonomous agent workflows."
      },
      {
        "name": "browse_topics",
        "description": "Browse the registry by cross-cutting compliance TOPIC (for example data breach notification, AI transparency, AML and KYC). Returns each topic with how many rules carry it and across how many pillars and jurisdictions. Topics sit on top of the 39 pillars without replacing them. Free, no key required. Pass a topic string to drill into one."
      },
      {
        "name": "compare_jurisdictions",
        "description": "Compare how different jurisdictions address a compliance topic, side by side, including where their numeric thresholds differ (for example a breach-notification deadline of 72 hours versus 30 days). It surfaces the real rules and numbers and does not rank which jurisdiction is stricter. Requires an active Bidda subscription: pass your key as api_key."
      },
      {
        "name": "create_attestation",
        "description": "Create a signed, time-stamped record of which Bidda rules a person or AI agent relied on for a decision. Returns a record ID and a public verify URL so anyone can later confirm the record has not been changed. Useful for agents that must keep an audit trail of what they checked. Requires an active Bidda subscription: pass api_key."
      },
      {
        "name": "point_in_time",
        "description": "Get a signed record of which committed version of a rule was authoritative at a specific past date, anchored to the public history chain. Useful when an agent must show what a rule said at the moment it acted. Requires an active Bidda subscription: pass api_key."
      },
      {
        "name": "watch_changes",
        "description": "Subscribe to regulatory change alerts: watch specific rules and/or whole pillars and get notified by email or webhook when their primary source changes. Requires an active Bidda subscription: pass api_key."
      },
      {
        "name": "open_run",
        "description": "Open a run ledger: a signed, tamper-evident log of what an agent does across a whole task or conversation (for example a support-bot chat). Returns a run_id. Record one entry per turn with record_run_entry, then seal_run to get a single signed Run Receipt. Requires an active Bidda subscription: pass api_key."
      },
      {
        "name": "record_run_entry",
        "description": "Append one entry to an open run: which Bidda rules the agent consulted, what it decided, and the end user's input (as text via note, or privately as input_hash). Each entry is hash-chained to the previous one. Requires an active Bidda subscription: pass api_key."
      },
      {
        "name": "consult_node",
        "description": "The one-call governed turn: fetch the full vault node (this consumes one call on your key, exactly like unlocking a node) AND record a verified node_consulted entry for it on an open run, in a single step. The entry pins the node to its current version + integrity hash, so the run receipt proves what the agent actually consulted. Use this instead of get_node when you are inside a run. Requires an active Bidda subscription: pass api_key."
      },
      {
        "name": "get_audit_pack",
        "description": "Export a run as a governance evidence pack: the signed receipt, every entry, a roll-up of the nodes consulted (with pinned versions/hashes), an independent hash-chain + Merkle integrity self-check, and a coversheet mapping the receipt to the record-keeping obligations it supports (EU AI Act Art. 12/26, ISO/IEC 42001, NIST AI RMF). A sealed run is readable by id; a still-open run's draft pack needs your api_key."
      },
      {
        "name": "seal_run",
        "description": "Seal an open run into one signed Run Receipt covering every entry, with a public verify URL. Idempotent: sealing an already-sealed run returns the same receipt. Requires an active Bidda subscription: pass api_key."
      },
      {
        "name": "get_run",
        "description": "Fetch a run and its entries. The owner can read an open or sealed run (pass api_key); a sealed run is also publicly readable by id and reports whether its signature is valid."
      },
      {
        "name": "drift_check",
        "description": "Check whether the compliance rules an agent has cached in its own memory are still current. Submit the node_id and the integrity hash you stored when you last grounded on each rule; get back, per rule, whether it is fresh, has drifted (content changed), or was withdrawn (instrument repealed) - so the agent re-grounds before acting on stale law. Included with every API tier; the per-call batch size scales with your plan. Pass api_key."
      },
      {
        "name": "create_control_attestation",
        "description": "Sign a tamper-evident record of one of YOUR OWN controls or policies and the Bidda obligation nodes it maps to. Each obligation is pinned to its current version + integrity hash at signing time, so the record shows what the control was mapped against on that date. This is the design-side evidence ('we operate this control, mapped to these obligations'); run receipts are the operating-side evidence. Requires an active Bidda subscription: pass api_key."
      },
      {
        "name": "gap_check",
        "description": "Given the compliance rules a team says it covers, return the prerequisite rules Bidda's dependency graph links to them that were NOT listed - the 'you missed the prerequisite obligation' gaps - plus any covered rule the registry marks withdrawn. A coverage aid for a qualified reviewer; it does not rank or determine compliance. Requires an active Bidda subscription: pass api_key."
      },
      {
        "name": "obligation_deltas",
        "description": "The obligation-level change feed: primary sources whose content changed (or whose node was withdrawn), mapped to the Bidda obligation nodes they affect, filterable by time, pillar, or specific nodes. Use it to answer 'what obligations changed since I last reviewed?'. Requires an active Bidda subscription: pass api_key."
      },
      {
        "name": "oscal_assessment_results",
        "description": "Export a governed run's evidence as a NIST OSCAL assessment-results document (the machine-readable format GRC and audit tooling consumes): reviewed-controls (the obligation nodes consulted), observations (each pinned to its version + integrity hash), and props recording the independent integrity self-check. A sealed run is readable by id; a still-open run needs your api_key."
      }
    ],
    "profiled_at": "2026-09-25T06:01:44.504Z"
  },
  "unreachable": false,
  "payment_method": "x402"
}