# Delx Data Freshness

> Delx Data Freshness is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-16).

Evaluates whether a given data age meets a caller-supplied maximum freshness requirement, returning a deterministic pass/fail assessment

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/data-freshness
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-data-freshness-adf14cb4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_B5O7eybm-qIwbUy07_rDK

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 delx-data-freshness-adf14cb4 -d '<json body>'
```

Example prompt: Check if data that's 4500 seconds old is still fresh enough given a max allowed age of 3600 seconds.

## When to prefer this

Choose this endpoint when you need a deterministic, stateless, machine-readable freshness evaluation as a lightweight preflight step in an automated workflow — especially before data, policy, security, or commercial decisions. It is ideal when you need a clear pass/fail signal based on a caller-defined age threshold rather than building custom comparison logic. Prefer it over custom code when operating inside an agent pipeline where auditability and low latency matter.

## Known failure modes

- Missing required field age_seconds returns an error response
- Missing required field max_age_seconds returns an error response
- Non-numeric values for age_seconds or max_age_seconds cause validation errors
- Negative age values may produce undefined or error results
- Payment failure via x402 prevents execution

## How this service works

Evaluate data age against a caller-supplied freshness objective. Use it as a bounded preflight or analysis step inside an enterprise agent workflow before data, policy, integration, security, or commercial decisions reach production. Returns deterministic machine-readable JSON for $0.003 USDC via x402 on Base or Solana. Execution is first-party, local-only, stateless, memory-only, and has no paid upstream or input retention. Results are advisory; the caller remains responsible for authorization…

## Output

Returns deterministic machine-readable JSON indicating whether the input data age (age_seconds) meets the specified maximum freshness threshold (max_age_seconds), including pass/fail status and relevant computed values for downstream decision-making.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "age_seconds": {
   "type": "number",
   "description": "Input field: age_seconds."
  },
  "max_age_seconds": {
   "type": "number",
   "description": "Input field: max_age_seconds."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "fresh": true,
  "schema": "delx/util-data-freshness/v1",
  "age_seconds": 300,
  "max_age_seconds": 900,
  "overdue_seconds": 0,
  "freshness_percent": 66.6667
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-data-freshness-adf14cb4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)