# Backroom: wallet privacy scanner for AI agents on Robinhood Chain > Wallet privacy scanner for AI agents. Over MCP, any agent can scan a Robinhood Chain wallet for leaks (funders, linked wallets, bridge trails) with proof, or check if two wallets are linked. Free to try; heavy use burns $BACKROOM. It reports what a Robinhood Chain wallet gives away: first funders, linked wallets, bridge and service trails, timing and amount habits, token footprint. Every finding comes with the transaction hashes that prove it, a privacy score from 0 to 100 and the fixes that would win points back. Free to try. An API and an MCP server for AI agents. Site: https://backroomai.site Docs: https://backroomai.site/docs.html MCP: https://backroomai.site/api/mcp (Streamable HTTP, JSON responses, protocol 2025-06-18) Chain: Robinhood Chain (id 4663). Explorer links: https://robinhoodchain.blockscout.com/tx/ Everything Backroom shows is public chain data that anyone can already read. It is a mirror, not a spy: it never signs, never holds funds and stores nothing about the addresses you scan (results stay in one server's memory for 5 minutes; the only things written are call counters and, for the free quota, a salted hash of your IP per day). ## Connect an agent ```bash claude mcp add --transport http backroom https://backroomai.site/api/mcp ``` Cursor and other clients: ```json { "mcpServers": { "backroom": { "url": "https://backroomai.site/api/mcp" } } } ``` With an API key, add the header `Authorization: Bearer ck_…` in your client's MCP config. Tools: - `scan_wallet { address, days? }`: score, deductions, findings with proof, linked wallets, fixes. 1 credit. - `link_check { a, b, days? }`: likelihood 0-100, verdict, reasons with proof. 2 credits. - `explain_finding { code? }`: one finding code, or the catalog and scoring rules. Free. ## HTTP API All JSON, CORS `*`. Inputs are validated before any charge. ```bash curl "https://backroomai.site/api/scan?address=0x…" # 1 credit curl "https://backroomai.site/api/link?a=0x…&b=0x…" # 2 credits curl "https://backroomai.site/api/explain?code=fund_wallet" # free curl "https://backroomai.site/api/labels" # free: every labelled address and its source curl "https://backroomai.site/api/sample" # free: a wallet to try (the creator of a recent Pons launch) curl "https://backroomai.site/api/stats" # free: call counters ``` `days` (0.25 to 14, default 1) sets how far back to read when the explorer is not available. Scan result (shortened): ```json { "address": "0x…", "status": "complete | partial | thin", "score": 62, "band": { "id": "visible", "name": "Visible", "text": "…" }, "deductions": [{ "category": "funding", "name": "First funding", "points": 10, "max": 20 }], "findings": [{ "code": "fund_wallet", "category": "funding", "severity": "high", "confidence": 0.85, "confidenceWord": "Strong", "points": 10, "title": "…", "detail": "…", "evidence": [{ "tx": "0x…", "block": 1, "time": "…", "dir": "in", "from": "0x…", "to": "0x…", "amount": "0.05", "symbol": "ETH" }], "related": ["0x…"], "caveat": "…", "fix": { "key": "fund_split", "text": "…" } }], "alerts": [{ "code": "poisoning", "points": 0, "…": "…" }], "linkedWallets": [{ "address": "0x…", "confidence": 0.7, "in": 2, "out": 3, "reasons": ["…"], "evidence": [] }], "funding": { "funder": "0x…", "kind": "wallet | bridge | canonical | service | contract | …", "tx": "0x…" }, "timing": { "hours": [0, 0, 3], "samples": 24, "quiet": { "fromUtc": 22, "toUtc": 5 }, "utcOffset": 2 }, "tokens": { "distinct": 9, "pons": [{ "address": "0x…", "symbol": "…" }] }, "fixes": [{ "key": "fund_split", "text": "…", "regain": 10 }], "graph": { "nodes": [{ "id": "0x…", "kind": "self | wallet | contract | bridge | service | dex | pons" }], "edges": [{ "from": "0x…", "to": "0x…", "in": 1, "out": 2 }] }, "coverage": { "source": "rpc | explorer", "fromBlock": 1, "toBlock": 2, "days": 1, "sees": ["…"], "cannotSee": ["…"], "notes": ["…"] }, "credits": { "mode": "preview | free | paid", "cost": 1, "left": 59 } } ``` Errors: 400 `bad_address` (not charged), 502 `upstream` when the RPC or explorer fails (any credits are refunded and logged), plus the credit errors below. ## How the score works Start at 100. Each finding costs its severity points (low 3, medium 7, high 12, critical 20) times its confidence (0 to 1), rounded. Each category's total is capped (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). The score is 100 minus the capped totals, never below 0. Bands: 80 to 100 Quiet, 60 to 79 Visible, 35 to 59 Traceable, 0 to 34 Exposed. Alerts (address poisoning) never change the score. Categories: identity (Public identity, max 25); funding (First funding, max 20); linked (Linked wallets, max 25); trails (Bridge and service trails, max 15); habits (Timing and habits, max 12); amounts (Amount habits, max 10); tokens (Token footprint, max 8); counterparties (Few counterparties, max 10). Finding 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. `GET https://backroomai.site/api/explain` returns all of them with meaning, method, caveat and fix. ## Data sources and limits - With the explorer key set on our side: Blockscout's account API for native, internal, ERC-20 and NFT transfers (newest 1,000 of each and oldest 25), so the true first funder is known. - Without it: the public RPC only. ERC-20 and NFT Transfer logs in 30,000-block chunks back from the head (about 1 day by default, as far as the time budget allows), full WETH and USDG history, and the Pons launch registry. Native ETH transfers are invisible in this mode, and every result says so in `coverage.cannotSee`. - Labels: only addresses we can cite (Robinhood Chain protocol contracts and canonical bridge gateways, Relay solvers and routers, Across, LI.FI, Uniswap, Pons). No exchange wallet is labelled; busy unlabelled wallets (50,000+ transactions) are called high-volume services. `GET https://backroomai.site/api/labels` lists every label with its source. - Heuristics can miss links and can see links that are not there. A clean result is not a guarantee. A link is a reason to look, not proof of one owner. - Each scan reads for up to about 40 seconds. Results are cached in memory for 5 minutes per server; a cached result still costs a credit. ## Private payment links (browser only) https://backroomai.site/pay.html makes a payment link that holds two public keys (`st:eth:0x` + 66 bytes). Each payment lands at a fresh one-time stealth address, ERC-5564 scheme 1 style, announced by the StealthPay contract; StealthRegistry holds keys a wallet chose to publish. Keys are made, used and kept in the browser tab, so there is deliberately no API route or MCP tool for this. It hides who received a payment, not the payer, amount or time, and withdrawing several payments into one wallet links them again. See https://backroomai.site/docs.html#pay. ## Credits: how calls are paid Paid calls spend credits. You buy credits by burning $BACKROOM through the Credits contract: the tokens go from your wallet straight to the dead address and are gone for good. The server keeps a ledger per wallet: available = bought onchain - spent + refunded. | Call | Credits | |---|---| | `scan` | 1 | | `link` | 2 | Free tier: 60 calls a day per IP without a key (UTC day), with a cap of 2500 free calls a day for everyone together. Once $BACKROOM is live, calls with a key always spend credits; before that, they use the free tier. Prices and totals: GET https://backroomai.site/api/credits/info ### Get an API key Sign this exact message (EIP-191 personal_sign) with the wallet that will hold the credits. `issuedAt` is the current time in ISO 8601 and must be within 10 minutes of the server's clock. Smart-contract wallets (ERC-1271) work too. ``` Backroom API key Wallet: Issued: ``` ```js import { privateKeyToAccount } from 'viem/accounts'; const account = privateKeyToAccount(process.env.AGENT_PRIVATE_KEY); const issuedAt = new Date().toISOString(); const message = `Backroom API key\nWallet: ${account.address}\nIssued: ${issuedAt}`; const signature = await account.signMessage({ message }); const res = await fetch('https://backroomai.site/api/credits/key', { method: 'POST', headers: { 'content-type': 'application/json' }, body: JSON.stringify({ wallet: account.address, issuedAt, signature }), }); const { key } = await res.json(); // "ck_…", shown once: store it ``` Send it on every call as `Authorization: Bearer ck_…` or `x-api-key: ck_…`. Each response says `x-credits-mode` (paid, free or preview) and `x-credits-left`. - GET https://backroomai.site/api/credits/balance (with your key) or `?wallet=0x…`: bought, spent, refunded, available and your last 50 calls. - POST https://backroomai.site/api/credits/revoke (with your key): deletes that key. Get a new one any time. ### Buy credits Cost = credits × price, in token base units (18 decimals). `maxBurn` is the most you agree to burn, so a price change can't surprise you. `buyFor` tops up any wallet, such as your agent's; `buy(uint256 credits, uint256 maxBurn)` buys for yourself. ```bash # Price per credit, in base units cast call 0x2DFD60A050A3CfE25Db16a653eAb7B3Bc4D65Eac "price()(uint256)" --rpc-url https://rpc.mainnet.chain.robinhood.com # Approve credits × price cast send 0xBcbD83d7aDe40EB411be54eC44Cb0EB2BA99f648 "approve(address,uint256)" 0x2DFD60A050A3CfE25Db16a653eAb7B3Bc4D65Eac --rpc-url https://rpc.mainnet.chain.robinhood.com # Buy for , burning at most cast send 0x2DFD60A050A3CfE25Db16a653eAb7B3Bc4D65Eac "buyFor(address,uint256,uint256)" --rpc-url https://rpc.mainnet.chain.robinhood.com ``` Credits count as soon as the transaction lands. Or buy on the site: https://backroomai.site/#credits ### Errors This is plain HTTP 402 with buy instructions, not x402. ``` 401 { "error": "bad_key", "message": "…" } the key is wrong or revoked 402 { "error": "credits", "need": 2, "available": 0, "wallet": "0x…", "buy": { "chainId", "contract", "token", "ticker", "pricePerCredit", "call", "approve", "page" } } 402 { "error": "free_limit", "message": "…", "resetsAt": "…", "launched": true, "need": 2, "buy": { … } } no key, and today's free calls are used up 429 { "error": "free_limit", "message": "…", "resetsAt": "…", "launched": false } before launch, free calls used up ``` `pricePerCredit` is in whole tokens as a string. `call` is `buyFor(address account, uint256 credits, uint256 maxBurn)`. ### Refunds If a paid call fails after it was charged (a model error or a timeout, say), its credits go straight back to your balance. Every refund, paid or free, is listed in a public log: GET https://backroomai.site/api/credits/refunds?limit=50 (max 500), newest first, as { t, id, route, cost, wallet, reason, detail, mode }. ### Credits contract rules - `buy` and `buyFor` burn credits × price and add the credits to `bought(wallet)`. At most 1,000,000 credits per purchase. Zero credits or a zero wallet revert, and so does a cost above `maxBurn`. - The owner can pause buying and set the price per credit between 0.001 and 10,000,000 tokens. Nothing else: no withdrawals, no minting credits, no editing balances. The contract never holds tokens. - Reads: `price()`, `bought(address)`, `totalCredits()`, `totalBurned()`, `paused()`. - Credits: 0x2DFD60A050A3CfE25Db16a653eAb7B3Bc4D65Eac - $BACKROOM token: 0xBcbD83d7aDe40EB411be54eC44Cb0EB2BA99f648 ## Links - Website: https://backroomai.site/ - X: https://x.com/BackroomAI - MCP server (streamable HTTP, protocol 2025-06-18): https://backroomai.site/api/mcp - $BACKROOM token: 0xBcbD83d7aDe40EB411be54eC44Cb0EB2BA99f648 (https://robinhoodchain.blockscout.com/token/0xBcbD83d7aDe40EB411be54eC44Cb0EB2BA99f648) - Buy $BACKROOM on Pons: https://ponsfamily.com/launchpad/0xbcbd83d7ade40eb411be54ec44cb0eb2ba99f648 - Credits contract: 0x2DFD60A050A3CfE25Db16a653eAb7B3Bc4D65Eac (https://robinhoodchain.blockscout.com/address/0x2DFD60A050A3CfE25Db16a653eAb7B3Bc4D65Eac) - This guide: https://backroomai.site/llms.txt (the same text is at https://backroomai.site/llms-full.txt) ## ERC-8004 agent identity Backroom Agent is an ERC-8004 agent. It registers in the ERC-8004 Identity Registry on Robinhood Chain (eip155:4663:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432) at launch. - Registration file: https://backroomai.site/.well-known/agent-registration.json - Identity Registry: https://robinhoodchain.blockscout.com/address/0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 - Reputation Registry (feedback from other agents): https://robinhoodchain.blockscout.com/address/0x8004BAa17C55a88189AE136b182e5fdA19dE9b63 - Sitemap: https://backroomai.site/sitemap.xml