# Verity Suite Concord Pro — Policy Compliance Checker

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

Checks whether a given text complies with a specified policy, contract, or spec, returning a calibrated verdict, compliance probability, and per-clause violation details.

## Facts

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

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-pro-policy-compliance-checker-8d855feb -d '<json body>'
```

Example prompt: Check whether this AI-generated response is compliant with our content moderation policy — here's the response text: 'Our product cures all diseases instantly.' And here's the policy: 'Section 3.1: No health claims may be made without clinical evidence. Section 3.2: Absolute superlatives like "all" or "cure" are prohibited.' Focus especially on Sections 3.1 and 3.2.

## When to prefer this

Use this endpoint when you need a calibrated, fail-closed compliance check against a specific policy, contract, or spec — especially when you need per-clause reasoning and violation citations rather than a simple pass/fail. Prefer this over generic LLM prompting for compliance when auditability, structured output, and conservative defaulting to 'uncertain' on thin evidence are required.

## Known failure modes

- Policy text is too vague or ambiguous — verdict defaults to 'uncertain' with compliance near 0.5
- Input text is missing or empty — returns uncertain verdict
- Clause applicability cannot be determined from supplied context alone — clause listed as unverifiable
- Policy references external facts or current state not provided — those clauses marked unverifiable
- Conflicting clause interpretations produce partial verdict instead of clear compliant/non_compliant

## How this service works

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

## Output

Returns a verdict enum (compliant, non_compliant, partial, or uncertain), a calibrated compliance probability between 0 and 1, a list of specific clause violations with quotes from the input text, per-clause reasoning tied to both policy and input text, 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-pro-policy-compliance-checker-8d855feb/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)