# capi2 Claim Verify

> capi2 Claim Verify is a paid API for AI agents from capi2-claim-verify.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Verifies vendor, product, security, or compliance claims against supplied public evidence URLs and returns a structured verdict with confidence score.

## Facts

- Endpoint: POST https://capi2-claim-verify.onrender.com/v1/vendor-security-check
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/capi2-claim-verify-32828f78
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GX-m3PYN714u2ypaj1Tb3

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 capi2-claim-verify-32828f78 -d '<json body>'
```

Example prompt: Can you verify the claim 'Acme Corp encrypts all customer data at rest and in transit' using their security page at https://acmecorp.com/security as evidence?

## When to prefer this

Choose this endpoint when you need agent-native, evidence-backed verification of a specific textual claim against one or more public URLs — particularly for vendor security, compliance, or commercial due diligence scenarios. It is purpose-built for AI agent workflows, returns structured machine-readable verdicts with confidence scores, and charges only $0.01 USDC per call via x402 micropayments, making it cost-effective for high-volume automated checks. Prefer this over generic web scraping when you need a normalized verdict and evidence citations rather than raw page content.

## Known failure modes

- Supplied URLs are inaccessible or return non-200 responses — source_results will show failed status
- Claim text is too short (under 3 characters) or too long (over 1200 characters) — returns 400 validation error
- Evidence found on the page is ambiguous or contradicts the claim — verdict may be NOT_SUPPORTED or UNCERTAIN
- Payment not settled via x402 micropayment — returns 402 Payment Required
- Rate limiting or server unavailability on Render.com — returns 5xx error
- Source URL content is behind a login wall and cannot be fetched — evidence will be empty

## How this service works

Agent-native evidence-backed claim verification with x402 micropayments on Base USDC.

## Output

Returns a JSON object containing a verdict label (e.g. SUPPORTED_BY_SUPPLIED_SOURCE, NOT_SUPPORTED), a numeric confidence score (0–1), an array of evidence excerpts with individual scores and source URLs, an evidence summary, caveats about the check's scope, the number of sources checked, a request ID, protocol version, and the timestamp of the check.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "claim": {
   "type": "string",
   "maxLength": 1200,
   "minLength": 3,
   "description": "Vendor, product, compliance, security, or commercial claim to verify."
  },
  "claim_id": {
   "type": "string",
   "maxLength": 200
  },
  "vendor_url": {
   "type": "string",
   "format": "uri",
   "description": "Public source URL containing evidence relevant to the claim."
  },
  "source_urls": {
   "type": "array",
   "items": {
    "type": "string",
    "format": "uri"
   },
   "maxItems": 3,
   "minItems": 1,
   "description": "Optional list of up to three public evidence URLs. These are checked together; vendor_url remains supported for backward compatibility.",
   "uniqueItems": true
  },
  "vendor_name": {
   "type": "string",
   "maxLength": 200
  },
  "request_type": {
   "type": "string",
   "maxLength": 120
  },
  "verification_type": {
   "type": "string",
   "maxLength": 120
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "claim": "Vendor states that customer data is encrypted at rest.",
  "caveats": [
   "Checks only the supplied public URL."
  ],
  "verdict": "SUPPORTED_BY_SUPPLIED_SOURCE",
  "evidence": [
   {
    "text": "Customer data is encrypted at rest.",
    "score": 0.9,
    "source_url": "https://example.com/security"
   }
  ],
  "protocol": "capi2.claim_verify/1.6.1",
  "checked_at": "2026-08-26T15:00:00Z",
  "confidence": 0.88,
  "request_id": "cv_018f5f8f0c2b4f7a",
  "vendor_url": "https://example.com/security",
  "source_results": [
   {
    "status": "checked",
    "final_url": "https://example.com/security",
    "requested_url": "https://example.com/security"
   }
  ],
  "sources_checked": 1,
  "evidence_summary": "Customer data is encrypted at rest.",
  "verification_result": "supported",
  "verification_status": "supported",
  "evidence_source_urls": [
   "https://example.com/security"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/capi2-claim-verify-32828f78/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from capi2-claim-verify.onrender.com](https://www.zero.xyz/host/capi2-claim-verify.onrender.com/llms.txt)