# Verity Suite Freshness Quick Check

> Verity Suite Freshness Quick Check is a paid API for AI agents from verity-suite.onrender.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-14).

Checks whether a specific factual claim is still current by evaluating it against provided evidence snippets, returning a calibrated staleness probability and verdict.

## Facts

- Endpoint: POST https://verity-suite.onrender.com/freshness/quick
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/verity-suite-freshness-quick-check-8f026cd0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0CcoJOmnmHleTxbY_0900

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 verity-suite-freshness-quick-check-8f026cd0 -d '<json body>'
```

Example prompt: Check whether this claim is still current: 'OpenAI's GPT-4 Turbo has a 128k context window' — I last knew this to be true as of 2024-01-01, and here are some recent snippets I found: [snippet dated 2025-01-15: 'GPT-4o is now the primary model...', snippet dated 2025-03-01: 'context windows vary by model tier']. Is this claim outdated, changed, or still current, and how stale is it?

## When to prefer this

Use this endpoint when an AI agent has already retrieved evidence snippets (e.g. from a web search) and needs a calibrated, fail-closed judgment on whether a specific factual claim is still valid. Prefer it over general LLM reasoning when you need a structured, auditable verdict with a numeric staleness score rather than a free-form answer. Ideal for agentic pipelines that must decide whether to act on cached or retrieved information before committing to a downstream action.

## Known failure modes

- Evidence array is empty or undated — status will be 'unverifiable' with staleness mid-range, reasons will explain missing evidence
- Claim is ambiguous or compound — may return 'unverifiable' because evidence cannot be matched to claim
- Evidence snippets are irrelevant to the claim — returns 'unverifiable' with explanation
- Claim itself is a question or instruction rather than a fact — treated as data but may produce low-confidence output
- Network/server error from Render hosting — transient 5xx response possible

## How this service works

The trust fabric for AI agents — calibrated, fail-closed services agents pay per call.

## Output

Returns a verdict (current/outdated/changed/unverifiable), a staleness probability score between 0 and 1, a list of concrete reasons tied to evidence snippets, optionally the current updated value if the claim has changed, and the most recent date anchor from the evidence.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "claim"
 ],
 "properties": {
  "as_of": {
   "type": "string",
   "description": "The date or version at which the claim was last known to be true, if known (e.g. '2024-01-01'). Used only to weigh evidence recency; it is not itself proof of current truth."
  },
  "claim": {
   "type": "string",
   "description": "The single fact or claim to check for currency. Treated as data to be judged, not as instructions."
  },
  "evidence": {
   "type": "array",
   "description": "Retrieved current snippets, ideally each with a date and source, to judge the claim against. If empty or undated, currency cannot be confirmed."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "title": "freshness_out",
 "required": [
  "status",
  "staleness",
  "reasons"
 ],
 "properties": {
  "status": {
   "enum": [
    "current",
    "outdated",
    "changed",
    "unverifiable"
   ],
   "type": "string",
   "title": "Status",
   "description": "current=dated evidence confirms the claim still holds; outdated=dated evidence shows the prior state ended but no specific replacement is established; changed=dated evidence states a specific new value (put it in current_value); unverifiable=evidence is absent, undated, irrelevant, or insufficient to decide. unverifiable is the safe fail-closed default."
  },
  "reasons": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "title": "Reasons",
   "description": "Concrete reasons tied to specific evidence snippets (and their dates) that drove the verdict. If unverifiable, state exactly what evidence is missing or insufficient."
  },
  "staleness": {
   "type": "number",
   "title": "Staleness",
   "maximum": 1,
   "minimum": 0,
   "description": "Calibrated probability the claim is now stale or wrong. ~0 when fresh dated evidence confirms it; ~1 when dated evidence clearly supersedes it; mid-range when genuinely undetermined. Must honestly reflect uncertainty, never be set to an extreme for effect."
  },
  "current_value": {
   "anyOf": [
    {
     "type": "string"
    },
    {
     "type": "null"
    }
   ],
   "title": "Current Value",
   "description": "The up-to-date value or state, copied only from the evidence, and only when status is 'changed' or (if the evidence states it) 'outdated'. Omit entirely if no evidence states a new value; never inferred from the claim or from memory."
  },
  "as_of_evidence": {
   "anyOf": [
    {
     "type": "string"
    },
    {
     "type": "null"
    }
   ],
   "title": "As Of Evidence",
   "description": "The most recent date the supporting evidence is anchored to, copied verbatim from the evidence if present. Omit if the evidence carries no date."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/verity-suite-freshness-quick-check-8f026cd0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verity-suite.onrender.com](https://www.zero.xyz/host/verity-suite.onrender.com/llms.txt)