# Verity Suite Concord — Policy Compliance Checker

> Verity Suite Concord — Policy Compliance Checker is a paid API for AI agents from verity-suite.onrender.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Evaluates a text or AI-generated output against a provided policy, spec, or contract, returning a calibrated compliance verdict with per-clause reasoning and violation citations.

## Facts

- Endpoint: POST https://verity-suite.onrender.com/concord/quick
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/verity-suite-concord-policy-compliance-checker-d5db2d93
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PiQsq_ts95FnDv2uTpuo6

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability verity-suite-concord-policy-compliance-checker-d5db2d93 -d '<json body>'
```

Example prompt: Check whether this AI-generated refund policy response complies with our customer service contract — the policy says 'Refunds must be issued within 5 business days, no exceptions for digital goods' and the output says 'We typically process refunds in 3-7 business days; digital purchases are non-refundable.' Focus especially on the timeline and digital goods clauses.

## When to prefer this

Choose this endpoint when you need calibrated, clause-level compliance analysis with explicit uncertainty signaling rather than a binary pass/fail. It is especially useful when the policy is long or structured with numbered clauses, when you need to know exactly which clauses were violated and why, or when your agent must fail closed on ambiguous cases. Prefer this over generic LLM prompting when auditability, reproducibility, and calibrated confidence scores matter.

## Known failure modes

- Policy text is too vague or missing → verdict defaults to 'uncertain' with compliance near 0.5
- Input text is empty or unreadable → uncertain verdict returned
- Clauses reference external facts not in the input (e.g. current dates, third-party records) → those clauses appear in unverifiable_clauses
- Policy and text are both present but evidence is thin → compliance score stays near 0.5 per calibration design
- Payment failure (x402) → request rejected before processing

## How this service works

The trust fabric for AI agents — calibrated, fail-closed services agents pay per call.

## Output

Returns a structured object with: a verdict enum (compliant / non_compliant / partial / uncertain), a calibrated compliance probability (0–1), a list of clearly-violated clauses with specific quotes from both policy and input, per-clause reasoning strings explaining each decision, and a list of clauses that could not be verified from the inputs alone.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "text",
  "policy"
 ],
 "properties": {
  "text": {
   "type": "string",
   "description": "the output or text to evaluate for compliance against the policy"
  },
  "scope": {
   "type": "string",
   "description": "optional note on which clauses or aspects matter most, or what 'compliant' means in this context"
  },
  "policy": {
   "type": "string",
   "description": "the policy, spec, or contract text to check against, ideally with clause numbers or headings"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "title": "concord_out",
 "required": [
  "verdict",
  "compliance",
  "violations",
  "reasons"
 ],
 "properties": {
  "reasons": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "title": "Reasons",
   "description": "concrete per-clause reasoning tying the verdict to specific clause text and specific input text, including why uncertain clauses could not be confirmed"
  },
  "verdict": {
   "enum": [
    "compliant",
    "non_compliant",
    "partial",
    "uncertain"
   ],
   "type": "string",
   "title": "Verdict",
   "description": "compliant=every applicable clause is satisfied with clear support in the text; non_compliant=at least one applicable clause is clearly violated and none is left blocking-uncertain; partial=at least one applicable clause is clearly satisfied AND at least one is clearly violated; uncertain=the SAFE DEFAULT: policy or text missing/unreadable, policy too vague to apply, evidence too thin to decide, or an applicable clause cannot be confirmed met"
  },
  "compliance": {
   "type": "number",
   "title": "Compliance",
   "maximum": 1,
   "minimum": 0,
   "description": "calibrated probability the text fully complies with ALL applicable clauses; 1=clearly and fully complies, 0=clearly violates; stay near 0.5 when evidence is thin or the policy is ambiguous"
  },
  "violations": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "title": "Violations",
   "description": "each clearly-violated applicable clause: cite the clause id/text from the POLICY, then quote the specific part of the input text that breaks it; empty list if none found"
  },
  "unverifiable_clauses": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "title": "Unverifiable Clauses",
   "description": "applicable clauses that could not be judged from the inputs alone (missing context, external/current facts not supplied, or wording too ambiguous to apply)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/verity-suite-concord-policy-compliance-checker-d5db2d93/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verity-suite.onrender.com](https://www.zero.xyz/host/verity-suite.onrender.com/llms.txt)