CueCruxVaultCrux

Watch Quickstart

Watches let you register a query and receive alerts when the corpus answer drifts. This is useful for monitoring policy documents, regulatory content, or any corpus where changes should trigger re-evaluation.

Requires Pro.

Required environment variables

  • VAULTCRUX_API_URL
  • VAULTCRUX_API_KEY
  • VAULTCRUX_TENANT_ID

1) Create a watch

Via MCP:

curl -sS "$VAULTCRUX_API_URL/rpc" \
  -H "content-type: application/json" \
  -H "x-tenant-id: $VAULTCRUX_TENANT_ID" \
  -H "x-api-key: $VAULTCRUX_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "id": "watch-1",
    "method": "watch_answer",
    "params": {
      "agent_id": "agent-1",
      "query": "What is the current data retention period?",
      "label": "retention-policy-watch"
    }
  }'

Returns a watch_id. The initial answer snapshot is recorded at creation time.

2) List active watches

curl -sS "$VAULTCRUX_API_URL/v1/watches" \
  -H "x-tenant-id: $VAULTCRUX_TENANT_ID" \
  -H "x-api-key: $VAULTCRUX_API_KEY"

Returns all active watches for the tenant, including creation timestamps and last-evaluated answer hashes.

3) Read watch alerts

curl -sS "$VAULTCRUX_API_URL/v1/watches/$WATCH_ID/alerts" \
  -H "x-tenant-id: $VAULTCRUX_TENANT_ID" \
  -H "x-api-key: $VAULTCRUX_API_KEY"

Each alert includes the timestamp of the drift event, the prior answer hash, the new answer hash, and the changed evidence references.

4) Unwatch

curl -sS -X DELETE "$VAULTCRUX_API_URL/v1/watches/$WATCH_ID" \
  -H "x-tenant-id: $VAULTCRUX_TENANT_ID" \
  -H "x-api-key: $VAULTCRUX_API_KEY"

Stops evaluation for this watch. Existing alerts are preserved.

Drift detection behavior

  • The watch evaluates the registered query against the current corpus on each corpus update cycle.
  • A drift event is emitted when the answer hash changes relative to the prior evaluation.
  • Answer hash is computed over the ranked evidence set, not the generated text, so vector-level corpus changes trigger alerts before downstream LLM output changes.