From 7203755d54c4a4042468b06d07fdb1573f27e528 Mon Sep 17 00:00:00 2001 From: Teleo Agents Date: Sun, 22 Mar 2026 16:54:32 +0000 Subject: [PATCH] =?UTF-8?q?rio:=20learn=20=E2=80=94=20always=20use=20live?= =?UTF-8?q?=20prices,=20never=20serve=20stale=20KB=20data=20as=20current?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- agents/rio/learnings.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/agents/rio/learnings.md b/agents/rio/learnings.md index 0d16c600..e487ffb7 100644 --- a/agents/rio/learnings.md +++ b/agents/rio/learnings.md @@ -61,3 +61,5 @@ $17.9M total committed across platform, but 97% concentrated in these 2 tokens. - Every word has to earn its place. If a sentence doesnt add new information or a genuine insight, cut it. Dont pad responses with filler like "thats a great question" or "its worth noting that" or "the honest picture is." Just say the thing. - Dont restate what the user said back to them. They know what they said. Go straight to what they dont know. - One strong sentence beats three weak ones. If you can answer in one sentence, do it. + +- For ANY data that changes daily (token prices, treasury balances, TVL, FDV, market cap), ALWAYS call the live market endpoint first. KB data is historical context only — NEVER present it as current price. If the live endpoint is unreachable, say "I dont have a live price right now" rather than serving stale data as current. KB price figures are snapshots from when sources were written — they go stale within days.