LARP check · Robinhood Chain
$HRX
$HRX
Robinhood Chain2 claims read from its site. Its API at heurix.xyz/api/agents answered with data (fields agents). One working part of it answered our reads; a second kind would make it found.
Read 12 h ago · mcap at check $29.2k · now $51.4k · since check +76.1% · asked 2×
What it says, and what we found
- not found“Hold 500,000+ $HRX and run up to 3 agents at the same time instead of 1.” its sitea second reader of our reads found they do not back this
- partly“Token Contract: 0xfcc86d9c23ffb9f27258534ea316c096f1af51b9” its siteits API at heurix.xyz/api/agents answered with data (fields agents)
The claims are their own words, quoted by Claude Haiku 5.5; Claude Sonnet 5.5 checked each result against our evidence and Claude Opus 5.5 had the final say; every check of them is our own read, and chain facts come from the chain.
Working parts we tested
- answeredAPI: its API at heurix.xyz/api/agents answered with data (fields agents) · heurix.xyz/api/agents
- no answerMCP: no MCP server answered at heurix.xyz/mcp, heurix.xyz/api/mcp, heurix.xyz/api/mcp
- factX account @HeurixRH: exists (an account is not working tech; it backs no claim)
- readThe page we read: www.heurix.xyz/ (declared at launch)
Holders of 1M $TOLL can re-read this now. Get $TOLL
Claude Opus 5.5 reviewed this read · holders see its notes. Get $TOLL
This dev's other coins we read
None yet: this is the first coin from this dev wallet that we read.
How we read it
We read what the project says in its own words: its website, its code README and its launch post. Each thing it says it offers is listed as a claim. Then we test it ourselves, and only our own reads count: the contracts it names on chain, who calls them and what they actually do; its app; its own API answering with data; its MCP server listing its tools; its x402 payments; its Chrome Web Store listing; its Telegram bot; its public code changed in the last 30 days. An X account that exists is shown as a fact; it never backs a claim.
- product found a contract of theirs is used by wallets other than the team, or two different working parts of theirs answered our reads.
- product partly found one working part of theirs answered, or weaker support (a contract only the team calls, a page of theirs that opens, fresh code).
- product not found we read their words, and nothing we could check backs them.
- product not read we could not read their words (no site or post, a site that did not open, or one that draws itself with scripts).
Facts, not a verdict: a quiet contract can be tech that launched yesterday, and a busy one can still lose you money. Not advice.