# Ultron Independent AI research assistant and developer MCP for Robinhood Chain4663. Humans execute trades. MCP: https://ultrontrading.app/mcp OpenAPI: https://ultrontrading.app/openapi.json Trading skill (authenticated): https://ultrontrading.app/trading/SKILL.md Builder skill (authenticated): https://ultrontrading.app/builder/SKILL.md Full documentation: https://ultrontrading.app/llms-full.txt No trade execution, brokerage access, issuer privileges or guaranteed outcomes. Private research is available only as focused authenticated MCP excerpts. FOMO context uses authorized supplied observations. Alchemy wallet history needs a user key, supported method coverage and an approved read budget. Telegram and Discord are coming soon. Paid research requires explicit approval in the in-AI panel or secure website fallback; keys never go in chat. # Historical research and similar projects Ask Ultron for comparable projects, dated market evidence and product lessons inside your AI. ## Ask naturally Ask “What other token built something similar?” or describe a product idea. Ultron’s find_similar_projects tool searches its private historical project library, expands known project names into product categories, and returns a few relevant comparisons with reasons and sources. Token briefs and builder plans also attach historical comparisons. You do not need to download or install the full research collection. ## Research first, fresh sources next The curated library covers the historical token cohort, utility expansion, technical product examples and selected deeper reviews. Records include product evidence, token economics, lessons, limitations and dated market samples where available. If no useful match exists, Ultron instructs your AI to use its native web search, open primary sources and verify the project’s chain and identity. Fresh web findings are distinguished from historical library evidence. If your host cannot search, Ultron must say so rather than invent results. ## What grounded in historical research means Ultron retrieves historical market and project research for your AI at answer time. This does not fine-tune Claude, ChatGPT or another underlying model. The accurate description is: Ultron draws on historical market data and project research. Historical cap samples are not live prices, executable liquidity, proven all-time highs or evidence that a technology caused a token’s success. Comparable products can differ in contracts, distribution and token economics. ## Private library, focused answers The complete source collection remains private. Authenticated users receive bounded, relevant excerpts through MCP; it is not bundled into browser code or downloadable skills. The index is curated and does not contain every raw document or every token. # Ultron in Claude Cowork Use Ultron inside Cowork for user-defined research, native schedules and phone notifications. ## Your AI is the workspace Use Claude Cowork for recurring research and native phone notifications. Connect Ultron once through remote MCP, then keep the conversation, tools, provider setup and research approvals inside your AI. Regular chat remains useful for one-off questions. Use a successful Ultron tool call to verify the connection. For repeatable work, keep Ultron enabled in the task and put its tool names in the saved instructions. The optional Ultron plugin includes a scheduled-research skill. [Download Claude workflow package](/downloads/ultron-claude.zip) · [Claude scheduling documentation](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork) ## Context that survives the next run Cowork scheduled tasks start fresh sessions. Store the objective, cadence, timezone, tools and notification conditions in the task prompt or attached skill. Use get_task_context and save_task_context with one stable taskKey for small baselines and delivered-result IDs. Version checks prevent concurrent overwrites. Remote connector-only tasks do not depend on a laptop staying awake. Local folders, local tools and Dispatch have their own execution requirements. Keep source material in an accessible account project or connected service. [Cowork projects](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) ## Notifications belong to your AI Create and manage the task using Cowork’s native scheduler. Enable the host’s notifications and test once on the intended device. A successful test does not guarantee every future run; monitor failed runs and expired connections. Ultron does not require a separate mobile app, PWA, device pairing, Telegram or Discord. Avoid duplicating the same scan in both Cowork and Ultron server routines. Use a server monitor only when persistent collection is part of the selected workflow. ## Your rules, not a preset strategy Conditions remain user-defined. Preserve exact metrics and intervals; do not substitute FDV for market cap or a different volume window. Missing observations are unknown. A crossing requires a prior observation, while an above-threshold snapshot does not. get_schedule_readiness reports Ultron permissions and connection expiry. It cannot inspect the host’s schedule. Reconnect through the host when credentials expire. Paid social requests require the explicit in-AI review; recurring scans do not silently spend on new paid research. ## ChatGPT Work and other AI apps Use the native scheduled-task surface when it supports Ultron’s connected tools. Feature and notification availability depend on the host, plan and workspace. Remote web tasks and local desktop project tasks have different requirements. The same Ultron task-context tools and scheduled-research skill work without assuming a specific scheduler API. Verify a run and delivery in the selected app; do not claim identical support across every client. [ChatGPT scheduled tasks](https://learn.chatgpt.com/docs/automations) · [ChatGPT notifications](https://learn.chatgpt.com/docs/notifications) # Meet Ultron Connect your AI to Robinhood Chain research, monitoring and developer tools. Start here. ## Your AI, connected to Robinhood Ultron is an independent research assistant and developer MCP for Robinhood Chain. It gives a compatible AI agent structured access to stock-token reference data, indexed markets, contract reads, wallet checks and persistent alerts. It also supplies focused documentation, implementation recipes and integration checks to coding agents. Ultron does not trade. It never signs a transaction, submits an order or takes custody of funds. You decide what matters and execute any trades yourself. ## Choose how you want to use it Already use a compatible AI client? Add Ultron as a remote MCP connection. Your AI stays in that client; Ultron supplies tools and evidence. Connect Ultron to your existing AI through MCP. Approved watch conditions create events in your AI through scheduled checks. Telegram and Discord are coming soon. [Connect your AI](/docs/connect) · [Builder quickstart](/docs/builders) ## Start with the data already connected Robinhood issuer APIs, chain-checked RPC, DEX Screener and GeckoTerminal provide base market and chain research. No personal brokerage login is required or provided. Add Alchemy for supported wallet history, Apify for clip research or X for recent conversation evidence only when your workflow needs it. [Data coverage and provider keys](/docs/providers) ## A useful first prompt Start with a concrete outcome. Ultron resolves identity and conditions before creating an alert; a question alone does not activate a routine. ``` Find Robinhood Chain tokens with meaningful liquidity and volume. Explain the sources and gaps, then help me choose a pair to watch. ``` [Browse every tool](/docs/tools) # Connect your AI Set up Ultron in a compatible Claude, ChatGPT or coding-agent client using remote MCP and OAuth or a scoped key. ## Your first conversation After connecting, say Hi Ultron or let’s use Ultron. Ultron opens a connection form inside an MCP Apps-compatible AI client. Enter each key once. Connect saves it and checks supported market/wallet providers using the approved read budget, then continues the AI automatically where the host supports messages. Failed saves retain the field for retry; failed verification does not require re-entering a saved key. X/Apify paid research still requires its separate approval. If external setup is necessary, the secure setup handoff uses the existing connection without another wallet login; finishing signals the original open AI panel to resume. Provider signup pages still open externally. Unsupported clients keep a secure website fallback. Start with Blockscout for ranked token holders and top-holder supply concentration. Create a free key at dev.blockscout.com, save it with an approved daily read budget, then test access. Holder analysis includes contracts and burn addresses and uses total supply, not circulating supply. Trader setup also offers CoinGecko for market history, Alchemy for wallet history, Apify for clips and X for recent conversation data. Base prices and explicit wallet balance reads need no extra key. Save optional keys in the secure form; approve the Alchemy daily read limit or each paid social request. Builder setup offers relevant infrastructure guidance. With your agreement and setup-management permission, save_ultron_setup remembers your choices in your account. Read-only clients can use the current conversation without claiming persistent changes. Use Claude Cowork scheduled tasks and its phone notifications. In ChatGPT Work or another AI, use the equivalent native scheduling and notification features when available. Keep setup and interactions inside your AI. Ultron does not offer separate phone pairing, a notification app, Telegram or Discord. ## One MCP endpoint Ultron exposes Streamable HTTP MCP at the endpoint below. A compatible host can discover its tools, authenticated builder resources and trading playbook. Connection support depends on your client, plan, workspace settings and administrator policy. ``` https://ultrontrading.app/mcp ``` ## Connect with OAuth In your AI client's connector or remote-MCP settings, add the endpoint. Where OAuth is supported, follow the browser authorization step, sign in with MetaMask, Phantom or another compatible installed EVM wallet and review the scopes. Use your normal wallet-enabled browser for sign-in. If an embedded browser cannot load the wallet, Ultron prepares a fresh visible handoff link with Open and Copy actions. Keep the original AI login attempt open so it can receive the callback. A website cannot force a host app to open external links in a particular browser; the copyable link remains available. Computer-use access is not required for the user to approve sign-in. Return to your AI client once authorization completes. Read access enables research. Account-operation access enables intentional watches and preferences. Provider-key management is a separate connections:write permission for the embedded form. Existing connectors must reconnect once and approve that permission to edit keys inside the AI. It does not grant wallet spending or paid-social approval. A separate research:approve scope enables explicit reviewed paid requests in the workspace. [Open setup](/start) · [Authentication details](/docs/authentication) ## Use a scoped access key For clients supporting authorization headers, create a Ultron access key in your workspace and use it as the Bearer credential. Store it in your client's secret configuration, not a chat message or a committed repository. The key is shown once and can be revoked. Do not put a key in the endpoint URL. The example is a generic HTTP-client configuration; consult your client's current documentation for the exact settings format. ``` { "url": "https://ultrontrading.app/mcp", "headers": { "Authorization": "Bearer " } } ``` ## Check the connection Ask your agent to call assistant_capabilities and network_status. You should see Robinhood Chain ID 4663 and the current coverage. For building, start with get_builder_capabilities. A saved endpoint alone does not prove that authentication or tool execution succeeded. Claude and ChatGPT use the tools through their own compatible connector features. ## Choose your AI Claude and ChatGPT support custom remote MCP connections on supported plans and settings. Cursor and Codex support remote MCP. Kimi connects through Kimi Code; this is not a claim that every Kimi chat interface accepts connectors. DeepSeek can power an MCP-capable agent such as Cline. Gemini connects through Gemini CLI. These are client/protocol compatibility routes, not claims that every provider client has been end-to-end certified with Ultron. [Kimi Code MCP](https://moonshotai.github.io/kimi-cli/en/customization/mcp.html) · [DeepSeek in Cline](https://docs.cline.bot/provider-config/deepseek) · [Cursor MCP](https://docs.cursor.com/context/model-context-protocol) ## Connect from Chrome, Safari or an embedded AI browser A browser with MetaMask, Phantom or another compatible EVM wallet can sign in directly. If no wallet is detected, open the wallet sign-in link in your normal wallet-enabled browser. Keep this original AI sign-in window open. Copy the generated approval link into a browser with MetaMask or Phantom, or scan the QR code on the HTTPS site to approve in Phantom on your phone. The external browser only approves your wallet and access request; it does not open the client callback. After approval, Ultron completes the OAuth return in the original AI browser. The handoff expires after five minutes and can be cancelled. If the AI client itself has cancelled or timed out its login, start a fresh connection there. No trade or spending permission is granted. You may alternatively create a scoped access key and store it in the client’s credential settings. ## Does Ultron need my computer password? No. Ultron signs you in using wallet ownership and never needs your Mac login, Keychain or wallet-unlock password. Native client or OS prompts are separate and must be handled by you, never pasted into chat. Agents should use the client’s existing authenticated MCP connection. They must not run the macOS security command, scrape credential stores or extract saved OAuth tokens to test Ultron. If the native connector is unavailable, use its settings or reconnect normally. Ultron cannot suppress the host operating system’s legitimate credential prompts. ## Keys inside your AI Ask Ultron to open its connection form. API keys are sent directly from the form to Ultron’s encrypted backend over HTTPS, not as chat messages or model-visible tool arguments. Claude receives connection status updates. The form session expires after 20 minutes and stops working if the original connector grant is revoked. An older or read-only connector can view status but cannot edit keys. Reconnect with provider-key management permission, or use the secure website fallback. Do not paste secrets into ordinary chat. Paid X/Apify requests can be reviewed in the research workspace with research:approve permission; the website remains a fallback. # The trading assistant How Ultron turns a research question into sourced evidence and personal market alerts, with the human in control. ## Ask, investigate, keep watch Describe what you want to understand: a contract, stock token, pool, wallet or market pattern. Ultron uses exact chain and contract identities, calls the available read tools, and returns evidence with source links and observation times. The assistant follows three research lanes: meme or clip narrative, real product or infrastructure utility, and stock/ticker catalysts. A token does not need a viral video to be worth investigating. Volume, momentum and liquidity can justify a research alert without invented social proof. ## Discovery is a sample DEX Screener and GeckoTerminal discovery uses bounded indexed feeds. Two-hour and calendar-day rankings use complete candles for up to ten candidate pools. These results are samples, never a claim to cover every coin on the chain. Paid visibility does not establish organic demand. FOMO-first discovery is available when your connected agent supplies a recent FOMO snapshot. Ultron does not currently run a continuous FOMO board feed. Imported observations are explicitly labeled unverified and become stale. [FOMO and source evidence](/docs/evidence) ## What an answer should contain A useful answer identifies the token and network, says what was actually measured, links the source, notes the observation window and flags missing information. Market cap and fully diluted valuation are separate fields. Headlines are leads, not proof of a catalyst. Public wallet labels and shared funders are clues, not proof that accounts have the same owner. Indexed prices are not execution guarantees. Ultron cannot establish that trading volume is organic or that a token is safe. ## Keep the ping short Connect Ultron to your existing AI through MCP. Approved watch conditions create events in your AI through scheduled checks. Telegram and Discord are coming soon. ``` Watch this exact pair when hourly volume exceeds $100,000, price change exceeds 8%, and liquidity stays above $50,000. Show me the rule before activating it. ``` [Monitor rules](/docs/monitors) · [Connect your AI to use this guide](/docs/connect) ## What the current data supports Available now: indexed token prices and liquidity, token-specific source windows, ETH and explicitly requested token balances, native-balance threshold alerts, price/volume/liquidity conditions, stock-token reference data and optional social/news research. Alerts appear in your AI through scheduled checks; an external AI client only pushes notifications if it supports that behavior. Use get_market_history for complete five-minute or hourly pool candles, and compare_market_windows for equal-window volume comparisons. Rankings remain a bounded provider sample. Alchemy-backed wallet transfers require your key and method coverage; opposing flows are only candidate swaps. FIFO profit calculations require recorded USD cost basis and do not reconstruct an entire wallet automatically. ## Context inside your AI Authenticated MCP calls retrieve relevant excerpts from maintained Robinhood research. Your agent combines dated case evidence with current tool results. The research library itself is not public, and old market outcomes are not current facts or guarantees. Ask “What can you do?” for a short capability menu. get_trader_capabilities contains 50 example workflows and the source or setup each needs. # Data sources & API keys Bring your own CoinGecko, Alchemy, Apify or X keys. Understand free public data, account quotas and secure enrollment. ## CoinGecko: your market-data account Start with a CoinGecko Demo account, then open Developer Dashboard → API keys. Save the Demo key in Ultron’s secure form with Demo selected. Approve daily and monthly request budgets. An existing Pro account is optional; Ultron does not buy, upgrade or fund a plan for you. Supported pool rankings, history and exact-coin movement checks use your selected CoinGecko key and account-specific cache. A failed key or exhausted budget does not use another account’s paid key. DEX Screener’s public API and public GeckoTerminal are keyless; there is no separate free key signup to complete for those public endpoints. Free plans are limited, and other applications using your key consume the same provider allowance. Saving a key is not a live coverage check. Quotes, swaps and legacy DEX-specific tools may still use their documented public sources. [CoinGecko key dashboard](https://www.coingecko.com/en/developers/dashboard#api-keys) · [CoinGecko Demo authentication](https://docs.coingecko.com/demo/reference/authentication) · [Save your key securely](/dashboard#research) ## Robinhood analytics: already connected Ultron's included tools read the issuer asset registry, stock reference quotes and corporate actions, plus a configured chain-checked RPC. DEX Screener provides indexed market observations. These do not require a personal provider key from each user. This is public chain and issuer data, not access to a Robinhood brokerage account. It is not a complete holder graph, smart-money index or order-flow terminal. [Robinhood stock-token APIs](https://docs.robinhood.com/chain/stock-token-apis/) ## Apify: clip research Create an Apify account, copy an API token from your account integration settings, then save it in Ultron's encrypted Research connection form. The shipped adapter runs clockworks/tiktok-scraper for one narrow hashtag and at most five returned clips. Media downloads and additional author metadata are off. The assistant prepares a request; you review it and approve a maximum actor-run charge of up to $0.25. It starts asynchronously. Return to the request or ask your agent to check its result. Apify platform reads may have their own usage charges. Instagram and arbitrary Apify actors are not supported in this release. [Apify API tokens](https://console.apify.com/settings/integrations) · [Connect research providers](/connections#research) ## X: recent conversation Create developer access in X's console and supply your bearer API credential in Ultron's secure Research form. Consumer X subscriptions are not this credential. Review your current endpoint pricing and credit balance before approving a request. Ultron reads usage, then counts for the two most recent completed UTC hours, then at most ten recent posts if the current count is nonzero. It does not paginate, expand authors or query the full archive. Percent change has no numeric value when the earlier count is zero. Most-engaged means within the returned sample. X's usage endpoint is not a prepaid dollar balance. You confirm at least $2 remains in the console before paid research. These endpoints do not expose a dollar spending cap; Ultron does not pretend the Apify cap applies to X. [X developer console](https://console.x.com/) ## Use your existing AI Remote MCP uses the AI client you already have; you do not need a separate model API key for that connection. The optional hosted web assistant uses a separately billed supported model API account. Telegram and Discord are coming soon. ## Never paste keys into chat The connection form encrypts keys with an account-and-provider-bound server key. Status responses only show the last four characters. Saving a research key does not certify its permissions or available credit; an approved request checks access. Disconnect blocks subsequent calls but cannot cancel a provider run already accepted. ## Wallet and market tracking integrations DEX Screener supplies built-in indexed market data. Robinhood Chain RPC supplies native and specified token balances. The Robinhood explorer and Blockscout provide explorer context; contract evidence is source-linked. Save an Alchemy Robinhood mainnet app key and approve a daily limit of 5–1000 read requests in secure setup. Ultron verifies chain 4663 before requesting native/ERC-20 transfer history or token balances. Method access depends on the provider plan and network coverage; unavailable reads fail explicitly. No signing, sending or automatic webhook provisioning is exposed. Transfers alone are not purchases or profit. [Alchemy Robinhood Chain support](https://www.alchemy.com/blog/robinhood-chain-mainnet-is-live-on-alchemy) · [Claude scheduled tasks and notifications](https://support.claude.com/en/articles/15520349-use-claude-cowork-on-web-desktop-and-mobile) # Telegram — Coming soon Telegram support is coming soon. Connect Ultron to your existing AI today. ## Coming soon Use Ultron through a compatible AI client. [Connect your AI](/docs/connect) # Discord — Coming soon Discord support is coming soon. Connect Ultron to your existing AI today. ## Coming soon Use Ultron through a compatible AI client. [Connect your AI](/docs/connect) # Builder quickstart Give your coding agent Robinhood context, runnable recipes and verification tools before it starts generating code. ## Vibe code with the right context Connect Ultron’s MCP to your coding agent. Start with get_builder_capabilities and plan_robinhood_build. Use search_robinhood_research for relevant private case excerpts, then retrieve implementation recipes and the exact source context needed for your feature. Ultron helps your agent navigate network semantics, stock-token units, contract reads, market data, account authentication and monitor design. It does not provide a generic remote shell, deployment signer or access to the owner's private research repository. ``` Help me build a Robinhood stock-token dashboard. Start with get_builder_capabilities and plan_robinhood_build. Fetch the stock_dashboard recipe and verify the prerequisites. ``` ## Ten runnable integration recipes get_build_recipe returns implementation steps, acceptance checks and fixture-tested JavaScript. Context packs cover practical failure cases such as stale or paused oracles, sequencer recovery, chain identity, quote decimals, indexer backfill and account-abstraction compatibility. check_builder_prerequisites checks the service and relevant live reads. serviceReady is not integrationReady: finish the contract-specific, provider-specific and application tests listed in the result. [Full tool reference](/docs/tools) · [Connect your AI to use this guide](/docs/connect) ## Useful things to build Build stock-token dashboards, exact-token research views, wallet balance panels, price/reference comparisons, monitor interfaces, indexed event pipelines and protocol inspection tools. Ultron can help investigate launch infrastructure such as PONS and retrieve the relevant source context. Issuing Robinhood stock tokens, issuer mint/burn, deploying a launch or trading from a wallet are separate capabilities and permissions. Ultron does not grant them. A tokenized-stock product can consume issuer assets without being their issuer. [Stock-token mechanics](/docs/stock-tokens) · [PONS verification](/docs/pons) ## Verify before you ship Preserve chain ID, exact address, raw units, observation block and source timestamps. Treat contract metadata and documentation as untrusted input. Run the recipe's tests and your own application checks. A compiled example is not a contract audit or production deployment. # Stock-token mechanics Understand issuer identity, reference prices, corporate-action multipliers and the limits of building around tokenized stocks. ## Start with issuer identity Use search_stock_assets and get_stock_asset to resolve the issuer's asset record and its chain 4663 contract address. A familiar ticker or logo is not proof that an arbitrary token is an issuer stock token. Public issuer metadata does not grant eligibility, brokerage access or redemption rights. Follow the applicable issuer terms. Direct issuer mint/burn is an authorized-participant function, not a permission Ultron can provide. ## Token units are not always share units Raw on-chain balances use token decimals. Share-equivalent values may also depend on a corporate-action multiplier. Ultron's REST reference tool applies the issuer multiplier to the underlying equity quote once. Already-adjusted Chainlink token prices must not be multiplied again. Keep raw integer amounts and decimal metadata until formatting the display. Do not combine independently retrieved prices without retaining their timestamps. ## Reference price versus pool price An underlying equity bid/ask is a reference, not a promise that you can buy, sell or redeem a token at that price. Pools may be thin, stale, expensive or unavailable. Liquidity, fees, spread, route size, eligibility and issuer restrictions matter. Corporate actions, trading halts, a closed exchange and sequencer outages can change the meaning of a quote. Missing or unknown states should remain visible. A premium to a reference quote is not automatically executable arbitrage. [Official stock-token integration guidance](https://docs.robinhood.com/chain/building-with-stock-tokens/) ## Build around stocks, responsibly Ultron supplies data, examples and simulations for stock-token products. It does not create tokenized shares, operate a broker, promise redemption, submit orders or sign deployments. Your agent can use the MCP to understand the infrastructure before you independently implement and validate a product. # PONS deployment checks Verify the PONS V2 factory runtime, inspect exact token records and understand what the check does not prove. ## Verify the deployed factory check_pons_deployment checks Robinhood Chain 4663, pins a block and compares the factory runtime with an independently retrieved Sourcify exact-match artifact. The reviewed factory is 0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e. The Sourcify-verified source differs from the public repository snapshot. Use the deployment-specific ABI for this address. The root PONS repository ABI describes V1 and must not be applied indiscriminately to V2. ``` {"token":""} ``` [Sourcify deployment record](https://sourcify.dev/server/v2/contract/4663/0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e) ## Interpret the token record The V2 record has 15 static ABI words. The check validates token identity, curve bytecode presence and the curve's token(), factory() and pairToken() relationships at the same block. A zero pairToken means native ETH in this reviewed deployment. Phases are NotGraduated, Swept, PoolCreated and Rescued. A record or a graduation flag does not establish useful liquidity or a valid execution route. Curve code hashes are returned, but curve source equivalence is not verified by this tool. ## Verification is not an audit Matching a deployed factory to a verified artifact does not establish token authenticity, safe permissions, organic demand or profitability. This tool does not launch tokens, build trades, claim fees or broadcast anything. # Monitors & compound signals Configure persistent account alerts, understand edge triggering, and distinguish market conditions from guaranteed trading signals. ## Eight supported watch types Supported watches cover stock reference-price thresholds, corporate-action multiplier changes, native ETH balances, transaction receipt state, indexed pool price, pool liquidity, trailing24-hour volume and compound market signals. A compound market signal requires every selected hourly-volume, hourly-price-change, liquidity and optional market-cap condition to pass. Missing values cannot become zero; FDV is never a fallback for market cap. ``` { "name":"My market watch", "kind":"market_signal", "target":"", "operator":"above", "threshold":0.5, "intervalSeconds":300, "signal":{ "minVolume1hUsd":100000, "minPriceChange1hPercent":8, "minLiquidityUsd":50000 } } ``` ## Confirm the exact rule Hosted chat prepares a proposal for you to review in the browser. It expires after 30 minutes. The review shows the target, conditions and frequency. Compatible MCP agents with account-operation scope may create a watch when you intentionally request it. Market watches pin both pool assets. An identity change, unknown source age or missing required measurement prevents a successful observation. Conditions are research filters, not technical-breakout proofs, buy instructions or organic-volume verification. ## Alerts on entering the condition A threshold may alert on its first observation if it is already matched. Further matching observations do not repeatedly alert. Once the condition becomes false, the watch rearms. Change watches first establish a baseline. Failures retry with backoff. After three consecutive failures the inbox receives a needs-attention event. Checks run automatically with recovery for interrupted work. There is no guarantee of second-perfect scheduling or uninterrupted provider availability. ## Delivery and limits Connect Ultron to your existing AI through MCP. Approved watch conditions create events in your AI through scheduled checks. Telegram and Discord are coming soon. Research routines support future market rankings, recurring token pulses, confluence scans, reminders and approved wallet-transfer checks. Your AI retrieves results and sends notifications through its own supported task feature. Routines do not start paid Apify or X searches; they can use recent approved evidence. ## One-off and recurring research Confirm the result wanted, exact assets, start time, timezone, frequency and delivery before create_research_routine. Recurring intervals start at five minutes; one-shot requests can run at a future time. Each account supports 20 routines. Checks are queued and can be delayed by source availability or load. Wallet routines need explicit metered-read approval and normally establish a baseline without reporting old transfers. Pause, resume or delete a routine through your AI. get_routine_results returns account-owned results; acknowledge each after successful delivery. Routine results expire after 30 days. A repeating interval is elapsed time. Use the AI host’s calendar scheduler for fixed local times across daylight-saving changes. The MCP connection alone does not wake a closed chat. # FOMO & evidence quality Import FOMO observations without confusing them with verified live feeds or wallet identities. ## Bring an observed snapshot A compatible host agent may read a user-authorized FOMO browser view and call import_fomo_snapshot with the source page, observation time and exact Robinhood token addresses. Only observations within the last hour are accepted. No session cookies, token-bearing URLs or login exports belong in that input. The record remains user-or-agent-supplied and unverified. Observations older than 15 minutes are marked stale, and retained for 24 hours. get_research_evidence returns only your own imports. ## Do not confuse the viewer with the trader A named FOMO handle is a public profile label, not automatically a verified wallet. The viewer's Your positions panel is not the named trader's holdings. A screenshot or board row cannot establish the complete activity of a person. ## Separate observation from explanation An X mention count, a TikTok view count or a paid boost is an observation. An explanation for price movement is an inference unless independently supported. Keep the original post or article link and its date. Do not label a token's creator or origin as authentic just because one mint is earlier. Imported FOMO heat cannot make missing live market data valid. Ultron does not claim full FOMO market coverage or bypass platform access controls. # Authentication & permissions Wallet sign-in, account-owned MCP keys, OAuth PKCE and the boundaries of each permission. ## Your wallet is your sign-in Choose MetaMask, Phantom or another compatible installed EVM wallet. Ultron uses that wallet on Robinhood Chain 4663. A personal_sign message proves ownership of your 0x wallet address. It does not authorize an on-chain transaction, trade, spending approval or private brokerage access. Challenges are single-use, bound to the site origin, address and chain 4663, and expire after five minutes. Sessions use Secure, HttpOnly, host-only cookies in production. Browser mutations require the correct origin and CSRF token. ## Scoped permissions chain:read allows research tools and account-owned reads. monitors:write allows intentional watch, preference, evidence-import and research-proposal operations. Neither scope authorizes trading. connections:write permits provider-key management through the secure embedded form. research:approve permits reviewed paid research requests through the embedded workspace. An authenticated website session provides a fallback. Account ownership is enforced in database queries; knowing another request ID is not access. connections:write separately permits provider-key management in the embedded Ultron form. This permission is not implied by chain:read or monitors:write. ## OAuth and lifecycle Remote clients use authorization-code OAuth with PKCE S256 and registered redirects. Access keys expire after 30 days and website sessions after seven days. Newly approved OAuth connections receive rotating refresh tokens and can renew access for up to 90 days. Each refresh replaces the prior tokens; replay revokes the connection. Existing connections need one reconnect to receive refresh tokens, and the AI client must support renewal. Revoke an access key or delete your account from the workspace. Disconnect provider credentials from Connections. Deletion removes account-owned records; it cannot delete public blockchain records or recall a third-party request already accepted. # REST API reference Use the same Ultron tools through authenticated HTTP calls, with structured schemas, scopes and errors. ## Call a tool POST /api/tools/{tool_name} accepts the JSON argument object shown in the tool reference. Authenticate with a scoped Ultron Bearer key. Successful REST responses wrap the tool output in result. Check HTTP status and error fields before using a value. ``` curl https://ultrontrading.app/api/tools/network_status \ -H "Authorization: Bearer $ULTRON_ACCESS_KEY" \ -H "Content-Type: application/json" \ --data '{}' ``` ## Machine-readable contracts /openapi.json exposes the current tool paths, input schemas and required scope. MCP clients can list tools and resources at /mcp. The schemas are generated from the same registry used to validate calls, so they should be preferred over copied examples when a tool changes. [OpenAPI specification](/openapi.json) · [All tool schemas](/docs/tools) · [Agent-readable documentation](/llms-full.txt) ## Errors and retries Errors contain a code and a concise message; REST errors include a request ID. Rate-limited requests use HTTP429 with Retry-After where available. Upstream data failure remains unavailable rather than a fabricated quote. GET-like reads can be retried with bounded backoff. Paid research initiation uses account-owned request IDs and browser approval. An unknown charged outcome must not be repeated automatically. [Troubleshooting](/docs/errors) ## Keep requests bounded The beta applies 120 authenticated requests per minute per account, tighter endpoint-specific limits, bounded source response sizes and timeouts. Do not poll complete tool catalogs or every wallet continuously. Cache public source metadata responsibly and retain source timestamps. # Security and access Your keys, your control. Research access without wallet spending permissions. ## Security and access Ultron runs on Railway with HTTPS connections, authenticated account access and encrypted provider credentials. No service can guarantee complete security. ## You stay in control Wallet sign-in does not give Ultron permission to move funds. Keep provider keys in the connection form. Review paid research before approving it. Revoke access or delete your account from your workspace. [Privacy and data controls](/privacy) # Troubleshooting Resolve connection, provider, watch and data-source failures without hiding missing evidence or repeating paid requests. ## My AI cannot see the tools Confirm that the client supports remote Streamable HTTP MCP and that its plan/admin settings allow custom connections. Use the exact /mcp URL, complete OAuth or configure a Bearer header, and reconnect if the grant expired. Call network_status to confirm execution, not just registration. ## Research asks for a key Open Setup → Optional data and save the requested provider credential. Keys do not go in chat. A saved key may lack endpoint permissions or credit. Check the provider console and supported Robinhood methods when a read fails. Ultron does not substitute a different chain. ## A paid request says unknown The service could not confirm the upstream outcome. It may already have incurred a charge or started an actor. Check the provider console before creating another request. Ultron deliberately does not repeat an uncertain paid action automatically. ## A watch stopped producing observations Check the watch's last error, exact asset identities and source timestamps. Missing metrics, stale/unknown transport age or changed pool assets fail the observation. A threshold that stays true does not repeatedly alert; it rearms only after becoming false. ## Messaging — Coming soon Connect Ultron to your existing AI through MCP. Approved watch conditions create events in your AI through scheduled checks. Telegram and Discord are coming soon. ## Two prices do not agree Check token identity, quote asset, raw units, issuer multipliers and observation times first. A stock reference quote and an indexed pool price measure different things. Do not discard a disagreement or call it executable arbitrage without checking the surrounding mechanics. # Limits, costs & launch readiness Understand beta capacity, provider billing, supported features and remaining launch gates. ## Beta limits Each account can create 20 watches, with intervals of 60–86400 seconds. General authenticated traffic is limited to 120 requests/minute, with tighter limits for sensitive actions. Hosted assistant calls have bounded model rounds, tools and output; partial replies are explicitly marked. Each account supports 20 research routines, with recurring intervals of at least five minutes. Paid social approvals are capped at 20 per day. Proposals expire after 30 minutes. Apify requests use at most five items and a displayed actor-run cap up to $0.25. X endpoint billing is governed by your provider account. ## Who pays for what Remote MCP uses your existing AI client. Optional hosted chat uses a separately billed model API account. Alchemy, Apify and X usage follows the connected provider plan; consumer subscriptions do not automatically cover API usage. No unlimited-capacity promise or new paid Cloudflare plan is implied. Service limits and public-data provider quotas apply. Pricing for a future Ultron commercial plan has not been announced here. CoinGecko Demo/Pro requests use the user’s connected account and approved limits. Ultron does not provide an operator-funded paid market-data fallback. Public sources retain shared quotas; bringing an unrelated social key does not lift those limits. ## Available versus still missing Historical research covers up to seven days and 1000 completed candles per pool request; historical leader scans examine at most ten candidates. Wallet history requires a working Alchemy key and supported methods. Profit is calculated only over supplied cost-basis records. FOMO is authorized snapshot context, not a continuous board feed. Host notifications require a separately configured task. Ultron never executes trades, grants issuer access or starts paid research without approval. Telegram and Discord are coming soon. # Your research workspace Markets, wallets, reviewed watches, research approvals and builder exports inside your AI. ## Open it in your AI Ask Ultron to open the research workspace. Select Markets, Wallets, Watches, Research, Builder or Usage. Click a token or transaction, then ask your AI about that exact selection. Expand the view if your client supports fullscreen. Data refreshes on request and follows your provider budgets. Missing coverage is shown explicitly. The workspace never places trades. ## Review before activating Use the watch builder to choose an exact pool, hourly movement threshold, direction and check interval. Review the rule before confirming. Pause, edit or delete owned watches from the list. A host notification schedule is separate; ask your AI to configure and test it. Paid X/Apify research needs research:approve permission and an explicit per-request review. An existing key-management grant does not authorize paid research. Reconnect only when you need the additional permission. ## Build with a workflow pack The Builder view provides integration recipes, source examples and project ZIPs. Download a Claude, Codex, Gemini CLI or Kimi workflow bundle, connect OAuth and verify a tool call. These bundles contain instructions and connector configuration; the private research library stays on Ultron. Native client behavior and plugin installation vary. The Kimi download is a skill/configuration kit. Starter projects are unexecuted server-side integration libraries and require your own project tests. ## Keep credentials out of chat Research panels use authenticated tools. Secret entry uses the dedicated connection flow and is not exposed as a model argument. ChatGPT-style hosts use external secure account linking. No wallet signing or spending permission is provided. # Know what’s moving. Live Robinhood data and historical project research inside your AI. Compare similar tokens, track wallets and build informed watch conditions. ## Your AI knows what came before. Ask which past projects built similar utility, how their tokens worked and what the evidence actually shows. Ultron retrieves relevant historical Robinhood research with dates and sources. Use your AI’s image and web tools to investigate a logo or visual theme, then compare verified project identities and historical context. A resemblance is not a prediction. [Historical research](/docs/historical-research) ## Less tab switching. More context. Price in one tab. Liquidity in another. A stock headline buried in a chat. Ultron brings those questions into one conversation with your existing AI, then gives the answers sources and boundaries. Ask about an exact token, investigate a wallet's visible balances, compare an issuer reference quote with indexed markets, or set a watch for the conditions you care about. You decide what to do with the information. ## An alert that knows what you meant. Combine hourly volume, price change, liquidity and a market-cap range on an exact Robinhood pair. Review the rule once. Ultron watches for the condition and creates an event for your AI to retrieve when it is met. Connect Ultron to your existing AI. Telegram and Discord are coming soon. [See how watches work](/docs/monitors) ## Use the research stack you need. Robinhood issuer data, chain reads and indexed markets are connected already. Add Apify for small clip searches and X for recent conversation counts. Paid research requires your approval. Put powerful AI to work on the research you keep doing manually. Ask better questions, keep the sources and spend less time reconciling tabs. [Set up Ultron](/start) · [Read the trading guide](/docs/trading-assistant) # Vibe code. With the right context. Ultron's MCP gives coding agents Robinhood Chain tools, source-linked context and runnable recipes for useful on-chain products. ## Your agent should not start from a blank tab. Give it focused Robinhood documentation, exact contract reads and implementation recipes before it guesses an API or applies the wrong token multiplier. Ultron connects your coding agent to the details that turn a generated demo into a working integration. Start with a product idea. The MCP can propose a supported implementation path, retrieve the relevant context and check live prerequisites. Your code stays in your project and your editor. ## Build things people can actually use. Stock-token dashboards. Research terminals. Wallet views. Personal alerts. Market/reference comparisons. Protocol inspectors. Ultron supplies read tools and guarded examples for these building blocks. For launch infrastructure, inspect PONS source context and verify the deployed V2 factory. Token launch, contract deployment and issuer stock-token creation remain separate workflows; Ultron does not grant issuer rights or sign transactions. [Stock-token guide](/docs/stock-tokens) · [PONS deployment checks](/docs/pons) ## Get to a verified first call faster. The toolkit includes 10 runnable recipes and 14 focused context packs, plus live tools for chain identity, assets, markets and contract reads. Ask for the task-specific recipe rather than loading a pile of unrelated documents. Treat examples as a starting point. Run their acceptance checks and your application tests. Ultron makes the research and integration work easier; it does not turn source verification into a security audit. [Builder quickstart](/docs/builders) · [Connect the MCP](/docs/connect) # Keep the AI you already use. Connect Ultron to your existing AI through MCP. ## Claude, ChatGPT and compatible agents Add the remote MCP endpoint to a client that supports custom Streamable HTTP connections. Authenticate with OAuth or a scoped key, depending on the client. Ultron supplies the tools; your existing AI supplies the conversation. Availability depends on client features, plan and admin settings. Ultron is an independent service, not an official Robinhood, Anthropic or OpenAI integration partner. [Connection instructions](/docs/connect) ## Telegram & Discord — Coming soon Messaging adapters are included but disabled in this local integration. A separate Ultron bot identity and operator credentials are required before linking an account or delivering alerts. Connect Ultron to your existing AI. Telegram and Discord are coming soon. ## Connect sources when you need them. Base Robinhood issuer and market reads work without individual data keys. The guided setup explains Apify, X and optional supported-chain [Provider setup](/docs/providers) · [Start connecting](/start) # Built around Robinhood Chain. Understand how Ultron connects AI agents to Robinhood Chain stock-token data, contract reads and developer infrastructure. ## One network. Specific context. Ultron's market and contract tools target Robinhood Chain mainnet, chain ID 4663. The service checks its RPC network before trusting reads. Ethereum is the gas asset. Phantom signs an authentication message with your Robinhood Chain EVM address; no transaction or spending approval is requested. EVM compatibility helps builders reuse familiar tools, but it does not prove every Ethereum or Arbitrum feature is deployed and supported. Ultron's context packs preserve those distinctions. ## Understand the stock behind the token. Look up issuer assets, quote timestamps and corporate-action multipliers. Compare reference information with indexed pool observations while keeping units and market structure clear. A stock-themed token is not automatically an issuer stock token. Direct mint/burn and issuer access require separate authorization. Ultron helps you build around the data; it does not issue securities or grant redemption access. [Tokenized-stock mechanics](/docs/stock-tokens) ## Independent, and explicit about it. Ultron is not affiliated with Robinhood. Its name, visual identity and tools belong to an independent product. It uses documented public interfaces and third-party data with their own availability and terms. [Explore the tool reference](/docs/tools) # Security and access Protected connections. Your keys and decisions stay yours. ## Your wallet stays yours. Sign-in proves wallet ownership. It does not authorize trades or spending. ## Control your access. Use the secure connection form for provider keys. Review paid research, revoke access and manage your data from your workspace. ## Security and access Protected connections and account access. No service can promise complete security. [Privacy and data controls](/privacy) # Your data What Ultron stores, which providers receive your queries, and how to revoke access or delete your account. ## What we store Ultron stores your public wallet identity, hashed session/access credentials, account preferences, conversations, monitor settings, saved wallet labels, supplied trade records, research routines, events and request metadata. It does not request wallet private keys or seed phrases. Optional model and research API keys are encrypted and bound to your account and provider. Optional messaging connections store platform identifiers and delivery records needed to serve previously linked accounts. API keys belong in the encrypted connection form, never chat. ## What leaves Ultron Requested contract addresses, wallet addresses and stock symbols go to the relevant issuer API, configured chain RPC or market-data provider. News queries go to Google News RSS or a labeled Bing fallback. Approved research goes to your selected Apify or X provider; wallet history reads go to your connected Alchemy project. These providers have their own terms and retention practices. Hosted web/bot chat sends your messages, recent conversation context, preferences and relevant tool evidence to your selected model provider. A remote MCP used in another AI client follows that client's model and privacy terms. Stored provider secrets are not inserted into model context. ## Retention Request metadata, routine results and research jobs/results are retained for 30 days; inbox events for 90 days; imported FOMO observations for 24 hours. Inactive assistant conversations are removed after 90 days. Saved wallet labels and supplied accounting records persist until account deletion. Preferences and encrypted provider connections persist until reset, disconnected or the account is deleted. Authentication challenges expire after five minutes. Sessions and OAuth grants expire after seven days; access keys after 30 days. Temporary link codes expire after ten minutes. Expired records are removed by scheduled cleanup. ## Your controls Revoke Ultron keys or delete your account in workspace settings. Disconnect model/research providers and channels in Connections. Account deletion removes associated stored records. A disconnected key cannot be used for subsequent provider steps, but a request already accepted by a provider may complete. Public blockchain records and third-party logs cannot be deleted by Ultron. Do not enter secrets or unnecessary personal information in research prompts, imports or API arguments. # Using Ultron Beta service boundaries, account responsibilities and research-only operation. ## Independent beta service Ultron is an independent research and developer tool for Robinhood Chain, not an affiliate of Robinhood, Phantom, OpenAI or Anthropic. It is a beta with documented capacity and provider limits. Availability, uninterrupted delivery, complete coverage and suitability for a particular workflow are not guaranteed. ## Research and alerts; human execution Ultron does not take custody, sign on-chain transactions, submit orders or execute trades. Reference quotes, indexed pool data, contract-source matches and AI-generated explanations are informational observations, not promises of execution, token safety or returns. You remain responsible for verifying the relevant sources, asset identity, eligibility and risks before acting. Issuer access, stock-token mint/burn and product-specific permissions are not granted by using Ultron. ## Accounts and provider usage Use only accounts and credentials you are authorized to connect. Keep access keys and temporary link codes private. Provider usage is billed to the connected API account according to that provider's terms. Consumer AI subscriptions do not automatically include API usage. Paid research requires browser approval of an exact request. An uncertain upstream outcome can still incur a charge; check the provider before initiating another request. Do not use the service to bypass platform controls or manipulate market activity. ## Service limits and support boundaries Rate limits, watch limits, retention and current missing capabilities are documented in the limits guide. The service may reject or pause requests when providers fail, identities change or required evidence is unavailable. Do not treat an unavailable observation as a zero value. These beta terms describe the current product's operating boundaries. No security certification, independent contract audit, brokerage service, guaranteed profitability or unlimited usage is represented. [Limits and readiness](/docs/limits) · [Privacy](/privacy) # get_forecast_status Read current or completed Jev experiment status, cost and evidence limits. ## Ultron forecasting experiment Read current or completed Jev experiment status, cost and evidence limits. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_forecast_status Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_market_forecast Read the selected market forecast at a supported horizon. Report expiry and uncertainty; never treat as a trade instruction. ## Ultron multi-horizon forecast Read the selected market forecast at a supported horizon. Report expiry and uncertainty; never treat as a trade instruction. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_market_forecast Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "horizonSeconds": { "anyOf": [ { "type": "number", "const": 60 }, { "type": "number", "const": 300 }, { "type": "number", "const": 600 }, { "type": "number", "const": 1200 }, { "type": "number", "const": 1800 } ] } }, "required": [ "horizonSeconds" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_forecast_results Read scored outcomes, raw/calibrated comparisons and experiment notes. ## Ultron forecast scorecard Read scored outcomes, raw/calibrated comparisons and experiment notes. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_forecast_results Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # open_ultron_workspace Open interactive markets, token charts, wallet history, watch reviews, research approvals and builder recipes inside your AI. Reuse workspaceId when reopening the same conversation view. ## Open Ultron research workspace Open interactive markets, token charts, wallet history, watch reviews, research approvals and builder recipes inside your AI. Reuse workspaceId when reopening the same conversation view. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/open_ultron_workspace Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "workspaceId": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" }, "initialTab": { "type": "string", "enum": [ "Markets", "Wallets", "Watches", "Research", "Builder", "Usage" ] }, "requestId": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" } }, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # open_ultron_setup Open Ultron’s embedded connection form to add, test or remove provider keys inside the AI client. No API keys in chat or tool arguments. Editing keys requires connections:write permission. ## Connect your tools inside your AI Open Ultron’s embedded connection form to add, test or remove provider keys inside the AI client. No API keys in chat or tool arguments. Editing keys requires connections:write permission. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/open_ultron_setup Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # check_price_moves Batch-check exact token addresses for up, down or either-direction percentage moves. Return only matching coins plus explicit missing coverage. A read is not an alert. ## Check the listed coins for a 1h move Batch-check exact token addresses for up, down or either-direction percentage moves. Return only matching coins plus explicit missing coverage. A read is not an alert. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/check_price_moves Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "tokens": { "minItems": 1, "maxItems": 20, "type": "array", "items": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } }, "thresholdPercent": { "default": 30, "type": "number", "exclusiveMinimum": 0, "maximum": 1000000 }, "direction": { "default": "either", "type": "string", "enum": [ "up", "down", "either" ] } }, "required": [ "tokens", "thresholdPercent", "direction" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_trader_capabilities List 50 concrete questions, workflows and routines with their tools, data prerequisites and evidence limits. ## What Ultron can do List 50 concrete questions, workflows and routines with their tools, data prerequisites and evidence limits. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_trader_capabilities Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # find_similar_projects Compare a named project or product idea with Ultron’s private historical Robinhood research. Explains shared utility, token economics, dated outcomes and differences. When no good match exists, follow its native web-search fallback immediately. ## Find similar historical projects Compare a named project or product idea with Ultron’s private historical Robinhood research. Explains shared utility, token economics, dated outcomes and differences. When no good match exists, follow its native web-search fallback immediately. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/find_similar_projects Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "query": { "type": "string", "minLength": 2, "maxLength": 180 }, "audience": { "default": "both", "type": "string", "enum": [ "trader", "builder", "both" ] }, "limit": { "default": 3, "type": "integer", "minimum": 1, "maximum": 5 }, "includeOtherChains": { "default": false, "type": "boolean" } }, "required": [ "query", "audience", "limit", "includeOtherChains" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # search_robinhood_research Retrieve a small relevant excerpt from Ultron’s private curated research. Historical context only; no bulk export or current-price claims. ## Consult Ultron research Retrieve a small relevant excerpt from Ultron’s private curated research. Historical context only; no bulk export or current-price claims. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/search_robinhood_research Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "query": { "type": "string", "minLength": 2, "maxLength": 180 }, "audience": { "default": "both", "type": "string", "enum": [ "trader", "builder", "both" ] }, "limit": { "default": 3, "type": "integer", "minimum": 1, "maximum": 5 }, "includeOtherChains": { "default": false, "type": "boolean" } }, "required": [ "query", "audience", "limit", "includeOtherChains" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_market_leaders Current trending, gainers, losers, volume or new-pool sample. Exact two-hour/day rankings use historical candles for a bounded subset. ## Robinhood market leaders Current trending, gainers, losers, volume or new-pool sample. Exact two-hour/day rankings use historical candles for a bounded subset. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_market_leaders Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "sort": { "default": "trending", "type": "string", "enum": [ "trending", "gainers", "losers", "volume", "new" ] }, "window": { "default": "h24", "type": "string", "enum": [ "m5", "h1", "h6", "h24", "h2", "h3", "today" ] }, "includeMajorAssets": { "default": false, "type": "boolean" }, "minAbsPriceChangePercent": { "type": "number", "minimum": 0, "maximum": 1000000 }, "minLiquidityUsd": { "default": 10000, "type": "number", "minimum": 0, "maximum": 1000000000000 }, "minMarketCapUsd": { "type": "number", "minimum": 0 }, "maxMarketCapUsd": { "type": "number", "exclusiveMinimum": 0 }, "quoteToken": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "pages": { "default": 2, "type": "integer", "minimum": 1, "maximum": 3 }, "limit": { "default": 8, "type": "integer", "minimum": 1, "maximum": 15 }, "timezone": { "default": "UTC", "type": "string", "maxLength": 80 } }, "required": [ "sort", "window", "includeMajorAssets", "minLiquidityUsd", "pages", "limit", "timezone" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_market_history Read verified-pool OHLCV and summarize complete candles. Missing coverage is explicit; no rolling-volume subtraction. ## Historical pool data Read verified-pool OHLCV and summarize complete candles. Missing coverage is explicit; no rolling-volume subtraction. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_market_history Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "pool": { "type": "string", "pattern": "^0x(?:[0-9a-fA-F]{40}|[0-9a-fA-F]{64})$" }, "from": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "to": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "interval": { "default": "minute", "type": "string", "enum": [ "minute", "hour" ] } }, "required": [ "pool", "from", "interval" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # compare_market_windows Compare equal-duration hourly or calendar-day windows with historical candles and timezone-aware boundaries. ## Compare market windows Compare equal-duration hourly or calendar-day windows with historical candles and timezone-aware boundaries. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/compare_market_windows Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "pool": { "type": "string", "pattern": "^0x(?:[0-9a-fA-F]{40}|[0-9a-fA-F]{64})$" }, "mode": { "default": "today_vs_yesterday", "type": "string", "enum": [ "today_vs_yesterday", "last_hour", "last_2_hours", "last_6_hours" ] }, "timezone": { "default": "UTC", "type": "string", "maxLength": 80 } }, "required": [ "pool", "mode", "timezone" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # remember_wallet Save a user-confirmed Robinhood address label for this account. Does not establish real-world ownership. ## Name a watched wallet Save a user-confirmed Robinhood address label for this account. Does not establish real-world ownership. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/remember_wallet Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "address": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "label": { "type": "string", "minLength": 1, "maxLength": 60 } }, "required": [ "address", "label" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # list_watched_wallets List only your account’s watched address labels. ## My named wallets List only your account’s watched address labels. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/list_watched_wallets Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_wallet_activity Read timestamped Alchemy native/ERC-20 transfers using the user’s encrypted key and approved daily request budget. No other-chain substitution. ## Wallet activity history Read timestamped Alchemy native/ERC-20 transfers using the user’s encrypted key and approved daily request budget. No other-chain substitution. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_wallet_activity Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "wallet": { "type": "string", "minLength": 1, "maxLength": 80 }, "hours": { "default": 6, "type": "number", "minimum": 0.05, "maximum": 168 }, "to": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "maxPages": { "default": 1, "type": "integer", "minimum": 1, "maximum": 3 }, "cursor": { "type": "object", "properties": { "incoming": { "type": "string", "maxLength": 200 }, "outgoing": { "type": "string", "maxLength": 200 } }, "additionalProperties": false } }, "required": [ "wallet", "hours", "maxPages" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_wallet_flows Group wallet transfers by transaction. Opposing flows are swap/contract-interaction candidates, not proven purchases or profits. ## Investigate wallet trades Group wallet transfers by transaction. Opposing flows are swap/contract-interaction candidates, not proven purchases or profits. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_wallet_flows Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "wallet": { "type": "string", "minLength": 1, "maxLength": 80 }, "hours": { "default": 6, "type": "number", "minimum": 0.05, "maximum": 168 }, "to": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "maxPages": { "default": 1, "type": "integer", "minimum": 1, "maximum": 3 }, "cursor": { "type": "object", "properties": { "incoming": { "type": "string", "maxLength": 200 }, "outgoing": { "type": "string", "maxLength": 200 } }, "additionalProperties": false } }, "required": [ "wallet", "hours", "maxPages" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_wallet_holdings Read bounded Alchemy raw ERC-20 balances. Explicit truncation; metadata and prices require separate verification. ## Discover wallet tokens Read bounded Alchemy raw ERC-20 balances. Explicit truncation; metadata and prices require separate verification. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_wallet_holdings Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "wallet": { "type": "string", "minLength": 1, "maxLength": 80 } }, "required": [ "wallet" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_funding_clues Compare recent native funders across at most five wallets. Shared funding does not prove common ownership. ## Compare wallet funding Compare recent native funders across at most five wallets. Shared funding does not prove common ownership. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_funding_clues Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "wallets": { "minItems": 2, "maxItems": 5, "type": "array", "items": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } }, "hours": { "default": 24, "type": "number", "minimum": 1, "maximum": 168 } }, "required": [ "wallets", "hours" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # record_wallet_trade Store a user-supplied accounting record with quantity, USD consideration and provenance. Never invent a fill or cost basis. ## Record verified cost basis Store a user-supplied accounting record with quantity, USD consideration and provenance. Never invent a fill or cost basis. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/record_wallet_trade Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "wallet": { "type": "string", "maxLength": 80 }, "token": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "kind": { "type": "string", "enum": [ "buy", "sell", "transfer_in", "transfer_out" ] }, "quantity": { "type": "string", "pattern": "^\\d{1,36}(?:\\.\\d{1,18})?$" }, "usdValue": { "type": "string", "pattern": "^\\d{1,36}(?:\\.\\d{1,18})?$" }, "occurredAt": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "txHash": { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$" }, "requestKey": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" }, "source": { "default": "user_statement", "type": "string", "enum": [ "user_statement", "user_verified_trade" ] } }, "required": [ "wallet", "token", "kind", "quantity", "occurredAt", "requestKey", "source" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_wallet_pnl Calculate exact-decimal FIFO and mark-to-market from recorded trades. Unknown basis makes total PnL unavailable. ## Position accounting Calculate exact-decimal FIFO and mark-to-market from recorded trades. Unknown basis makes total PnL unavailable. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_wallet_pnl Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "wallet": { "type": "string", "maxLength": 80 }, "token": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "markPriceUsd": { "type": "string", "pattern": "^\\d{1,36}(?:\\.\\d{1,18})?$" }, "pool": { "type": "string", "pattern": "^0x(?:[0-9a-fA-F]{40}|[0-9a-fA-F]{64})$" } }, "required": [ "wallet", "token" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_trader_brief Combine exact-token market data, supplied FOMO observations, approved social results and authenticated research context. ## Token research brief Combine exact-token market data, supplied FOMO observations, approved social results and authenticated research context. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_trader_brief Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "token": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "query": { "type": "string", "minLength": 2, "maxLength": 100 } }, "required": [ "token" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # run_trench_radar Discover market candidates without waiting for user token names, incorporate recent supplied FOMO and approved exact-token social evidence. No paid calls started. ## Scan Robinhood confluence Discover market candidates without waiting for user token names, incorporate recent supplied FOMO and approved exact-token social evidence. No paid calls started. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/run_trench_radar Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "minLiquidityUsd": { "default": 25000, "type": "number", "minimum": 0 }, "minVolume1hUsd": { "default": 10000, "type": "number", "minimum": 0 }, "minPriceChange1hPercent": { "default": 5, "type": "number" }, "minMarketCapUsd": { "default": 1000000, "type": "number", "minimum": 0 }, "maxMarketCapUsd": { "default": 10000000, "type": "number", "exclusiveMinimum": 0 }, "limit": { "default": 6, "type": "integer", "minimum": 1, "maximum": 10 } }, "required": [ "minLiquidityUsd", "minVolume1hUsd", "minPriceChange1hPercent", "minMarketCapUsd", "maxMarketCapUsd", "limit" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # create_research_routine Create an explicitly confirmed one-shot or recurring research/reminder job. Results are retrieved by the user’s AI; host notifications require setup. ## Schedule a research routine Create an explicitly confirmed one-shot or recurring research/reminder job. Results are retrieved by the user’s AI; host notifications require setup. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/create_research_routine Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "name": { "type": "string", "minLength": 1, "maxLength": 80 }, "kind": { "type": "string", "enum": [ "market_cap_crossing", "market_leaders", "trench_watch", "token_pulse", "wallet_activity", "reminder" ] }, "config": { "default": {}, "type": "object", "propertyNames": { "type": "string" }, "additionalProperties": {} }, "firstRunAt": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "intervalMinutes": { "type": "integer", "minimum": 5, "maximum": 10080 }, "expiresAt": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "confirm": { "type": "boolean", "const": true } }, "required": [ "name", "kind", "config", "firstRunAt", "confirm" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # list_research_routines List only your routines and schedules. ## My research routines List only your routines and schedules. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/list_research_routines Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_routine_results Read unacknowledged account-owned routine results for delivery in the AI host. Deduplicate by result ID. ## Read routine results Read unacknowledged account-owned routine results for delivery in the AI host. Deduplicate by result ID. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_routine_results Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "after": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "limit": { "default": 20, "type": "integer", "minimum": 1, "maximum": 50 }, "unacknowledgedOnly": { "default": true, "type": "boolean" } }, "required": [ "limit", "unacknowledgedOnly" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # set_research_routine_active Change an owned routine and fence off any in-flight result. ## Pause or resume research Change an owned routine and fence off any in-flight result. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/set_research_routine_active Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" }, "active": { "type": "boolean" } }, "required": [ "id", "active" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # delete_research_routine Delete only an owned routine and its retained results. ## Delete a research routine Delete only an owned routine and its retained results. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/delete_research_routine Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" } }, "required": [ "id" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # acknowledge_routine_result Mark only your own result after it was successfully reported by the AI host. ## Acknowledge a delivered result Mark only your own result after it was successfully reported by the AI host. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/acknowledge_routine_result Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" } }, "required": [ "id" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # onboard_ultron Use when the user says Hi Ultron, Hey Ultron or explicitly asks to start Ultron; a generic hi alone is not a trigger; call with {} to read saved setup and return one next question. Use suggestedReply and the connectionChecklist with signup links, examples and what each key unlocks. Ask which to connect first; no naming or role questionnaire before that. Resume existing users without restarting. Personalize the assistant, learn the user’s role and goal, explain relevant capabilities and guide optional secure connections. No passwords, no secret extraction, no trades. ## Say hi to Ultron — start or resume Use when the user says Hi Ultron, Hey Ultron or explicitly asks to start Ultron; a generic hi alone is not a trigger; call with {} to read saved setup and return one next question. Use suggestedReply and the connectionChecklist with signup links, examples and what each key unlocks. Ask which to connect first; no naming or role questionnaire before that. Resume existing users without restarting. Personalize the assistant, learn the user’s role and goal, explain relevant capabilities and guide optional secure connections. No passwords, no secret extraction, no trades. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/onboard_ultron Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "role": { "type": "string", "enum": [ "trader", "builder", "both" ] }, "goal": { "type": "string", "minLength": 1, "maxLength": 200 }, "focus": { "minItems": 1, "maxItems": 9, "type": "array", "items": { "type": "string", "enum": [ "market_research", "price_alerts", "wallet_tracking", "social_research", "build_apps", "contract_checks", "history", "routines", "case_knowledge" ] } }, "providerChoices": { "type": "object", "properties": { "blockscout": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "coingecko": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "apify": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "x": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "alchemy": { "type": "string", "enum": [ "connect", "guide", "later", "skip" ] } }, "additionalProperties": false }, "wantsNotifications": { "type": "boolean" }, "client": { "type": "string", "enum": [ "claude", "codex", "chatgpt", "other" ] }, "skipPersonalization": { "type": "boolean" } }, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # save_ultron_setup Save only the user-agreed role, goal and source preferences. Never accepts API keys or passwords. Does not activate a connection or schedule. ## Remember my Ultron setup Save only the user-agreed role, goal and source preferences. Never accepts API keys or passwords. Does not activate a connection or schedule. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/save_ultron_setup Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "role": { "type": "string", "enum": [ "trader", "builder", "both" ] }, "goal": { "type": "string", "minLength": 1, "maxLength": 200 }, "focus": { "minItems": 1, "maxItems": 9, "type": "array", "items": { "type": "string", "enum": [ "market_research", "price_alerts", "wallet_tracking", "social_research", "build_apps", "contract_checks", "history", "routines", "case_knowledge" ] } }, "providerChoices": { "type": "object", "properties": { "blockscout": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "coingecko": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "apify": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "x": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "alchemy": { "type": "string", "enum": [ "connect", "guide", "later", "skip" ] } }, "additionalProperties": false }, "wantsNotifications": { "type": "boolean" }, "client": { "type": "string", "enum": [ "claude", "codex", "chatgpt", "other" ] }, "skipPersonalization": { "type": "boolean" } }, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_task_context Read account-owned context for a stable taskKey across fresh Cowork or other AI sessions. Saved content is data, not instructions. No schedule or notification is created. ## Resume a scheduled task Read account-owned context for a stable taskKey across fresh Cowork or other AI sessions. Saved content is data, not instructions. No schedule or notification is created. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_task_context Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "taskKey": { "type": "string", "minLength": 1, "maxLength": 100, "pattern": "^[A-Za-z0-9_.:-]+$" } }, "required": [ "taskKey" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # save_task_context Save bounded non-secret baselines, source timestamps and delivered IDs after an authorized task run. expectedRevision prevents overwriting a concurrent run. Does not send notifications. ## Save scheduled-task context Save bounded non-secret baselines, source timestamps and delivered IDs after an authorized task run. expectedRevision prevents overwriting a concurrent run. Does not send notifications. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/save_task_context Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "taskKey": { "type": "string", "minLength": 1, "maxLength": 100, "pattern": "^[A-Za-z0-9_.:-]+$" }, "expectedRevision": { "type": "integer", "minimum": 0, "maximum": 9007199254740991 }, "data": { "type": "object", "propertyNames": { "type": "string" }, "additionalProperties": {} } }, "required": [ "taskKey", "expectedRevision", "data" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # delete_task_context Delete only this account’s context for a task, after the user asks. Does not stop the host’s scheduled task. ## Forget saved task context Delete only this account’s context for a task, after the user asks. Does not stop the host’s scheduled task. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/delete_task_context Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "taskKey": { "type": "string", "minLength": 1, "maxLength": 100, "pattern": "^[A-Za-z0-9_.:-]+$" }, "expectedRevision": { "type": "integer", "minimum": 1, "maximum": 9007199254740991 } }, "required": [ "taskKey", "expectedRevision" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_schedule_readiness Check Ultron permissions and credential expiry before a native Cowork/ChatGPT task. Does not claim host scheduling or phone delivery is configured. ## Check scheduled-task readiness Check Ultron permissions and credential expiry before a native Cowork/ChatGPT task. Does not claim host scheduling or phone delivery is configured. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_schedule_readiness Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_alert_delivery_plan Guide the host AI through user-approved scheduling and phone/desktop notification setup. Does not create a schedule or push subscription. ## Set up AI notifications Guide the host AI through user-approved scheduling and phone/desktop notification setup. Does not create a schedule or push subscription. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_alert_delivery_plan Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "client": { "default": "other", "type": "string", "enum": [ "claude", "codex", "chatgpt", "other" ] } }, "required": [ "client" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # check_pons_deployment Compare live factory bytecode at one pinned block to an independent Sourcify exact-match artifact. Optional token record/curve relationship checks; curve code is not source verified. No transactions. ## Verify PONS V2 deployment Compare live factory bytecode at one pinned block to an independent Sourcify exact-match artifact. Optional token record/curve relationship checks; curve code is not source verified. No transactions. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/check_pons_deployment Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "token": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } }, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_research_connections Check Apify and X research setup. No Nansen onboarding for Robinhood. Keys belong only in the secure form. ## Research setup Check Apify and X research setup. No Nansen onboarding for Robinhood. Keys belong only in the secure form. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_research_connections Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # propose_research Prepare one Nansen label lookup, small TikTok hashtag run or bounded X counts/search and open an embedded approval panel inside the AI. Does not spend or run. Robinhood Nansen labels unsupported. ## Prepare paid research Prepare one Nansen label lookup, small TikTok hashtag run or bounded X counts/search and open an embedded approval panel inside the AI. Does not spend or run. Robinhood Nansen labels unsupported. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/propose_research Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "provider": { "type": "string", "enum": [ "nansen", "apify", "x" ] }, "requestKey": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" }, "query": { "type": "string", "minLength": 1, "maxLength": 160 }, "token": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "address": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "chain": { "type": "string", "enum": [ "ethereum", "base", "arbitrum", "bnb", "optimism", "polygon", "avalanche", "robinhood" ] }, "maxChargeUsd": { "description": "Apify actor maximum charge only. Nansen and X endpoints do not enforce this dollar cap; their provider prices require separate human review.", "type": "number", "minimum": 0.01, "maximum": 0.25 } }, "required": [ "provider", "requestKey" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # list_research_requests List your proposed/running/completed research requests and results. ## Research requests List your proposed/running/completed research requests and results. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/list_research_requests Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_research_result Read an account-owned request; poll an already approved Apify run. Never starts another paid run. ## Research result Read an account-owned request; poll an already approved Apify run. Never starts another paid run. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_research_result Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" } }, "required": [ "id" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # search_stock_news Search a bounded two-day news RSS sample (Google, then Bing fallback). Headlines are leads, not verified token catalysts. ## Stock and narrative headlines Search a bounded two-day news RSS sample (Google, then Bing fallback). Headlines are leads, not verified token catalysts. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/search_stock_news Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "query": { "type": "string", "minLength": 2, "maxLength": 100 } }, "required": [ "query" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # import_fomo_snapshot Save a recent user/agent-observed Robinhood FOMO board or named public action. Unverified snapshot, not an API feed. Never send cookies or viewer positions. ## Import observed FOMO board Save a recent user/agent-observed Robinhood FOMO board or named public action. Unverified snapshot, not an API feed. Never send cookies or viewer positions. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/import_fomo_snapshot Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "sourceUrl": { "type": "string", "maxLength": 300, "format": "uri" }, "observedAt": { "type": "string", "format": "date-time", "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$" }, "rows": { "minItems": 1, "maxItems": 30, "type": "array", "items": { "type": "object", "properties": { "token": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "chainId": { "type": "number", "const": 4663 }, "symbol": { "type": "string", "maxLength": 40 }, "heat": { "type": "number", "minimum": 0 }, "buyerHandle": { "type": "string", "pattern": "^[a-zA-Z0-9_.-]{1,60}$" }, "action": { "default": "board", "type": "string", "enum": [ "board", "buy", "sell" ] } }, "required": [ "token", "chainId", "symbol", "action" ], "additionalProperties": false } } }, "required": [ "sourceUrl", "observedAt", "rows" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_research_evidence Read only your FOMO observations with age, chain, token and provenance; stale evidence stays explicit. ## Imported research evidence Read only your FOMO observations with age, chain, token and provenance; stale evidence stays explicit. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_research_evidence Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "token": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } }, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # evaluate_market_signal Check all volume, momentum, liquidity and optional market-cap conditions on one exact Robinhood pair. No trading. ## Check market confluence Check all volume, momentum, liquidity and optional market-cap conditions on one exact Robinhood pair. No trading. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/evaluate_market_signal Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "pair": { "type": "string", "pattern": "^0x(?:[0-9a-fA-F]{40}|[0-9a-fA-F]{64})$" }, "conditions": { "type": "object", "properties": { "priceMovementDirection": { "default": "up", "type": "string", "enum": [ "up", "down", "either" ] }, "minVolume1hUsd": { "type": "number", "minimum": 0, "maximum": 1000000000000 }, "minPriceChange1hPercent": { "type": "number", "minimum": 0, "maximum": 100000 }, "minLiquidityUsd": { "type": "number", "minimum": 0, "maximum": 1000000000000 }, "minMarketCapUsd": { "type": "number", "minimum": 0, "maximum": 1000000000000000 }, "maxMarketCapUsd": { "type": "number", "minimum": 1, "maximum": 1000000000000000 } }, "required": [ "priceMovementDirection", "minVolume1hUsd", "minPriceChange1hPercent", "minLiquidityUsd" ], "additionalProperties": false } }, "required": [ "pair", "conditions" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # network_status Check Robinhood mainnet identity and current RPC block. ## Network status Check Robinhood mainnet identity and current RPC block. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/network_status Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # search_stock_assets Search the official Robinhood issuer registry. Results are strictly chain 4663. ## Find stock tokens Search the official Robinhood issuer registry. Results are strictly chain 4663. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/search_stock_assets Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "query": { "default": "", "type": "string", "maxLength": 80 }, "limit": { "default": 20, "type": "integer", "minimum": 1, "maximum": 50 } }, "required": [ "query", "limit" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_stock_asset Get a single issuer asset by exact ticker or contract address; includes multiplier and restrictions metadata. ## Stock token identity Get a single issuer asset by exact ticker or contract address; includes multiplier and restrictions metadata. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_stock_asset Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "asset": { "type": "string", "minLength": 1, "maxLength": 70 } }, "required": [ "asset" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_stock_quote Underlying-equity bid/ask and multiplier-adjusted token values. Not an executable quote; explicit freshness and unknown session status. ## Stock reference quote Underlying-equity bid/ask and multiplier-adjusted token values. Not an executable quote; explicit freshness and unknown session status. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_stock_quote Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "asset": { "type": "string", "minLength": 1, "maxLength": 70 } }, "required": [ "asset" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_corporate_actions Read issuer corporate-action history. processDate is not a guaranteed payable date. ## Corporate actions Read issuer corporate-action history. processDate is not a guaranteed payable date. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_corporate_actions Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "symbol": { "type": "string", "maxLength": 20 } }, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # inspect_token Read ERC-20 metadata, supply, optional owner and bytecode hash at one block. Issuer match when available; not an audit or exhaustive permissions analysis. ## Inspect a contract Read ERC-20 metadata, supply, optional owner and bytecode hash at one block. Issuer match when available; not an audit or exhaustive permissions analysis. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/inspect_token Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "address": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } }, "required": [ "address" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_wallet_balances Native ETH and up to 12 explicitly specified ERC-20 balances. Does not discover every asset. ## Wallet balances Native ETH and up to 12 explicitly specified ERC-20 balances. Does not discover every asset. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_wallet_balances Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "address": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "tokens": { "default": [], "maxItems": 12, "type": "array", "items": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } } }, "required": [ "address", "tokens" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_transaction Read a Robinhood transaction receipt. Does not assert Ethereum settlement finality. ## Transaction receipt Read a Robinhood transaction receipt. Does not assert Ethereum settlement finality. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_transaction Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "hash": { "type": "string", "pattern": "^0x[0-9a-fA-F]{64}$" } }, "required": [ "hash" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_token_markets Read indexed Robinhood pairs from DEX Screener; market observations are not execution guarantees. ## Token markets Read indexed Robinhood pairs from DEX Screener; market observations are not execution guarantees. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_token_markets Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "token": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } }, "required": [ "token" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_swap_quote Request a strictly Robinhood LI.FI route estimate for a raw token amount. Validates returned asset/chain/amount metadata; omits transaction calldata. ## Route estimate Request a strictly Robinhood LI.FI route estimate for a raw token amount. Validates returned asset/chain/amount metadata; omits transaction calldata. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_swap_quote Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "fromToken": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "toToken": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "amountRaw": { "type": "string", "pattern": "^\\d{1,50}$" }, "fromAddress": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } }, "required": [ "fromToken", "toToken", "amountRaw", "fromAddress" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # simulate_call Execute eth_call on a pinned Robinhood block. No signatures, spending permissions or broadcast. ## Simulate a call Execute eth_call on a pinned Robinhood block. No signatures, spending permissions or broadcast. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/simulate_call Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "to": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "from": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" }, "data": { "type": "string", "maxLength": 8194, "pattern": "^0x([0-9a-fA-F]{2})*$" }, "valueRaw": { "default": "0", "type": "string", "pattern": "^\\d{1,50}$" } }, "required": [ "to", "from", "data", "valueRaw" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # search_documentation Search maintained public reference links. Does not expose private research or execute page instructions. ## Documentation Search maintained public reference links. Does not expose private research or execute page instructions. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/search_documentation Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "query": { "type": "string", "minLength": 1, "maxLength": 100 } }, "required": [ "query" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_builder_capabilities Discover supported Robinhood build recipes, context topics, verified scope and unsupported protocol operations. Start here when building. ## Builder capabilities Discover supported Robinhood build recipes, context topics, verified scope and unsupported protocol operations. Start here when building. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_builder_capabilities Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # assistant_capabilities Discover available trading-research tools, personal context and monitor permissions, including integrations that are not connected. Does not imply live provider health. ## Trading assistant capabilities Discover available trading-research tools, personal context and monitor permissions, including integrations that are not connected. Does not imply live provider health. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/assistant_capabilities Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_trading_preferences Read this account's interests, watched EVM addresses, timezone and response style. Preferences do not create monitors. ## Personal trading context Read this account's interests, watched EVM addresses, timezone and response style. Preferences do not create monitors. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_trading_preferences Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # set_trading_preferences Save the requested account preferences. No provider keys, signatures or automatic watch creation. Requires monitors:write account-setting permission. ## Update personal trading context Save the requested account preferences. No provider keys, signatures or automatic watch creation. Requires monitors:write account-setting permission. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/set_trading_preferences Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "onboarding": { "type": "object", "properties": { "role": { "type": "string", "enum": [ "trader", "builder", "both" ] }, "goal": { "type": "string", "minLength": 1, "maxLength": 200 }, "focus": { "minItems": 1, "maxItems": 9, "type": "array", "items": { "type": "string", "enum": [ "market_research", "price_alerts", "wallet_tracking", "social_research", "build_apps", "contract_checks", "history", "routines", "case_knowledge" ] } }, "providerChoices": { "type": "object", "properties": { "blockscout": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "coingecko": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "apify": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "x": { "type": "string", "enum": [ "connect", "later", "skip" ] }, "alchemy": { "type": "string", "enum": [ "connect", "guide", "later", "skip" ] } }, "additionalProperties": false }, "wantsNotifications": { "type": "boolean" }, "client": { "type": "string", "enum": [ "claude", "codex", "chatgpt", "other" ] }, "skipPersonalization": { "type": "boolean" } }, "additionalProperties": false }, "interests": { "maxItems": 12, "type": "array", "items": { "type": "string", "minLength": 1, "maxLength": 100 } }, "watchedAddresses": { "maxItems": 20, "type": "array", "items": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } }, "timezone": { "type": "string", "maxLength": 70 }, "responseStyle": { "type": "string", "enum": [ "brief", "detailed" ] } }, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_build_recipe Return a task-specific implementation plan, source-linked context, acceptance checks and fixture-tested server-side JavaScript. Does not deploy or create account state. ## Get an integration recipe Return a task-specific implementation plan, source-linked context, acceptance checks and fixture-tested server-side JavaScript. Does not deploy or create account state. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_build_recipe Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "recipe": { "type": "string", "enum": [ "stock_accounting", "oracle_guard", "event_indexer", "market_compare", "deployment_review", "pons_curve_read", "stock_dashboard", "wallet_view", "simulate_contract", "persistent_monitor" ] }, "includeExample": { "default": true, "type": "boolean" } }, "required": [ "recipe", "includeExample" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_integration_context Retrieve reviewed network, stock-unit, market-data, monitoring or authentication semantics. Explicit review version and freshness caveats; not private research search. ## Focused Robinhood context Retrieve reviewed network, stock-unit, market-data, monitoring or authentication semantics. Explicit review version and freshness caveats; not private research search. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_integration_context Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "topic": { "type": "string", "enum": [ "oracles", "finality", "indexing", "deployment", "account_abstraction", "bridging", "pons_v2", "stock_accounting", "service_quality", "network", "stock_units", "market_data", "monitoring", "authentication" ] } }, "required": [ "topic" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # troubleshoot_integration Get bounded diagnostic checks and relevant live tool names for a known issue category. Does not claim a diagnosis without evidence. ## Diagnose an integration issue Get bounded diagnostic checks and relevant live tool names for a known issue category. Does not claim a diagnosis without evidence. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/troubleshoot_integration Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "issue": { "type": "string", "enum": [ "wrong_chain", "double_multiplier", "stale_quote", "missing_balance", "call_reverted", "missing_alert", "unauthorized", "provider_unavailable", "unsupported_protocol" ] } }, "required": [ "issue" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # search_builder_knowledge Retrieve focused public-derived Robinhood context with source URLs, evidence levels and review versions. ## Search builder knowledge Retrieve focused public-derived Robinhood context with source URLs, evidence levels and review versions. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/search_builder_knowledge Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "query": { "type": "string", "minLength": 2, "maxLength": 500 }, "limit": { "default": 5, "type": "integer", "minimum": 1, "maximum": 8 } }, "required": [ "query", "limit" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # plan_robinhood_build Map a concrete goal to supported recipes, prerequisites and explicit unsupported dependencies. ## Plan a Robinhood integration Map a concrete goal to supported recipes, prerequisites and explicit unsupported dependencies. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/plan_robinhood_build Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "goal": { "type": "string", "minLength": 5, "maxLength": 1200 }, "includeExamples": { "default": false, "type": "boolean" } }, "required": [ "goal", "includeExamples" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # check_builder_prerequisites Run read-only checks for the selected recipe; source and account access failures are explicit. ## Check integration prerequisites Run read-only checks for the selected recipe; source and account access failures are explicit. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/check_builder_prerequisites Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "recipe": { "type": "string", "enum": [ "stock_accounting", "oracle_guard", "event_indexer", "market_compare", "deployment_review", "pons_curve_read", "stock_dashboard", "wallet_view", "simulate_contract", "persistent_monitor" ] } }, "required": [ "recipe" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # discover_market_candidates Search indexed Robinhood pairs and public profile/boost feeds. Rankings apply only to sampled candidates; paid boosts are advertisements, not endorsements. ## Discover sampled market candidates Search indexed Robinhood pairs and public profile/boost feeds. Rankings apply only to sampled candidates; paid boosts are advertisements, not endorsements. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/discover_market_candidates Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "query": { "type": "string", "minLength": 1, "maxLength": 80 }, "includeMajorAssets": { "default": false, "type": "boolean" }, "sortBy": { "default": "volume24h", "type": "string", "enum": [ "volume24h", "liquidity", "priceChange24h" ] }, "direction": { "default": "desc", "type": "string", "enum": [ "asc", "desc" ] }, "minLiquidityUsd": { "default": 0, "type": "number", "minimum": 0, "maximum": 1000000000000000 }, "minVolume24hUsd": { "default": 0, "type": "number", "minimum": 0, "maximum": 1000000000000000 }, "limit": { "default": 15, "type": "integer", "minimum": 1, "maximum": 30 } }, "required": [ "includeMajorAssets", "sortBy", "direction", "minLiquidityUsd", "minVolume24hUsd", "limit" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_token_holders Get ranked holder addresses and their percentage of total supply for an exact Robinhood ERC-20 token. Requires the user’s Blockscout key. Includes contracts and burn addresses; not beneficial ownership or circulating supply. ## Analyze top token holders Get ranked holder addresses and their percentage of total supply for an exact Robinhood ERC-20 token. Requires the user’s Blockscout key. Includes contracts and burn addresses; not beneficial ownership or circulating supply. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_token_holders Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "token": { "type": "string", "pattern": "^0x[\\da-fA-F]{40}$" }, "top": { "default": 10, "type": "integer", "minimum": 1, "maximum": 50 } }, "required": [ "token", "top" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_token_report Combine contract inspection and indexed markets with provenance, missing checks, and distinct market cap/FDV. Not a security audit or buy recommendation. ## Research an exact token Combine contract inspection and indexed markets with provenance, missing checks, and distinct market cap/FDV. Not a security audit or buy recommendation. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_token_report Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "token": { "type": "string", "pattern": "^0x[0-9a-fA-F]{40}$" } }, "required": [ "token" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_market_pair Read an exact Robinhood pair or v4 pool with its base/quote identity, USD metrics and retrieval freshness. Not an executable quote. ## Inspect an exact pool Read an exact Robinhood pair or v4 pool with its base/quote identity, USD metrics and retrieval freshness. Not an executable quote. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_market_pair Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "pair": { "type": "string", "pattern": "^0x(?:[0-9a-fA-F]{40}|[0-9a-fA-F]{64})$" } }, "required": [ "pair" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # get_channel_status Read this account's linked channels and delivery/job state. Does not reveal bot credentials or enable notifications. ## Your channel connections Read this account's linked channels and delivery/job state. Does not reveal bot credentials or enable notifications. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/get_channel_status Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # create_monitor Persist a stock, wallet, receipt or exact-pool price/liquidity/24h-volume watch. Events go to the account inbox and separately opted-in channel deliveries. No trading. ## Create a monitor Persist a stock, wallet, receipt or exact-pool price/liquidity/24h-volume watch. Events go to the account inbox and separately opted-in channel deliveries. No trading. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/create_monitor Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "name": { "type": "string", "minLength": 1, "maxLength": 70 }, "kind": { "type": "string", "enum": [ "stock_price", "multiplier", "native_balance", "transaction", "market_price", "market_liquidity", "market_volume", "market_signal" ] }, "target": { "type": "string", "minLength": 1, "maxLength": 70 }, "operator": { "default": "changed", "type": "string", "enum": [ "above", "below", "changed" ] }, "threshold": { "type": "number" }, "signal": { "type": "object", "properties": { "priceMovementDirection": { "default": "up", "type": "string", "enum": [ "up", "down", "either" ] }, "minVolume1hUsd": { "type": "number", "minimum": 0, "maximum": 1000000000000 }, "minPriceChange1hPercent": { "type": "number", "minimum": 0, "maximum": 100000 }, "minLiquidityUsd": { "type": "number", "minimum": 0, "maximum": 1000000000000 }, "minMarketCapUsd": { "type": "number", "minimum": 0, "maximum": 1000000000000000 }, "maxMarketCapUsd": { "type": "number", "minimum": 1, "maximum": 1000000000000000 } }, "required": [ "priceMovementDirection", "minVolume1hUsd", "minPriceChange1hPercent", "minLiquidityUsd" ], "additionalProperties": false }, "intervalSeconds": { "default": 300, "type": "integer", "minimum": 60, "maximum": 86400 } }, "required": [ "name", "kind", "target", "operator", "intervalSeconds" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # check_monitor Request an immediate check for an owned active monitor. Limited to three manual checks per minute per account. ## Check a monitor now Request an immediate check for an owned active monitor. Limited to three manual checks per minute per account. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/check_monitor Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" } }, "required": [ "id" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # list_monitors Read only monitors owned by the authenticated account. ## List monitors Read only monitors owned by the authenticated account. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/list_monitors Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": {}, "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # set_monitor_active Pause or resume one owned monitor. ## Pause or resume Pause or resume one owned monitor. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/set_monitor_active Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" }, "active": { "type": "boolean" } }, "required": [ "id", "active" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # delete_monitor Delete one owned monitor and its retained events. ## Delete a monitor Delete one owned monitor and its retained events. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/delete_monitor Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" } }, "required": [ "id" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # list_events List account-owned monitor events with a stable timestamp/id pagination cursor. ## Read monitor inbox List account-owned monitor events with a stable timestamp/id pagination cursor. ## Permission and calling convention Required scope: chain:read. This tool reads data or account-owned state. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/list_events Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "cursor": { "type": "string", "pattern": "^\\d{1,12}:[a-fA-F0-9-]{36}$" }, "limit": { "default": 30, "type": "integer", "minimum": 1, "maximum": 100 } }, "required": [ "limit" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant) # mark_event_read Mark an owned inbox event as read. ## Mark event read Mark an owned inbox event as read. ## Permission and calling convention Required scope: monitors:write. This tool can change account-owned settings or prepare a request. Use only for an intentional user action. This tool does not sign or broadcast a transaction. Check errors, source timestamps and explicit unavailable fields before using the result. ``` POST /api/tools/mark_event_read Authorization: Bearer Content-Type: application/json ``` ## Input schema Inputs are validated against this current schema. Use exact values from live source results rather than substituting a ticker for a contract or a different chain. ``` { "$schema": "https://json-schema.org/draft/2020-12/schema", "type": "object", "properties": { "id": { "type": "string", "format": "uuid", "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" } }, "required": [ "id" ], "additionalProperties": false } ``` ## Continue building Use the MCP tools/list response or /openapi.json for machine-readable discovery. For workflows and evidence boundaries, follow the appropriate guide. [REST API](/docs/api) · [Builder quickstart](/docs/builders) · [Research workflow](/docs/trading-assistant)