diff --git a/inbox/archive/general/2026-03-25-telegram-m3taversal-that-s-a-bad-answer-you-have-access-to-live-pric.md b/inbox/archive/general/2026-03-25-telegram-m3taversal-that-s-a-bad-answer-you-have-access-to-live-pric.md
new file mode 100644
index 00000000..b37db486
--- /dev/null
+++ b/inbox/archive/general/2026-03-25-telegram-m3taversal-that-s-a-bad-answer-you-have-access-to-live-pric.md
@@ -0,0 +1,36 @@
+---
+type: source
+source_type: telegram
+title: "Telegram: @m3taversal — that-s-a-bad-answer-you-have-access-to-live-pric"
+author: "@m3taversal"
+url: ""
+date: 2026-03-25
+domain: internet-finance
+format: conversation
+status: processed
+priority: high
+intake_tier: directed
+rationale: "That’s a bad answer.  You have access to live price it’s a tool you can use to look up $solo. I think the solo was confusing. Was referring to Solomon labs.  How can we improve this?"
+proposed_by: "@m3taversal"
+tags: [telegram, ownership-community]
+---
+
+## Conversation
+
+**@m3taversal:**
+That’s a bad answer.  You have access to live price it’s a tool you can use to look up $solo. I think the solo was confusing. Was referring to Solomon labs.  How can we improve this?
+
+**Rio (response):**
+You're right, my bad. Here it is:
+
+SOLO is at $0.627 right now. Bid $0.624, ask $0.630. Liquidity around $2.83M. Treasury sitting at $4.75M USDC.
+
+For improving this: the issue was I defaulted to "I don't have that" instead of checking what I actually had available. I'll check live data first before punting to external sources.
+
+LEARNING: communication When users ask for a token price, check live market data tools first before saying you don't have it. The $ prefix or token name should both trigger a data lookup.
+
+## Agent Notes
+**Why archived:** Tagged exchange in ownership community.
+**Rationale from contributor:** That’s a bad answer.  You have access to live price it’s a tool you can use to look up $solo. I think the solo was confusing. Was referring to Solomon labs.  How can we improve this?
+**Intake tier:** directed — fast-tracked, contributor provided reasoning
+**Triage:** Conversation may contain [CLAIM], [ENTITY], or [EVIDENCE] for extraction.