# NovaPath Public Records Freshness Auditor

> NovaPath Public Records Freshness Auditor is a paid API for AI agents from instructional-decision-engine-x402.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-31).

Audits event age and snapshot age for up to five public records against a chosen as-of date, flagging stale snapshots and distinguishing source-event recency from observation date.

## Facts

- Endpoint: POST https://instructional-decision-engine-x402.vercel.app/research/freshness?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/novapath-public-records-freshness-auditor-a8f6c80c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Q2DqtqvXX1BWZStoRj0SY

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 novapath-public-records-freshness-auditor-a8f6c80c -d '<json body>'
```

Example prompt: Can you audit the freshness of these five public records — REC:001, REC:002, REC:003, REC:004, REC:005 — as of 2025-01-15, and flag any that are older than 180 days?

## When to prefer this

Choose this endpoint when you need to audit the recency of existing public record snapshots against a specific historical or current as-of date, and want a clear distinction between when the source event occurred versus when the snapshot was captured. It is ideal for compliance checks, data quality pipelines, or pre-decision freshness validation where you must not conflate live verification with snapshot observation. It is not suited for fetching new live data or performing real-time lookups.

## Known failure modes

- Invalid date format for asOf (must match ^20[0-9]{2}-[0-9]{2}-[0-9]{2}$) returns a validation error
- Record IDs that do not conform to the allowed pattern are rejected
- Submitting more than 5 record IDs returns a schema validation error
- maximumAgeDays outside the range 1–3650 is rejected
- Unknown or unresolvable record IDs may return no data or a not-found indicator for those records
- Payment failure via x402 protocol results in the request not being processed

## How this service works

Audit event age and snapshot age for up to five public records against a chosen as-of date. Distinguishes source-event recency from the observation date, flags stale snapshots and never reports an unperformed live verification.

## Output

Returns per-record audit results including: the age of the underlying source event, the age of the stored snapshot, a staleness flag if the snapshot exceeds the specified maximumAgeDays threshold, and a clear note that no live verification was performed — only existing snapshot and event metadata is assessed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "asOf": {
   "type": "string",
   "pattern": "^20[0-9]{2}-[0-9]{2}-[0-9]{2}$"
  },
  "recordIds": {
   "type": "array",
   "items": {
    "type": "string",
    "pattern": "^[A-Za-z0-9][A-Za-z0-9:._|+-]{1,119}$"
   },
   "maxItems": 5,
   "minItems": 1,
   "uniqueItems": true
  },
  "maximumAgeDays": {
   "type": "integer",
   "maximum": 3650,
   "minimum": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/novapath-public-records-freshness-auditor-a8f6c80c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from instructional-decision-engine-x402.vercel.app](https://www.zero.xyz/host/instructional-decision-engine-x402.vercel.app/llms.txt)