Live Data Freshness

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.

• 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