Monitors & compound 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":"<EXACT_PAIR_ADDRESS_OR_V4_POOL_ID>",
  "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.