Watch X for contract addresses

The bot watches X (accounts that you choose, or a search across all of X) for a token's contract address. It checks the token, buys a small amount, and exits on your usual rules. This guide shows three ways to build it, from the simplest to the fastest.

Every way ends the same. The bot looks up the token's market (a Pons or Torch token on its launchpad, any other token in its pools on UP and Uniswap). It checks your rules with the token's own values, and buys only if they hold. With Once per token on, a token is bought at most once, however often it is posted.

A. Grok searches X (simplest)Copy Anchor Link

The same strategy in the JSON tab:

{
  "schema": 1,
  "name": "X contract watch",
  "entry": {
    "trigger": { "on": "timer", "every_s": 120 },
    "target": { "token": "{{watch.token}}" },
    "ai": {
      "steps": [
        {
          "id": "watch",
          "provider": "xai",
          "search": { "x": { "handles": ["@account_one", "@account_two"], "days": 1 } },
          "prompt": "Has any of these accounts posted a token contract address on Robinhood Chain in the last 5 minutes? Give the newest one exactly as posted, or null if none. Say whether you are confident it is the account's own call, not a reply or a quote of someone else.",
          "output": { "token": "token", "confident": "boolean" }
        }
      ]
    },
    "confirm": { "and": [{ "==": [{ "f": "ai.watch.confident" }, true] }, { ">=": [{ "f": "token.liquidity" }, 3] }] },
    "buy_eth": 0.005
  },
  "exits": [
    { "if": { ">=": [{ "f": "position.multiple" }, 2] }, "reason": "take_profit", "sell_pct": 50 },
    { "if": { "<=": [{ "f": "position.pnl_pct" }, -30] }, "reason": "stop_loss" },
    { "if": { ">=": [{ "f": "position.age_s" }, 7200] }, "reason": "time" }
  ],
  "limits": { "once_per_token": true, "max_open": 3, "max_ai_runs_per_hour": 30 }
}

Cost: each run is one Grok request with X search, on your xAI key. See xAI's pricing. A 2-minute timer is 720 runs a day.

B. The X MCP server (exact posts from exact accounts)Copy Anchor Link

Grok's search filters posts by day, and it chooses what to search. X's own MCP server returns the exact posts of the accounts that you name, with their times.

{
  "id": "watch",
  "tools": ["x"],
  "prompt": "Read the latest posts of @account_one and @account_two from the last 5 minutes. Has either posted a token contract address on Robinhood Chain? Give the newest one exactly as posted, or null if none. Say whether you are confident it is the account's own call, not a reply or a quote of someone else.",
  "output": { "token": "token", "confident": "boolean" }
}

Cost: X bills each read on your bearer token (see X's pricing). The AI step costs the same as any other step on your key.

Add a check step (recommended for A and B)Copy Anchor Link

Add a second step that checks the token before the bot buys it, with a rug-risk MCP server. DeFade is one click in MCP servers.

{
  "id": "check",
  "tools": ["defade"],
  "if": { "==": [{ "f": "ai.watch.confident" }, true] },
  "prompt": "Check token {{watch.token}} on Robinhood Chain: honeypot, sell tax, holders, snipers, deployer history. Is it safe to buy a small amount?",
  "output": { "risk": ["low", "medium", "high"] }
}

Then buy only on a low risk:

"confirm": { "and": [{ "==": [{ "f": "ai.watch.confident" }, true] }, { "==": [{ "f": "ai.check.risk" }, "low"] }, { ">=": [{ "f": "token.liquidity" }, 3] }] }

The check step runs only when the first step found something (its if), so most runs cost one request. For a token that is not from a launchpad, a step can also read its contract on Blockscout: see MCP data sources.

Rules can also read the token's own values once its market is known:

• token.liquidity: the ETH in its market. It is the real ETH on a Pons curve, in a Torch pool, in a graduated Pons pool and in a v2-style pool. For other Uniswap and UP pools, it is the ETH depth near the price, which a narrow position can make look deeper than it is.
• token.buy_tax: a Torch token's tax.
• token.market_cap.

A brand-new token's liquidity is known at once. See conditions for every value.

C. Your own service and the bot's webhook (Legendary)Copy Anchor Link

For speed, run your own watcher (X's filtered stream, a Telegram listener, a chart alert) and let it call the bot the moment it sees something.

// Node.js
import crypto from "node:crypto";

const body = JSON.stringify({ token: "0x0000000000000000000000000000000000000001", score: 0.9 });
const ts = Math.floor(Date.now() / 1000).toString();
const sig = "v1=" + crypto.createHmac("sha256", process.env.SPIN_HOOK_SECRET).update(`${ts}.${body}`).digest("hex");
const res = await fetch("https://spin.trading/api/hooks/123", {
  method: "POST",
  headers: { "content-type": "application/json", "x-spin-timestamp": ts, "x-spin-signature": sig, "x-spin-event-id": postId },
  body,
});
// 202: accepted. The bot starts the entry within seconds.

The same strategy in JSON:

{
  "schema": 1,
  "name": "My X watcher",
  "entry": {
    "trigger": { "on": "webhook", "fields": { "token": "token", "score": { "number": [0, 1] } } },
    "target": { "token": "{{hook.token}}" },
    "if": { "and": [{ ">=": [{ "f": "hook.score" }, 0.7] }, { ">=": [{ "f": "token.liquidity" }, 3] }] },
    "buy_eth": 0.005
  },
  "exits": [
    { "if": { ">=": [{ "f": "position.multiple" }, 2] }, "reason": "take_profit", "sell_pct": 50 },
    { "if": { "<=": [{ "f": "position.pnl_pct" }, -30] }, "reason": "stop_loss" },
    { "if": { ">=": [{ "f": "position.age_s" }, 7200] }, "reason": "time" }
  ],
  "limits": { "once_per_token": true, "max_open": 3 }
}

Webhooks has the signing in curl and Python, every answer the webhook can give, and its limits. In short:

• The webhook refuses a call with a wrong signature, a timestamp more than 5 minutes from now, fields that the strategy does not declare, a body over 8,192 bytes, or more than 30 calls a minute or 2,000 a day.
• An event id sent twice is taken once.
• A new secret ends the old one at once, and a sale of the Spinner ends it too.
• A call can only start an entry. It cannot move or withdraw funds. Every buy still passes the strategy's rules, its limits, and the live trading limits on the Spinner's guard.
• A call that is more than 5 minutes old when the bot gets to it is dropped.

Reading the activityCopy Anchor Link

The Activity tab shows each run's AI answers, and why the bot did or did not buy: