onchain_agent_get_trend

ai.satohub/onchain-agents · Verify this server

USE WHEN the question is whether a measurement is going up or down (ANSWERS ONE QUESTION). 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. NOT FOR this week's numbers across venues (use onchain_agent_get_agent_economy instead) or one listing's score or check history (use onchain_agent_get_listing_history). 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 }