Docs
Backroom API and MCP
Backroom scans a Robinhood Chain wallet for what it gives away and returns every finding with the transaction hashes that prove it. It is read-only: it never signs, never holds funds, and stores nothing about the addresses you scan. All routes answer JSON, allow CORS from any origin, and accept GET or POST (a JSON body works the same as the query string).
Quickstart
No key, no account. The free tier is 60 calls a day per IP.
curl "https://backroomai.site/api/scan?address=0xec70bbd3456bab889bdfd1b8a8d70096b084c90a"
claude mcp add --transport http backroom https://backroomai.site/api/mcp
A scan takes 10 to 45 seconds: it stops on time and says what it could not read. Results are cached in memory for 5 minutes, so a repeat is instant ("cached": true).
GET/api/scan
The full privacy scan. 1 credit.
| Parameter | Meaning |
|---|---|
address | Required. The wallet: 0x and 40 hex characters. A bad address is a 400 and is never charged. |
days | Optional, 0.25 to 14, default 1. How far back to read blocks when the explorer is not available (RPC mode). The answer says how far it actually got. |
curl "https://backroomai.site/api/scan?address=0x…&days=2" -H "Authorization: Bearer ck_…" # key optional
Response (a real scan of a Pons creator, shortened where marked):
{
"address": "0xbbabd3f035290a1f246591869f8d062193505467",
"engine": "backroom-1.0",
"scannedAt": "2026-11-15T17:56:49.147Z",
"cached": false,
"status": "thin", // complete | partial | thin
"score": 89,
"band": { "id": "quiet", "name": "Quiet", "text": "Little in what we read ties this wallet to anything else." },
"deductions": [ { "category": "identity", "name": "Public identity", "max": 25, "points": 11 }, … 8 categories ],
"findings": [ {
"code": "pons_creator", "category": "identity", "severity": "high",
"confidence": 0.95, "confidenceWord": "Strong", "points": 11,
"title": "This wallet launched Pons tokens",
"detail": "The Pons registry lists this wallet as the creator of 1 launch: 0x9de9…7561.",
"evidence": [ { "tx": "0x12df1ba0…a5850de", "block": 115130758, "note": "TokenLaunched for 0x9de9…7561", "time": null } ],
"related": [ "0x9de938fe13556ed64d56ba7d288a431aac287561" ],
"caveat": "Launching is public by design. This only matters if you want the wallet kept apart from the project.",
"fix": { "key": "fresh_launch", "text": "Launch from a fresh wallet used for nothing else, funded over a bridge rather than from your main wallet." }
} ],
"alerts": [], // address-poisoning lookalikes; never change the score
"linkedWallets": [], // { address, confidence, confidenceWord, in, out, reasons[], evidence[], sharedFunder }
"funding": { "funder": "0x…", "kind": "wallet", "label": null, "provider": null, "firstEver": false, "tx": "0x…", "proof": { … }, "txType": null },
"timing": { "hours": [24 counts by UTC hour], "samples": 0, "quiet": null, "utcOffset": null },
"tokens": { "distinct": 1, "pons": [], "list": [ { "address": "0x…", "symbol": "", "nft": false, "pons": false, "label": null } ] },
"fixes": [ { "key": "fresh_launch", "text": "Launch from a fresh wallet…", "regain": 11, "findings": ["pons_creator"] } ],
"graph": { "nodes": [ { "id": "0x…", "kind": "self", "label": "This wallet" }, … ], "edges": [ { "from": "0x…", "to": "0x…", "in": 1, "out": 0, "tx": "0x…" } ] },
"wallet": { "type": "eoa", "delegate": null, "nonce": 2, "balance": "0.00682208", "agents": 0 },
"counts": { "transfers": 2, "in": 1, "out": 1, "counterparties": 1, "sentTxsRead": 0 },
"coverage": {
"source": "rpc", "explorer": false, "fromBlock": 114780969, "toBlock": 115140968,
"fromTime": "2026-11-15T07:08:53.000Z", "toTime": "2026-11-15T17:56:08.000Z", "days": 0.45, "askedDays": 1,
"sees": [ "ERC-20 and NFT transfers in the scanned blocks", "full WETH and USDG history", "Pons launches this wallet created" ],
"cannotSee": [ "native ETH transfers (they leave no logs; set BLOCKSCOUT_API_KEY to read them)", … ],
"notes": [ "Read 12 of 27 chunks of 30,000 blocks: blocks 114,780,969 to 115,140,968, about 0.45 days.", … ],
"requests": 72, "ms": 39715
},
"explorer": "https://robinhoodchain.blockscout.com",
"limits": "Heuristics can miss links and can see links that are not there. A clean result is not a guarantee. …",
"credits": { "mode": "preview", "cost": 1, "left": 59, "id": "GxNSx2KwZDU" }
}GET/api/link
Are two wallets linked, and how? Scans both in parallel and compares them. 2 credits. Parameters: a, b (required), days (0.25 to 7, default 1).
curl "https://backroomai.site/api/link?a=0x…&b=0x…"
{
"a": "0x…", "b": "0x…", "engine": "backroom-1.0", "checkedAt": "2026-11-15T18:02:11.000Z",
"likelihood": 90, // 0-100: 1 - product of (1 - confidence) over the reasons
"verdict": "Likely linked", // Likely linked | Possibly linked | Weak signs only | No link found in what we read
"reasons": [
{ "code": "direct", "confidence": 0.9, "text": "They transferred to each other directly (3 transfers in what we read).", "evidence": [ { "tx": "0x…", … } ] }
], // codes: direct, funded, same_funder, shared_wallets, shared_launches, same_hours
"scores": { "a": 54, "b": 71 },
"coverage": { "a": { … }, "b": { … } },
"limits": "A link is a reason to look, not proof of one owner. No link found means none in what we read, not that none exists.",
"credits": { "mode": "free", "cost": 2, "left": 57, "id": "…" }
}GET/api/explain
What a finding code means, how it is detected, what it does not prove, and its fix. Free, reads no chain data. Omit code for the whole catalog plus the scoring rules.
curl "https://backroomai.site/api/explain?code=fund_wallet"
{ "code": "fund_wallet", "category": { "id": "funding", … }, "severity": "high", "points": 12, "title": "…", "means": "…", "how": "…", "caveat": "…", "fix": { "key": "fund_split", "text": "…" } }Codes: pons_creator, erc8004_agent, fund_canonical, fund_bridge, fund_service, fund_wallet, fund_contract, funder_reuse, linked_wallet, bridge_trail, canonical_withdraw, service_wallet, deposit_address, timezone, schedule, fixed_gas, delegated, round_amounts, reused_amounts, pass_through, token_footprint, airdrop_spam, few_counterparties, poisoning.
Other routes
| Route | What it returns | Cost |
|---|---|---|
GET /api/labels | Every address Backroom labels (canonical bridge, Relay, Across, LI.FI, Uniswap, Pons, WETH, ERC-8004), each with its source link. { labels: [{ address, name, kind, provider, source }], exchanges: [], note } | Free |
GET /api/sample | A wallet to try: the creator of a recent Pons launch. { address, token, tx, why } | Free |
GET /api/stats | Call counters, numbers only. { today: { scan, link, … }, total: { … }, day } | Free |
GET /api/credits/info | Launch state, Credits contract, token, price per credit, costs, free tier. | Free |
POST /api/credits/key | Get an API key by signing a message with the wallet that bought credits. | Free |
GET /api/credits/balance | Credits bought, spent, refunded and available for a key or wallet. | Free |
GET /api/credits/refunds | The public refund log. | Free |
GET /llms.txt | The agent guide: routes, result shape, scoring, credits. | Free |
MCP server
Endpoint https://backroomai.site/api/mcp: Streamable HTTP in its simple form (JSON responses, no sessions, no streaming), protocol 2025-06-18 (also accepts 2025-03-26 and 2024-11-05). Methods: initialize, notifications/initialized, tools/list, tools/call, ping.
claude mcp add --transport http backroom https://backroomai.site/api/mcp # with a key: claude mcp add --transport http backroom https://backroomai.site/api/mcp --header "Authorization: Bearer ck_…"
{ "mcpServers": { "backroom": { "url": "https://backroomai.site/api/mcp", "headers": { "Authorization": "Bearer ck_…" } } } }| Tool | Input | Returns | Cost |
|---|---|---|---|
scan_wallet | { address, days? } | A text summary plus the full scan result in structuredContent. | 1 credit |
link_check | { a, b, days? } | Verdict, likelihood and reasons with proof. | 2 credits |
explain_finding | { code? } | One finding code, or the catalog and scoring rules. | Free |
curl -s https://backroomai.site/api/mcp -H "content-type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"explain_finding","arguments":{"code":"timezone"}}}'A bad address or an exhausted quota comes back as a tool result with "isError": true and a plain message, so the agent can read it. Unknown methods are JSON-RPC error -32601.
Result shape
- findings: sorted by points. Each has
code,category,severity(low, medium, high, critical),confidence(0 to 1) and its word (Strong, Likely, Possible, Weak),points,detail,evidence(up to 6 transfers or transactions, each withtx),relatedaddresses,caveat(what it does not prove) andfix. - linkedWallets: wallets that may share an owner, with the reasons and the transfers behind them. Contracts, labelled services and wallets with 50,000+ transactions are never called linked.
- fixes: each fix with
regain, the exact points the score would win back if every finding it covers went away. - graph: this wallet and its 14 most telling counterparties. Node kinds: self, wallet, contract, bridge, service, dex, pons, unknown.
- coverage: the data source, the blocks and times read, what it saw, what it could not see, and notes. Read this before trusting a clean result.
Scoring
Start at 100. Each finding costs its severity points (low 3, medium 7, high 12, critical 20) times its confidence, rounded. Each category's total is capped, and the score is 100 minus the capped totals, never below 0.
| Category | Cap |
|---|---|
| Public identity | 25 |
| First funding | 20 |
| Linked wallets | 25 |
| Bridge and service trails | 15 |
| Timing and habits | 12 |
| Amount habits | 10 |
| Token footprint | 8 |
| Few counterparties | 10 |
Bands: 80 to 100 Quiet, 60 to 79 Visible, 35 to 59 Traceable, 0 to 34 Exposed. Alerts (address-poisoning lookalikes) never change the score.
Data sources and limits
- Explorer mode (when the operator has set a Blockscout API key): native, internal, ERC-20 and NFT transfers from Robinhood Chain's Blockscout, newest 1,000 of each kind plus the oldest 25, so the true first funder is known. It also reads the funder's own history (who else it paid), linked wallets' first funders, and whether a wallet you sent to forwards everything to a busy wallet (a deposit address).
- RPC mode (the fallback): ERC-20 and NFT transfer logs from the public RPC in chunks of 30,000 blocks, newest first, for the look-back you ask for (default 1 day), plus the full WETH and USDG history and the Pons launch registry. Native ETH transfers leave no logs, so RPC mode cannot see them, and it says so in
coverage.cannotSee. - Counterparties are classified with
eth_getCodeandeth_getTransactionCount. Labels come only from addresses we can cite (see/api/labels). No exchange hot wallet on Robinhood Chain is labelled yet; unlabelled wallets with 50,000+ transactions are flagged as high-volume services instead. - The scan has a 45-second budget inside the 60-second function limit. When the RPC is busy it reads less, reports exactly what it missed, and skips findings that would need the missing data instead of guessing.
- Heuristics can miss links and can see links that are not there. A clean result is not a guarantee, and a link is a reason to look, not proof of one owner.
Free tier, credits and the token
Every route is free up to 60 calls a day per IP (2,500 a day for everyone together). Above that, send a Credits key. You buy credits by burning $BACKROOM through the shared Credits contract on Robinhood Chain; burned tokens are gone for good, and credits can't be sold back. Then sign a message with the same wallet to get a key on the token section of the home page.
| Call | Credits |
|---|---|
scan, scan_wallet | 1 |
link, link_check | 2 |
explain, labels, sample, stats, explain_finding | Free |
The price per credit is set on the Credits contract and shown by /api/credits/info. That is all the token does here: it pays for heavy use. There is no promise about its price or any return.
Errors
| Status | When | Charged? |
|---|---|---|
| 400 | Bad or missing address, or the same address twice. { error: "bad_address", message } | Never |
| 401 | An API key that does not exist or was revoked. | No |
| 402 | After launch, free quota used and no credits: a plain HTTP 402 with how to buy credits (not x402). | No |
| 429 | Before launch, the free quota for the day is used up. | No |
| 502 | The chain did not answer. The charge is refunded and listed in the public refund log. | Refunded |
Every paid answer carries x-credits-mode, x-credits-left, x-credits-cost and x-call-id headers.
Private payment links
The payment page lets anyone receive ETH or ERC-20 tokens at one-time stealth addresses, in the style of ERC-5564 (announcements) and ERC-6538 (a registry of published keys). Everything below runs in the browser. There is no API route and no MCP tool for it, because the keys must never reach a server.
Keys and links
- Keys come from one wallet signature over a fixed message: spending key = keccak256(first 32 bytes of the signature) mod n, viewing key = keccak256(next 32 bytes) mod n. The same wallet always recreates them. Random keys are also offered; then the downloaded backup is the only copy.
- A link holds both public keys, compressed:
st:eth:0x+ 33 bytes spending key + 33 bytes viewing key. The shareable form ishttps://backroomai.site/pay.html#to=st:eth:0x…. The part after#is never sent to our server. - Publishing on StealthRegistry (
registerKeys(1, keys)) lets payers use your plain 0x address. It reveals only that your wallet accepts private payments.
Paying
- The payer's browser picks a random key r and computes R = r·G, the shared secret S = r·V, h = keccak256(compressed S), and the one-time address from K + h·G. The view tag is the first byte of h.
- ETH:
StealthPay.sendEth(stealth, R, viewTag)forwards the value in the same transaction. Tokens: the payer approves the exact amount, thensendToken(token, stealth, amount, R, viewTag)moves the tokens from the payer to the one-time address and forwards any ETH sent along as a gas tip. - Each payment emits
Announcement(schemeId, stealthAddress, caller, ephemeralPubKey, metadata). Metadata is the view tag, then0xeeeeeeee+ ETH + amount for ETH, or0x23b872dd+ token + amount received + tip for tokens. Fee-on-transfer tokens announce the amount that actually arrived.
Finding and withdrawing
- The page reads every Announcement from StealthPay, skips the ones whose view tag does not match (255 in 256), and checks the rest fully. Only the matches are shown.
- A withdrawal is signed in the tab with the one-time address's own key (spending key + h mod n) and sent with
eth_sendRawTransaction. Tokens move first, then the remaining ETH. Gas is reserved up front and the unused part is refunded to the one-time address, so a tiny amount of ETH dust can stay behind. - A token payment with no gas tip leaves the one-time address without ETH. Funding it from one of your own wallets links the two, which is why the payer is asked for a tip.
Contracts
| Contract | Address | What it does |
|---|---|---|
| StealthPay | 0x84387d294f3967dd17cce769b3e9e0bc584674f7 | Sends ETH or tokens to a one-time address and announces it. Holds nothing between transactions. |
| StealthRegistry | 0xf80fa6a508d7d14a4625c3286442e4c3de6b6126 | Each wallet's published keys. Only the wallet itself can set or clear its entry. |
Both are deployed with CREATE2 through the standard deterministic deployer, so the addresses are fixed by the code. The payment page shows whether they are live yet. Neither has an owner, a fee or an upgrade path. They are new and have not been audited; use small amounts.
Limits
- It hides who received a payment. It does not hide the payer, the amount, the token or the time. An unusual amount right after you shared your link is easy to match.
- Careless withdrawals undo it: sending several one-time addresses into one wallet, or into your main wallet, links them publicly.
- There is no mixing pool, so nothing is hidden among other users' deposits.
- The math follows ERC-5564 scheme 1 closely, but working with other stealth wallets is not promised: they may hash the shared secret differently.
Privacy
- Everything Backroom shows is public chain data that anyone can already read.
- Nothing about the addresses you scan is stored. A result stays in one server's memory for 5 minutes, then it is gone.
- What is written down: call counters per day (no addresses) and, for the free quota, a salted hash of your IP for the current UTC day.
- No accounts, no analytics, no cookies, no ad pixels. The scanner never signs anything and never holds funds. Payment keys exist only in your browser tab.
- Requests to the chain carry the user agent
Backroom/1.0 (+https://backroomai.site).