Is this going up or down?
onchain_agent_get_trendANSWERS ONE QUESTION: is this measurement going up or down? Returns a bounded series (at most 30 points, default 8) for ONE venue, ONE chain and ONE stage from Sato Hub's own weekly (or daily) chain reads — each point with its date, value, sample_size and method.
Pass stage (required). Venue is optional: name it to read exactly one series; omit it and a stage that only one venue reports is read from that venue, while a stage several venues report comes back as one SEPARATE series per venue. Stages by venue: erc8004 reports registered (weekly), registered_new_1d (daily), active_7d, mcp_endpoint_answers; olas reports registered and working; virtuals reports launched; virtuals_acp reports jobs_created; x402 reports settled_to_catalogued_seller, answers_402 (weekly) and facilitator_txs_1d_known (daily). A stage name alone is enough when one venue reports it; when several do (registered is reported by more than one venue) you get one separate series per venue.
RULE ENFORCED: points are never summed across venues, chains or stages — the tool refuses to blend chains and tells you which chains exist when you omit one, and several venues are never combined. A null point is UNKNOWN for that period, never zero. The weekly point is the citable one; daily points feed a trend and never a headline. Raw rows are not returned.
Returns (json): { venue, chain, stage, grain, unit, points: [{ date, value, sample_size, method, evidence_tier }], direction_first_to_last, known_points, rules, as_of, source } — or, when a stage several venues report is asked without a venue, { stage, grain, series: [that same object per venue], needs_chain?, no_reading?, rules }. Read-only.
Examples:
"are ERC-8004 registrations on Base growing" -> { venue: "erc8004", chain: "Base", stage: "registered" }
"how is registered trending on Base" (no venue) -> { stage: "registered", chain: "Base" }
"x402 sellers week over week" -> { venue: "x402", chain: "Base", stage: "settled_to_catalogued_seller", points: 12 }
"do registered endpoints answer, day by day" -> { venue: "erc8004", chain: "Base", stage: "mcp_endpoint_answers", grain: "daily", points: 30 }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | 'stage' (default) is one venue/chain/stage series. 'movers' is the week's Sato Score movement across the directory — which listings rose, fell, crossed a tier, were scored for the first time, or answered our daily checks differently. In movers mode venue, chain and stage are ignored. | stage |
| chain | No | Chain, e.g. Base, Ethereum, Gnosis. Required when a venue's stage is measured on more than one chain — series are never blended across chains. Omit for venue-level rows. | |
| grain | No | 'weekly' (the citable series, default) or 'daily' (the trend grain; never a headline). | weekly |
| stage | No | Lifecycle stage. REQUIRED in 'stage' mode. By venue: erc8004 = registered, registered_new_1d (daily), active_7d, mcp_endpoint_answers; olas = registered, working; virtuals = launched; virtuals_acp = jobs_created; x402 = settled_to_catalogued_seller, answers_402, facilitator_txs_1d_known (daily). | |
| venue | No | Venue id: erc8004, olas, virtuals, virtuals_acp, x402, erc4337_accounts. Optional: when omitted, a stage that one venue reports is read from that venue, and a stage several venues report (registered) returns one separate series per venue. Pass it to read exactly one. See onchain_agent_get_agent_economy for the catalogue. | |
| points | No | How many most-recent points (1-30, default 8). | |
| response_format | No | Text format; structuredContent is JSON either way. | markdown |