FAQ

A Robinhood Chain intelligence surface for humans and agents: search, charts, desk, pons launches, wallet tracking, and MCP tools — not a custodian and not a CEX.

It reads public RPC, DexScreener, GeckoTerminal, DefiLlama, RHJ Stock Token APIs, and on-chain pons factories, then exposes that as a website and as MCP/REST tools.

Traders, researchers, and agent hosts (Cursor, Claude, ChatGPT, Grok) who need Robinhood Chain context without pasting keys.

Robinhood Chain only (EIP-155 4663). DexScreener/Gecko slug is robinhood, never 4663.

The in-app assistant on /orbit. Same tools as the MCP server. It scans tokens, tracks wallets, and can prepare an unsigned pons launch.

If NVIDIA_API_KEY is set, NVIDIA NIM (default meta/llama-3.1-70b-instruct) with tool calling. Otherwise a deterministic MCP-tools agent. There is no NVIDIA model inside Supabase.

Yes. It dispatches the same listed MCP tools. Replies show which tools ran. Tool failures are explained; the chat does not crash.

Scan NVDA, desk overview, track a 0x wallet, holders, activity, or “launch token named Aurora ticker AUR”. Do not paste a seed phrase.

Model Context Protocol. Hosts call Apogee over HTTP. Canonical URL: https://apogeemcp.digital/api/mcp (alias /mcp). Auth none.

3000 catalog operations. Listed tools with schemas: /developers/tools (generated from source). Aliases like scan_NVDA go through search_catalog / run_tool.

The website, /api/v1, and /api/mcp share src/lib/dispatch.ts. A scan on Desk is the same engine an agent calls.

No. Live MCP is auth none. Optional paid plans: send SOL or USDC to the published Solana treasury, then paste the Solscan tx link. 25% is allocated to a manual $ORBITX buy-and-burn after payment. Do not pay any other address.

write_onchain_note records a public Solana memo from the Apogee service wallet, then buys and burns about $0.03 of $ORBITX (keeping a $0.15 float so the token account stays rented). The feed on /onchain-notes shows confirmed signatures only. Do not put secrets in a memo.

write_token_seal on /onchain-seals lets you pick $ORBITX or $ROKHA, write a memo, and attach an image. The service wallet stores the image forever, mints a 1/1, then buys and burns up to $0.25 of that token. Only 50 seals will ever be minted — after that the set is closed. Each seal is a numbered Saturn card. Do not put secrets in the memo or image.

Yes. Connect https://apogeemcp.digital/api/mcp or REST /api/v1. Partnership conversations: /developers/partners. That form does not sell access.

Orbit POSTs /api/agent, which runs dispatchTool. NVIDIA, when enabled, chooses tools; otherwise intents map to the same functions.

Public RPC, DexScreener, GeckoTerminal, DefiLlama, RHJ, and pons factory logs. It can be delayed or wrong. Tickers collide — resolve by contract.

On request. Desk refreshes about every 45s in the browser. Token buy/sell polls Gecko trades every 20s. There is no private websocket firehose.

Mark-to-market: RPC balances × DexScreener USD. Cost basis is not recovered when Blockscout history is truncated. We do not invent realized PnL.

USD in the deepest Robinhood Chain pool for that token. See the glossary chip on token pages.

pons v2 is a bonding curve then Uniswap v4. v1 is Uniswap v3 vs WETH. Apogee indexes TokenLaunched events. You sign the unsigned v2 tx in Phantom.

On-chain pons metadata, DexScreener info, Gecko token/info (image, socials, supply), IPFS/Arweave URI fallbacks.

Broken URI, slow IPFS, or no metadata. Cards show a letter mark instead of hiding the token.

No. Phantom (EIP-1193) stays in your browser. We never take a seed phrase or private key.

Address, native ETH mark, watched USDG/WETH/Stock Token balances, and explorer flow when Blockscout allows it.

Queries run in your session against public RPC/APIs. There are no user accounts to store a portfolio.

Anything you look up is already on a public chain or market API. The site does not publish a social profile of your trades.

There is no account, so no visibility toggle. Tool telemetry may log tool name, query string, and timestamp when Supabase is configured.

They don't exist as account switches. See /privacy. Do not expect a public/private profile that isn't in the backend.