# Live Data Freshness

> Live Data Freshness is a paid API for AI agents from phion.systems, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-02).

Tests whether source observations meet an explicit maximum-age policy, validating that data is fresh enough to be trusted

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/live-data-freshness?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/live-data-freshness-5cf6dc4d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ifAjHQQFivp9DAsjrMEei

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 live-data-freshness-5cf6dc4d -d '<json body>'
```

Example prompt: Before I use this sensor reading, check if it meets a maximum age policy of 5 minutes — here's the observation with its timestamp, and reject it if it's stale.

## When to prefer this

Choose this endpoint when you need a lightweight, policy-enforced freshness check on individual source observations before acting on them — especially in agentic pipelines where stale data could cause incorrect decisions. Prefer this over manual timestamp comparisons when you need a signed, auditable freshness result or when enforcing an explicit declared maximum-age policy rather than an ad-hoc recency heuristic.

## Known failure modes

- Missing or unparseable timestamp on the observation leads to inability to compute age
- Maximum-age policy value not provided or ambiguously formatted causes policy enforcement failure
- Network latency introduces small timing uncertainty near the age threshold
- Clock skew between source and validator may cause borderline observations to fail incorrectly
- Malformed input schema results in a 400-level error with no freshness verdict

## How this service works

Test whether source observations meet an explicit maximum-age policy

## Output

Returns a pass/fail freshness verdict indicating whether the source observation satisfies the declared maximum-age policy, along with the observed data age and any policy violation details such as how much the age limit was exceeded.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "example"
   ],
   "properties": {
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/live-data-freshness-5cf6dc4d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phion.systems](https://www.zero.xyz/host/phion.systems/llms.txt)