# Verdicts Freshness Deep Check

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

Performs a deep attestation verdict on whether a given citation/claim and its source URL is still current and factually fresh.

## Facts

- Endpoint: POST https://verdictmcp.com/verdict/freshness/deep
- Price: $0.04/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-deep-check-61e17e67
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BpTvzBdGKJ23SYhgPpr8T

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-deep-check-61e17e67 -d '<json body>'
```

Example prompt: Can you do a deep freshness check on this claim — 'The Eiffel Tower is 330 meters tall' — and verify it against https://en.wikipedia.org/wiki/Eiffel_Tower to see if the citation is still current?

## When to prefer this

Choose this endpoint when you need a deep, paid-attestation freshness check on a specific claim-URL pair — not just a link-alive ping. Prefer over generic link checkers when you need a structured verdict and reproduction class score, especially in agentic pipelines requiring traceable citation validation. Use when citation accuracy and recency matter more than speed or cost.

## Known failure modes

- Source URL is unreachable or returns non-200 — verdict may be indeterminate
- Claim is too vague or ambiguous for comparison against source content
- Source URL has paywalled or bot-blocked content preventing deep access
- Payment of $0.04 USDC via x402 not completed — request rejected with 402
- Malformed input schema (missing claim or source_url) returns validation error

## 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 ('freshness'), verdict (e.g. 'current' or 'stale'), and reproduction_class (integer indicating how reproducible/verifiable the claim is against the source). Indicates whether the claim is still supported by the source URL at time of check.

## 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-deep-check-61e17e67/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)