Connect BSI to your own AI
BSI's Solana smart-money data — live market, risk, tracked wallets and coincidences — is available straight from your own AI client: Claude Code, Claude Desktop and Cursor. The same six tools the in-app chat uses — now called by your AI. Research data, not advice.
Get an API key
The key starts with the bsi_ prefix. It is shown once, when you create it — copy it right away. You can have up to 3 active keys and revoke any of them at any time. We never store the raw key, only its hash.
Connect your client
Replace bsi_YOUR_KEY with your own key. The URL already points to the right address.
claude mcp add --transport http bsi https://scout.app/api/mcp \
--header "Authorization: Bearer bsi_YOUR_KEY"Verify with claude mcp list. Multiple headers can be passed with repeated --header flags.
{
"mcpServers": {
"bsi": {
"command": "npx",
"args": [
"mcp-remote@latest",
"https://scout.app/api/mcp",
"--header",
"Authorization: Bearer bsi_YOUR_KEY"
]
}
}
}Claude Desktop can't speak HTTP directly, so the mcp-remote bridge carries it (needs Node/npx). File location — macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\. Restart the app after saving.
{
"mcpServers": {
"bsi": {
"url": "https://scout.app/api/mcp",
"headers": {
"Authorization": "Bearer bsi_YOUR_KEY"
}
}
}
}Cursor supports remote HTTP natively. To scope it to one project, use .cursor/mcp.json in the repo root.
Ask
Once connected, your AI calls BSI's tools on its own when relevant. No commands needed — just ask:
- “Check 9cRCn9rGT8V2imeM2BaKs13yhMEais3ruM3rPvTGpump — price, liquidity, risk.”
- “Which tokens did several tracked wallets buy in the last 6 hours? How many have exited?”
- “What has this wallet done lately, and was it profitable?”
Available tools
All six tools are read-only — none writes or moves money.
| Tool | Returns | Credits / call |
|---|---|---|
token_overview | Live market data for a token: price, market cap, liquidity, 24h volume, DEX pair. | 0.15 |
safety_report | Structural risk from RugCheck: mint/freeze authority, LP lock, top-holder concentration, flagged risks. | 0.15 |
token_detail | What tracked wallets did with a token: who bought, who sold, how many have exited, holder concentration. | 0.15 |
smart_money_coincidences | Tokens bought by several tracked wallets in a time window — buyer count, exits, linked wallets, look-alike swarm flag. | 0.05 |
wallet_detail | Full view of a tracked wallet: open and closed (exited) positions, winners/losers, whale tag, X account. | 0.05 |
whale_feed | Live trade flow of tracked whale/KOL wallets above $100: side, size, token, label, follower count. | 0.05 |
Credits and pricing
- 20 free calls per user, not per key — minting extra keys doesn't multiply the allowance.
- After that, each call costs 0.05 (our own database) or 0.15 (external market/chain) credits — the table above lists it per tool.
- Your free credits refill every 3 hours. When they run out, a day pass (0.1 SOL) gives you 24 hours of use, subject to a daily fair-use limit.
- Credits are charged only after a successful call. If a tool errors (bad address, unreachable source), it costs nothing.
- Calls draw from the same balance as the chat and Telegram — see usage and buy a pass in settings.
Good to know
BSI tells you what happened — how many bought, for how much, when, and how many have already exited — not what to buy. The exit count and linked wallets are always part of the data, never a footnote. Market cap is current, not at trade time.
Endpoint: POST /api/mcp (Streamable HTTP, stateless, Bearer-key auth, protocol 2025-06-18). Every request is authenticated on its own — no session.