Building a trading bot for Robinhood Chain and want a social signal from X and Telegram, delivered by webhook or MCP? This is that signal: the fresh calls of X accounts with a measured record, each with the token's deployer score, its LP custody on plan keys and, on Omega keys or x402, whether Telegram rooms carried it before X.
Most accounts that post Robinhood Chain tokens on X are echo. RobinX grades the ones it captures against the price that followed their calls: of 3,604 accounts measured on 28 October 2026 (four or more graded calls each), 146 were early on half their calls or more. The bot builder's guide, with the code, is at robinx.io/robinhood-chain-trading-bots. The signals API streams fresh calls from the accounts with that record. A measured record describes past calls: an input for your bot, not a prediction or a recommendation.
Poll. GET /signals/calls with a cursor. Tune the filter with min_rank_score (default 0.3, grade B: the 95% lower confidence bound on the early rate), min_early_rate as an optional extra, and min_calls.
Push. Signed webhooks (HMAC-SHA256) on the Omega plan.
Agents. x402 pay-per-call (USDC on Base) or the MCP server at https://api.robinx.io/mcp.
Graded callers are watched directly, so a call usually reaches the API within minutes of the post. Plans and pricing: robinx.io/pricing. Endpoint reference: robinx.io/api.
RobinX's signals API. RobinX captures the X posts that name a Robinhood Chain token, grades each caller against the on-chain price that followed, counts the Telegram rooms that carried the token, and streams the calls of measured callers to your bot over REST, signed webhooks, MCP or x402. Observations, not advice.
Yes, on the Omega plan: when a grade-B-or-better caller posts a token's contract address, the call is pushed as an HMAC-SHA256-signed webhook (daily caps apply) with the caller's record, the deployer record, LP custody and whether Telegram carried the token first. The Omega signal event adds the Telegram room count when X and three or more rooms converge. A failed delivery is retried for up to an hour with the same event id, so your bot can process each event once. Observations, not advice.
Yes: https://api.robinx.io/mcp, for Claude, ChatGPT, Cursor, the xAI API or any MCP client (a Grok Bot reads the same API through the RobinX skill), with the same calls, report cards and token checks as tools.
No. Telegram is counted, not graded: the signal records how many monitored rooms carried a token (three or more, never named) and whether Telegram led X. Only public X calls are graded against price, because they are public and timestamped.
Calls are rule-based observations from public data: inputs for your own model or bot, not predictions, recommendations or financial advice. RobinX is independent and not affiliated with Robinhood Markets, Inc.