# C2PA Content Credentials Provenance Verifier

> C2PA Content Credentials Provenance Verifier is a paid API for AI agents from payai.agentstools.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-12).

Verifies the cryptographic C2PA provenance manifest embedded in a media file, returning a verdict (authentic-provenance, untrusted-signer, tampered, or unsigned) plus distilled signed claims including signer, creator tool, generative-AI flag, edit actions, and ingredient graph.

## Facts

- Endpoint: POST https://payai.agentstools.dev/provenance/verify?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/c2pa-content-credentials-provenance-verifier-236665f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_26R5-ESN-CDm4AvuWknT0

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 c2pa-content-credentials-provenance-verifier-236665f2 -d '<json body>'
```

Example prompt: Can you verify the C2PA content credentials on this JPEG image I'm uploading — I need to know if its provenance is authentic-provenance, who signed it, whether it was AI-generated, and what edits were recorded in the manifest?

## When to prefer this

Choose this endpoint when you need cryptographic verification of C2PA / Content Credentials embedded in media files — particularly when you need a trust-list-verified verdict and structured provenance claims (signer, AI-generation flag, edit history). Prefer this over general-purpose deepfake detectors when the media file may already carry a C2PA manifest and you need to know whether that manifest is authentic and intact. It is not a perceptual or AI-detection tool — it only reads and validates cryptographically signed embedded provenance data.

## Known failure modes

- Media file too large or unsupported format — returns error with supported format list
- Base64 encoding is malformed or truncated — returns parse error
- File contains no embedded C2PA manifest — verdict returned as 'unsigned' with no claims
- Signer certificate not on production or Interim Trust List — verdict returned as 'untrusted-signer'
- Asset hash does not match embedded manifest hash — verdict returned as 'tampered'
- Network timeout if file is very large
- Invalid MIME type provided — returns validation error

## How this service works

Cryptographic C2PA / Content-Credentials verdict for a media file. Parses the embedded manifest, verifies the signature chain and asset hash-binding against the C2PA production + Interim trust lists, and returns a go/no-go verdict (authentic-provenance, untrusted-signer, tampered, unsigned) with the distilled signed claims. Cryptographic provenance, not a deepfake detector.

## Output

Returns a go/no-go verdict string (authentic-provenance, untrusted-signer, tampered, or unsigned) plus distilled signed claims extracted from the verified C2PA manifest: the signer identity, creator tool name, a boolean generative-AI source flag, list of recorded edit actions, and the ingredient/provenance graph showing the asset's history.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "media": {
   "type": "string",
   "description": "The media file bytes, base64-encoded (image, video, audio or PDF). A data: URI prefix is tolerated."
  },
  "format": {
   "type": "string",
   "description": "Media MIME type or file extension, e.g. image/jpeg, png, mp4, pdf (see GET /provenance/sources for the full list)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/c2pa-content-credentials-provenance-verifier-236665f2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from payai.agentstools.dev](https://www.zero.xyz/host/payai.agentstools.dev/llms.txt)