# Verity Suite Concord — Policy Compliance Checker

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

Evaluates a text against a given policy, spec, or contract and returns a calibrated compliance verdict with per-clause reasoning and an optional signed receipt.

## Facts

- Endpoint: POST https://suite.veritylayer.dev/concord
- Price: $0.06/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-policy-compliance-checker-f3835eac
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1pMmY5Jcen3xB6VorxLUR

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

Example prompt: Check whether the following AI-generated response is compliant with our data privacy policy — the policy text is 'Users must not be identified by name, location, or device ID in any output. All PII must be redacted before disclosure.' and the response to evaluate is 'The user John Smith in New York accessed the system from iPhone 14.' Focus the check on PII and disclosure clauses.

## When to prefer this

Use this endpoint when you need a calibrated, auditable compliance verdict against a specific policy or contract text — especially in agentic pipelines where outputs must be verified before delivery, or when a signed proof of compliance is required for logging or audit trails. Prefer this over generic LLM prompting for compliance when you need structured verdicts, per-clause reasoning, and a cryptographic receipt rather than a free-form assessment.

## Known failure modes

- Policy or text fields missing — returns validation error
- Text or policy exceeds 2000 character limit — rejected at schema validation
- Ambiguous or vague policy with no clause structure may yield 'uncertain' verdict
- Signing not configured — receipt field returns null
- Network or service error — fail-closed behavior means no partial result is returned

## 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, per-clause reasoning that ties the verdict to both the policy text and the evaluated text, and an optional Ed25519-signed VerityLayer receipt for auditability. The receipt can be independently verified via a separate 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-policy-compliance-checker-f3835eac/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)
