LARP check · Solana
$LOCO
$LOCO
Solana4 claims read from its site. Two different working parts of it answered our own reads: its API at studioloco.cfd/api/public/loco/v1/openapi.json answered with data (fields openapi, info, servers, paths); its public code at jjyaz/studio-loco was last changed 3 days ago.
Read 10 h ago · mcap at check $34.5k · now $29.9k · since check −13.3%
What it says, and what we found
- found“Studio Loco An independent interface for Meteora DLMM on Solana, with an educational coordination lab.” its siteits API at studioloco.cfd/api/public/loco/v1/openapi.json answered with data (fields openapi, info, servers, paths); its public code at jjyaz/studio-loco was last changed 3 days ago
- found“Trades and liquidity go directly to Meteora s onchain program from your wallet.” its siteits API at studioloco.cfd/api/public/loco/v1/openapi.json answered with data (fields openapi, info, servers, paths); its public code at jjyaz/studio-loco was last changed 3 days ago
- not found“Never. There is no custodial backend. Your wallet signs every transaction after we simulate it.” its sitea working part answering does not show this; we could not check it
- found“Every number in the terminal comes from Meteora s public API or your RPC.” its siteits API at studioloco.cfd/api/public/loco/v1/openapi.json answered with data (fields openapi, info, servers, paths); its public code at jjyaz/studio-loco was last changed 3 days ago
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 studioloco.cfd/api/public/loco/v1/openapi.json answered with data (fields openapi, info, servers, paths) · studioloco.cfd/api/public/loco/v1/openapi.json
- no answerMCP: no MCP server answered at studioloco.cfd/mcp, studioloco.cfd/api/mcp
- answeredPublic code: its public code at jjyaz/studio-loco was last changed 3 days ago · github.com/jjyaz/studio-loco
- factX account @StudioLocoDBC: exists (an account is not working tech; it backs no claim)
- readThe page we read: studioloco.cfd/ (declared at launch and listed on DexScreener)
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.