Fidacy
See it in action

Continuous control monitoring

Show where the control boundary is live.

Control Coverage turns raw connector and executor signals into an explicit view of what Fidacy can prove now, what it proved in the past and where the evidence stops.

Coverage states

StateMeaning
GATEDA one-time signed grant was redeemed by a Fidacy executor. This is historic hard-gate proof, not an assertion that the executor remains connected now.
OBSERVEDAn authenticated connector sent a current heartbeat. Its latest submitted session is complete when one is present.
LIMITEDThe connector is current, but its latest submitted session is truncated and cannot prove a complete trail.
NO_CURRENT_EVIDENCENo recent authenticated heartbeat exists. Historical records remain available, but do not prove a current boundary.

Send an authenticated connector signal

POST/v1/control-coverage/signals

The signal is tenant-authenticated, separate from anonymous product telemetry, and deliberately accepts only a closed host vocabulary. It contains boundary metadata, never a free-form action payload.

curl -s https://api.fidacy.com/v1/control-coverage/signals   -H "Authorization: Bearer $FIDACY_ENGINE_API_KEY"   -H "Content-Type: application/json"   -d '{
    "v": "fidacy.control-coverage.v1",
    "machine": "support-ops-eu-01",
    "host": "host_codex",
    "subject": "support-refund-agent",
    "clientVersion": "1.0.0"
  }'
This endpoint requires an account-owned connector and one ofassess:write, session:write or artifact:write. It returns the current heartbeat window so the connector can report again before its liveness becomes stale.

Read coverage and reconciliation

GET/v1/control-coverage

The response includes controls and reconciliation totals: decisions, signed receipts, receipt artifacts, redeemed grants, unreedeemed grants and detected coverage gaps. It also reports outside_boundary_actions: NOT_OBSERVABLE rather than pretending to see actions that bypass every connected control.

{
  "controls": [{
    "state": "GATED",
    "enforcement": "HARD_GATE_PROVEN",
    "scope": "Signed grant gate · stripe.refund.create",
    "connection": "UNKNOWN"
  }],
  "reconciliation": {
    "decision_count": 12,
    "signed_receipt_count": 12,
    "decisions_without_receipt_artifact": 0,
    "grants_redeemed": 4,
    "coverage_gap_count": 0,
    "outside_boundary_actions": { "status": "NOT_OBSERVABLE" }
  }
}

Export a Control Coverage Report

GET/v1/control-coverage/report

A report is a signed period control object for an auditor, insurer or customer. It includes the monitored scope, control states, reconciliation, retention disclosure and a JWS that can be checked against Fidacy's public JWKS. It requires audit:read.

  • ·Use an Incident Pack for one decision and its evidence.
  • ·Use a Control Coverage Report for the operational condition of boundaries over the retained reporting period.
  • ·If retained history exceeds the complete report window, narrow the interval before relying on an export as complete evidence.

For third parties

Give an insurer or auditor the signed report and the public JWKS URL, not an unrestricted tenant key. A recipient can verify that the report was signed by Fidacy and see the report's stated scope and disclosures. They should not infer broader coverage than the report claims.

Next →MCP server