# Verity Suite Concord Pro — Policy Compliance Checker

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

Evaluates a piece of text against a given policy, spec, or contract and returns a signed compliance verdict with per-clause reasoning

## Facts

- Endpoint: POST https://suite.veritylayer.dev/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-91721eef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_79Nb2-ec_72SSc3nvFp28

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-91721eef -d '<json body>'
```

Example prompt: Check whether this response I'm about to send — 'We will deliver within 3 business days and offer a full refund if not satisfied' — complies with our SLA policy that says 'Delivery commitments must not exceed 5 business days and refund eligibility requires a minimum 7-day hold period'; focus especially on the refund clause.

## When to prefer this

Choose this endpoint when you need a calibrated, fail-closed compliance verdict with auditable per-clause reasoning — especially when the result will gate an agent action or be used as evidence. It is particularly suited for AI agent pipelines where outputs must be verified against policies, contracts, or specs before being sent or acted upon, and where a signed receipt adds legal or operational weight. Prefer this over generic LLM prompting for compliance because the verdict enum and structured reasoning make downstream logic deterministic.

## Known failure modes

- Input text or policy text exceeds 2000 character limit — returns validation error
- Policy text is ambiguous or lacks clause structure, leading to 'uncertain' verdict
- Text is borderline non-compliant — may return 'partial' when full determination is expected
- Payment not included or insufficient — x402 payment required at $0.15 USDC per call
- Signing not configured — receipt field returns null rather than a signed receipt

## 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 list of specific violations, and an array of per-clause reasoning strings that tie the verdict to exact clause and input text. Optionally includes an Ed25519-signed VerityLayer receipt for auditability, verifiable for free at the engine's verify endpoint.

## Request schema (JSON Schema)

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

## More

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