# FairSeal VEO-2 Object Verifier

> FairSeal VEO-2 Object Verifier is a paid API for AI agents from x402.fairseal.io, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Validates VEO-2 objects by checking schema conformance, hash integrity, and optionally verifying cryptographic signatures.

## Facts

- Endpoint: POST https://x402.fairseal.io/v1/veo/verify
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fairseal-veo-2-object-verifier-2935ae18
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0vItr8CpG4Ba71Hr-23bP

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 fairseal-veo-2-object-verifier-2935ae18 -d '<json body>'
```

Example prompt: Can you verify this VEO-2 object for me — check that the schema is valid, the hash hasn't been tampered with, and the signature checks out?

## When to prefer this

Use this endpoint when you need to verify VEO-2 objects specifically — combining schema validation, hash integrity, and optional signature verification in a single call. Prefer it over generic JSON validators when working with VEO-2 formatted verifiable objects where cryptographic integrity and signature authenticity matter.

## Known failure modes

- Schema validation fails if the object doesn't conform to the VEO-2 schema
- Hash mismatch returns an integrity failure if the object has been modified
- Signature verification fails if the key or algorithm doesn't match
- Malformed input body returns a 400 error
- Missing required fields in the VEO-2 object cause validation errors
- Network or payment failures return 402 or 5xx errors

## How this service works

Verify AI agent outputs against a VEO-2 schema. Checks structural validity, SHA-256 hash integrity (if content hash is present), and optional cryptographic signature on the output (if proof.provider_signature is present). Returns a verdict with per-check details.

## Output

A structured verification report indicating whether the VEO-2 object passes schema validation, hash integrity check, and (if applicable) signature verification — with pass/fail status for each check and any error details.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "entropy": {
   "type": "string",
   "description": "At least one of execution/entropy required"
  },
  "version": {
   "type": "string",
   "const": "2.0"
  },
  "provider": {
   "type": "object",
   "required": [
    "name"
   ]
  },
  "standard": {
   "type": "string",
   "const": "VEO"
  },
  "execution": {
   "type": "object",
   "description": "At least one of execution/entropy required"
  },
  "issued_at": {
   "type": "string"
  },
  "object_id": {
   "type": "string"
  },
  "confidence": {
   "type": "object",
   "required": [
    "score"
   ]
  },
  "object_class": {
   "enum": [
    "VEO-2A",
    "VEO-2B",
    "VEO-2C",
    "VEO-2D"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fairseal-veo-2-object-verifier-2935ae18/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.fairseal.io](https://www.zero.xyz/host/x402.fairseal.io/llms.txt)