How fresh is the data behind each answer
onchain_agent_get_data_freshnessUSE WHEN you are about to quote a Sato Hub number, score, count or feed item and want to know how old it is — or when a figure looks stale and you need to know whether the pipeline behind it is late. Returns, per data surface (directory activity, news, Sato Score, liveness checks, snapshots, ERC-8004 counts, the weekly agent-economy measurements, x402, LP pools, skills, deploy verification and more): when it was last collected successfully, when a collection was last attempted and how that ended, how often it is expected to run, whether it is late, the next scheduled run, and the ledger step it was read from.
RULE ENFORCED: late = now − last success > 1.5 × the expected cadence (daily 36h, weekly 252h). A surface built from several pipeline steps is as fresh as its stalest step, and one of its steps never succeeding makes it late. A surface with no recorded success at all returns last_success_at: null and late: null — unknown, never an invented date. If the ledger cannot be read, every surface is unknown, never "fresh". A late surface still serves its last good data: quote it WITH its date.
Returns (json): { generated_at, ledger, rule, surfaces: [{ surface, what, expected_every, last_success_at, last_attempt_at, last_status, late, state, age_hours, late_after_hours, next_update, source, steps: [{ step, last_success_at, last_attempt_at, last_status }], served_by }], note, source_url, sato_url }. Timestamps and statuses of data jobs only — no usage figures. Read-only.
Example: { surface: "sato_score" }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| surface | No | One data surface to check. Omit for all of them. Surfaces: directory_activity, news, erc8004_count, agent_tokens, liveness, sato_score, snapshots, x402_bazaar, x402_answers_daily, erc8004_endpoints_daily, mcp_alive_daily, erc8004_router_pool, passports, erc8004_census, x402_throughput, erc8004_agents_celo, custody_profiles, sato_scan, sato_scan_census, agent_economy, x402_settlement, lp_pools, skills, deploy_verification, custody_observed, dead_project_sweep. | |
| response_format | No | Text format; structuredContent is JSON either way. | markdown |