If you're building an agent on Robinhood Chain, you don't need to parse our UI
GET https://t.co/mAm9PUYiwl...?chain=4663
→ verdict
→ scores.liquidity / concentration / reliability
→ freshness.state
→ sources[] behind every field
No key. CORS open. 60 req/min. Returns null, never zero
Up to four assets through the same pipeline
Liquidity, 24h volume, top holder %, impact at $1k / $10k, pool age, price confidence, freshness, scores, verdict
Rows aligned. Best and worst highlighted. Every cell keeps its source
https://t.co/wyqmUyJtj9
INITIALIZING DOOMWARE
$DOOM is live on Robinhood Chain
Read the machine state. Six verdicts, every formula printed next to the number, nothing predicted, nothing mocked
CA:
0x01e65691ce44b5b61d25de90bd95fc3489ef58c8
A missing value on DoomWare prints DATA SOURCE UNAVAILABLE
Not zero. Not an estimate. Not a placeholder
Nulls mean "not observable from the configured sources at this block" and the verdict excludes them
Nothing is mocked in production paths
Every number on DoomWare ships with its formula and the substituted inputs printed next to it
Liquidity score =
60 × min(1, log10(1 + liqUsd) / 6)
+ 25 × (1 − impact$1k / 5%)
+ 15 × (1 − impact$10k / 10%)
If you can't audit the math, it isn't intelligence. It's a vibe
Six words. Ordered rules. First match wins. Reasons attached
UNKNOWN → no live pool or no USD reference
CONCENTRATED → top holder ≥ 30% or top-10 ≥ 80%
UNSTABLE → confidence < 0.5 or price disagreement > 15%
THIN → liquidity < $50k or $1k impact > 1%
LIQUID → ≥ $250k and $10k impact ≤ 1%
HEALTHY → otherwise
That's the whole verdict engine
Read the machine state
DoomWare turns fragmented on-chain data contract state, liquidity, pools, holders, transaction context into structured, machine-readable intelligence
RAW STATE → NORMALIZATION → ANALYSIS → VERDICT → OUTPUT