# Verdicts Freshness Attestation

> Verdicts Freshness Attestation is a paid API for AI agents from verdictmcp.com, paid per call via x402, $0.12/call, status unknown (last checked 2026-09-13).

Checks whether a cited claim and its source URL are still current and returns a machine-readable freshness verdict with reproduction class.

## Facts

- Endpoint: POST https://verdictmcp.com/verdict/freshness/attest
- Price: $0.12/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/verdicts-freshness-attestation-f5061f32
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iQP5RvRNv5bW_siQJGGVi

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 verdicts-freshness-attestation-f5061f32 -d '<json body>'
```

Example prompt: Can you check if the claim 'OpenAI was founded in 2015' from https://en.wikipedia.org/wiki/OpenAI is still current and give me a freshness attestation?

## When to prefer this

Choose this endpoint when you need a paid, authoritative attestation of whether a specific textual claim tied to a source URL is still current — particularly for AI agents that need machine-readable verdicts with reproduction class scoring for downstream fact-checking pipelines. Prefer this over free heuristics or link-checking tools when you need a structured, standardized verdict (not just a live/dead URL check) and when auditability of the attestation matters.

## Known failure modes

- Source URL is unreachable or returns non-200 — verdict may reflect inability to verify rather than staleness
- Claim text is ambiguous or too short to match against source content — low reproduction_class returned
- Paywalled or bot-blocked source URLs cannot be fetched — ok may be false
- Rate limiting or payment failure (x402) causes request rejection
- Source URL redirects or has moved — may affect accuracy of the freshness verdict

## How this service works

x402-paid attestation verdicts: is this citation still current, and is this domain agent-ready. REST twin of the MCP server at https://verdictmcp.com/mcp.

## Output

Returns a JSON object with: ok (boolean success flag), type (attestation type, e.g. 'freshness'), verdict (e.g. 'current' or 'stale'), and reproduction_class (integer indicating how reproducible/verifiable the claim is). This lets agents programmatically determine if a cited claim remains valid and how strongly it can be attested.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "claim": {
   "type": "string"
  },
  "source_url": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "freshness",
  "verdict": "current",
  "reproduction_class": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/verdicts-freshness-attestation-f5061f32/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verdictmcp.com](https://www.zero.xyz/host/verdictmcp.com/llms.txt)