LARP check · Robinhood Chain
$FIDES
$FIDES
Robinhood Chain5 claims read from its site (read with a sandboxed browser). We could not find a contract, a working app or recent code of its own that backs it.
Read 13 h ago · mcap at check — · now — · since check —
What it says, and what we found
- not found“Builds complete agent transaction flows across MCP, x402 and onchain actions, with authorization built into the execution path.” its sitewe could not find a contract, a working app or recent code of its own that backs this
- not found“The Transaction Builder combines compatible calls and payments before execution.” its sitewe could not find a contract, a working app or recent code of its own that backs this
- not found“Execution bundles are simulated before submission.” its sitewe could not find a contract, a working app or recent code of its own that backs this
- not found“The user defines the execution boundary before the agent begins. – Spend budget – Allowed assets – Allowed contracts – Allowed services – Per-action limits – Expiry” its sitewe could not find a contract, a working app or recent code of its own that backs this
- not found“Live on Robinhood Chain mainnet. The contracts are deployed, the packages are on npm under @fidesbuild” its sitea working part answering does not show this; we could not check it
The claims are their own words, quoted by Claude Haiku 5.5; Claude Sonnet 5.5 checked each result against our evidence; every check of them is our own read, and chain facts come from the chain.
Working parts we tested
- no answerAPI: no address of its API we tried answered with data (fidesbuilder.xyz/api/health, fidesbuilder.xyz/api/stats, fidesbuilder.xyz/api/status)
- no answerMCP: no MCP server answered at fidesbuilder.xyz/mcp, fidesbuilder.xyz/api/mcp
- no answerx402: fidesbuilder.xyz/.well-known/x402, fidesbuilder.xyz/x402 did not answer as x402
- factX account @fidesbuilder: exists (an account is not working tech; it backs no claim)
- readThe page we read: fidesbuilder.xyz/ (declared at launch)
Holders of 1M $TOLL can re-read this now. Get $TOLL
Claude Sonnet 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.