# C2PA Content Provenance Verifier

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

Verifies the cryptographic C2PA manifest embedded in a media file, checking signature validity and asset integrity against trust lists, returning a provenance verdict with signed claims.

## Facts

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

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-provenance-verifier-3e4180e9 -d '<json body>'
```

Example prompt: Can you check the C2PA content credentials on this JPEG image for me — base64-encode it and verify whether the signature is from a trusted signer and whether the file has been tampered with since it was signed?

## When to prefer this

Use this endpoint when you need cryptographic verification of C2PA content credentials embedded in a media file — images, video, audio, or PDF. This is the right choice when you need to know if a file was signed by a known trusted publisher, whether it has been modified after signing, and what provenance claims are asserted. It is NOT a deepfake detector or perceptual authenticity analyzer; it only reads and verifies cryptographic manifests. Prefer this over general metadata inspection tools when you need a standards-compliant, trust-list-backed C2PA verdict.

## Known failure modes

- Unsupported media format — MIME type not in supported list returns an error; check GET /provenance/sources
- No C2PA manifest present — returns 'unsigned' verdict
- Malformed base64 input — parsing failure
- Signature chain broken but file otherwise intact — returns 'tampered'
- Signer not on C2PA production or Interim trust list — returns 'untrusted-signer'
- File too large for inline base64 submission

## 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 verdict string (one of: authentic-provenance, untrusted-signer, tampered, unsigned) along with distilled signed claims extracted from the C2PA manifest, including signer identity, timestamp, and any declared actions or assertions embedded in the credential.

## 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-provenance-verifier-3e4180e9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agentstools.dev](https://www.zero.xyz/host/api.agentstools.dev/llms.txt)