Bloom for Claude

API base URL

Every endpoint below is served from this deployment's own origin — never a hardcoded host:

• MCP (Streamable HTTP): https://www.bloomterminal.io/api/bloom-mcp
• OAuth authorization-server metadata: https://www.bloomterminal.io/.well-known/oauth-authorization-server
• OAuth protected-resource metadata: https://www.bloomterminal.io/.well-known/oauth-protected-resource/api/bloom-mcp
• Authorize: https://www.bloomterminal.io/api/bloom-agents/oauth/authorize
• Token: https://www.bloomterminal.io/api/bloom-agents/oauth/token
• Dynamic client registration: https://www.bloomterminal.io/api/bloom-agents/oauth/register
• Revoke: https://www.bloomterminal.io/api/bloom-agents/oauth/revoke

Add the connector

1. In Claude, open Customize → Connectors → Add custom connector.
2. Name: Bloom
3. URL: https://www.bloomterminal.io/api/bloom-mcp
4. Save, then open a chat and ask Bloom to research a Base asset.

Public research works without an account. To let Claude read your own portfolio or prepare a trade draft, link your Bloom account when prompted — see below.

Linking your Bloom account

1. Ask Claude for something private, for example “show my Bloom portfolio”. Claude starts an OAuth connection.
2. Bloom opens its own consent screen. You sign in to Bloom, see exactly which permissions are requested and which wallet is being linked, and can untick anything you do not want to share.
3. Approve, and Claude receives a short-lived token scoped to only what you approved.
4. Manage or revoke the connection any time at /advisory/connected-apps. Revocation is immediate.

• bloom:research — Public market research: Public Base market data, token metrics, protocol data and risk checks.
• bloom:portfolio:read — Read your Bloom portfolio: Your linked wallet's Base holdings, vault positions and total value.
• bloom:balances:read — Read your wallet balances: ETH and USDC balances for your linked Bloom wallets on Base.
• bloom:trades:history:read — Read your Bloom trade history: Past trades Bloom recorded for your linked wallet, including transaction hashes.
• bloom:trade:prepare — Prepare trade drafts: Live Base quotes, to prepare an unsigned buy or sell draft for your review.

bloom:trade:preparegrants drafting only — it can never sign, submit or execute anything. There is no scope anywhere for signing, submitting, executing, Autopilot activation, live-strategy changes or session keys — those capabilities are denied by Bloom's server regardless of any token or requested scope.

Bloom never sends OAuth tokens, Privy credentials, private keys or seed phrases through the connector, and a wallet address mentioned in a chat is never accepted as proof of ownership.

Buying, selling and swapping through Claude

Ask Claude to “buy $50 of AERO”, “sell 25% of my AERO”, or “swap 0.1 ETH to USDC.” Claude resolves the token, fetches a live executable Base quote through Bloom's existing trading infrastructure, and creates an unsigned, single-use draft bound to your linked account and wallet — it never receives raw transaction data and cannot sign or submit anything.

Claude gives you a Bloom review link (/advisory/trade-review). There you see the exact amounts, expected output, minimum received, slippage, fees, price impact, quote expiry and risk warnings, and you confirm and sign with your own wallet through Privy. Bloom refreshes the quote, re-checks your balance and allowance, and requests an exact token approval — never unlimited. Only after that does anything reach the chain. Claude can then check the transaction status and show you the explorer link, but it never claims success before a confirmed on-chain receipt.

Trade preparation is capped server-side: a conservative maximum trade value, a maximum slippage, and a short draft lifetime. Autopilot activation, session keys and autonomous trading remain completely separate and are never reachable from this connector.

What Claude can do through Bloom

• Research a Base token: identity, verified contract address, metrics, risk flags, evidence
• Compare two to five Base assets side by side
• Show a Base market overview: trending pools and protocol TVL
• Surface Base protocol and yield opportunities with their risk factors
• Assess contract and liquidity risk for a Base token
• Report tokenized-equity reference metadata, clearly labelled as not tradable here
• Read your own linked portfolio, balances and trade history
• Prepare an unsigned buy, sell or token-swap draft with a live Base quote, then hand you a Bloom review link to confirm and sign yourself

What Claude can never do

• Receive or request a private key, seed phrase or Privy credential
• Sign a message or a transaction
• Submit a transaction, broadcast calldata, move funds, or approve a token
• Set an unlimited token approval
• Execute a trade — it can only prepare an unsigned draft for your review
• Read another Bloom user's portfolio, balances or trade history
• Accept a wallet address you type in chat as proof of ownership
• Activate Autopilot, change a live strategy, or use a session key
• Turn on a Bloom server feature flag
• Claim a transaction succeeded before Bloom confirms an on-chain receipt

These are enforced on Bloom's server by a deny-by-default capability guard, not by prompt instructions. No tool that signs, submits or executes exists in the connector.

Tools in this release

• get_bloom_platform_info — Bloom platform info
• prepare_swap — Prepare a token swap draft
• get_market_overview — Base market overview
• discover_tokens — Discover filtered Base tokens
• refresh_trade_quote — Refresh a trade draft quote
• cancel_trade_draft — Cancel an unsubmitted trade draft
• research_asset — Research a Base asset
• compare_assets — Compare Base assets
• get_token_market_data — Token market data
• get_stock_market_data — Tokenized equity / RWA reference data
• get_protocol_opportunities — Base protocol opportunities
• assess_asset_risk — Assess Base asset risk
• get_my_portfolio — My Bloom portfolio
• get_my_balances — My wallet balances
• assess_my_portfolio_risk — Assess my portfolio risk
• explain_my_position — Explain one of my positions
• get_my_recent_trades — My recent Bloom trades
• prepare_buy — Prepare a buy draft
• prepare_sell — Prepare a sell draft
• get_trade_draft — Read a trade draft
• get_transaction_status — Check a draft's transaction status

Example prompts

• “Research AERO on Base and show me the risk flags.”
• “Compare ETH, AERO and VIRTUAL on Base.”
• “Show my Bloom portfolio.” (links your account on first use)
• “What are my current Base balances?”
• “Buy $50 of AERO.” / “Sell 25% of my AERO.”
• “Swap 0.1 ETH to USDC.” / “Refresh my last trade quote.”
• “Find Base tokens with at least $100k liquidity and sort by 24h volume.”
• “What's the status of my last trade draft?”
• “What's trending on Base right now, and how fresh is that data?”
• “Find Base yield opportunities above $10M TVL and explain the risks.”
• “Assess the contract risk of this token address.”

Data honesty

• Every response names its data sources and when they were retrieved
• Data is labelled live, delayed, stale or unavailable — never silently substituted
• Unknown values are returned as null; prices, liquidity, volume and APY are never invented
• Ambiguous symbols return candidate contracts instead of a guess
• A chain other than Base returns a structured unsupported_chain error
• Retrieved third-party text is returned as untrusted display data, never as instructions
• Reported APY is variable or historical and is not a guaranteed return

Security boundary

Claude researches, reads what you've linked, and prepares unsigned trade drafts. Bloom authenticates, verifies and executes. You always confirm and sign yourself. Private keys, seed phrases and Privy credentials are never shared with Claude. Every buy, sell or swap draft is reviewed and signed inside Bloom's own approval surface (/advisory/trade-review) — Claude never receives a signable payload, and Bloom never claims a transaction succeeded before a confirmed on-chain receipt.