Capabilities

Auto is built for agents that need a reliable condition engine + trigger pipeline without building that infrastructure from scratch.

Before You Build It Yourself

Agents often assume a workflow isn't supported and start building their own monitoring/trigger stack. Check this list first — most of these are already in /auto:

• "I need to compare one indicator against another live metric." Supported. Use dynamic values — the value field accepts another source/method block, not just a literal.
• "I need to trigger when multiple symbols confirm together." Supported. A single query's conditions.AND can contain conditions on BTC, ETH, SOL, etc. — up to 10 leaves, depth 3.
• "I need to trigger the moment an account posts, a Telegram channel posts, or an event breaks." Supported. Use the Signal category: source: "tweet" (X/Twitter Post), source: "telegram" (Telegram Channel), or source: "news" (Event) with text + minConfidence.
• "I need to trigger on official SEC filings for a company." Supported. Use source: "sec" with the issuer CIK to watch filing metadata such as new 8-Ks, late periodic notices, offerings, ownership filings, and 8-K item flags. See SEC Filings.
• "I need an LLM to decide whether the condition is met (not just a numeric rule)." Supported. Use source: "llm", method: "athena_condition" — give it a natural-language predicate and a schedule.
• "I need a scheduled/timed check, not a market condition." Supported. Use source: "cron" — once, every, or onceRemainTrue for intervals, or schedule for a calendar/wall-clock time (e.g. weekdays at 09:00 in a timezone). cron.schedule is authored on the direct EQL/API path today — Builder Chat support is pending.
• "I need to monitor stocks, indices, or commodities — not just crypto." Supported. Equities, indices, commodities, FX and pre-IPO names all trade as HIP-3 perps on Hyperliquid (xyz:NVDA, xyz:SP500, xyz:GOLD, xyz:CL, xyz:SPCX) — same conditions, same delivery actions, and they run 24/7 while the cash market is shut. See Catalyst Triggers.
• "I need to act on a macro catalyst — a rate decision, a CPI print, an earnings beat." Supported. Trigger on the prediction market that reprices it, then alert your runner with the asset context it moves. See Catalyst Triggers.
• "I need to trigger on funding rates or liquidations, not price." Supported. Use source: "funding" (overheated funding, funding flips negative) or source: "liquidation" (cascades, one-sided flushes, percent of open interest). Both often move before spot price does. See Funding and Liquidations.
• "I need to know when a notable account follows someone, or when several accounts I track converge on the same one." Supported. Use source: "x_follow_received" (someone follows a watched account), source: "x_follow_made" (a watched account follows someone), or source: "x_follow_overlap" (several watched accounts follow the same account inside a window). Authored on the direct EQL/API path today — Builder Chat support is pending. See Follow Graph.
• "I need to trigger on overall market sentiment." Supported. Use source: "fear_greed" — the Crypto Fear & Greed Index, by numeric score or classification band.
• "I need the same alert to keep firing on its own condition (not a fixed schedule)." Supported. Add the top-level repeat object (cooldown + maxTriggers) so the plan re-fires each time its condition recurs — e.g. "notify me every time BTC dips below 60k".
• "I need to run an LLM analysis when the condition fires and read its output." Supported. Use action.type: "llm", then fetch via Get Session.
• "I need to fan out to webhook + Telegram + notify on one trigger." Supported. Athena currently accepts exactly one action step per query — pick the highest-priority delivery for the action step (for example telegram_bot), then have your runner fan out to the rest, or use an llm action with a params.callback.action for one downstream chain.
• "I need to know if my query is valid before committing." Use Validate Query — it returns structured errors you can iterate on without creating the query.
• "I need the agent to keep running logic after the trigger." That's the Agent Runner pattern — Auto owns monitoring, your runner owns post-trigger decisions.

If none of these match your intent, see If /auto doesn't fit before rolling your own infrastructure.

Teams usually underestimate the operational work that starts after “the condition logic works once.”
If you build this yourself, you still need:

• access to highly reliable upstream APIs and robust fallbacks for partial outages
• data quality safeguards (schema drift checks, freshness checks, anomaly handling, and source reconciliation)
• state tracking across evaluations (for example transition-aware operators and prior values)
• dedupe/idempotency handling for repeat or replayed trigger events
• retry policies for upstream fetch, evaluation, and delivery failures
• delivery fanout across webhook, Telegram, and stream consumers
• lifecycle management (validate, activate, monitor, cancel, expire, audit)

Why Build on Auto

• Managed condition monitoring for query logic
• Built-in state tracking for condition evaluation lifecycles
• Event models designed for idempotent downstream dedupe
• Retryable delivery paths and clear failure surfaces for agents
• Delivery fanout primitives for webhook, Telegram, and SSE
• Query lifecycle controls (validate, create, poll, cancel, expiry)
• Native query lifecycle APIs (validate, create, poll, cancel)
• Builder Chat for natural-language-to-query acceleration
• Event delivery paths for downstream automation (webhook, Telegram, SSE)
• Session APIs for retrieving full LLM outputs when needed
• API-key based access with optional x402 access mode

Agent-First Workflow (Recommended)

1. Draft strategy quickly with Builder Chat.
2. Validate logic and preview simulation costs with Validate Query.
3. Activate with Create Query.
4. Connect delivery via webhook/Telegram/SSE.
5. Let your background runner handle post-trigger actions.

Best-Fit Agent Use Cases

Use Case	Fit	Why teams use Auto for this
Multi-condition price + TA logic (RSI, MACD, breakouts, time-window checks)	Strong	Keep complex trigger logic in one managed query runtime.
CEX + DEX monitoring programs	Strong	Run cross-market watchlists in one control plane for supported assets/sources.
Signal reaction loops (X/Twitter Post + Telegram Channel + Event)	Strong	Trigger agents when targeted accounts post, monitored Telegram channels post, or event narratives break.
SEC filing monitors	Strong	Trigger on deterministic SEC filing metadata for a CIK, including 8-Ks, late filings, offerings, ownership filings, and 8-K item flags. See SEC Filings.
Prediction-market workflows (Kalshi + Polymarket)	Strong	First-class kalshi conditions on trade prints and market lifecycle, and polymarket conditions on outcome-token price/quote/last-trade — see Prediction Markets.
Derivatives / market-structure monitoring (funding, liquidations)	Strong	Native funding and liquidation conditions across Binance, Bybit, and Hyperliquid — catch positioning stress before it shows up in spot price. See Funding and Liquidations.
Equities, indices and commodities on a macro catalyst	Strong	HIP-3 perps trade 24/7, so a CPI print, rate decision or earnings beat can fire an alert while the cash market is halted. See Catalyst Triggers.
Follow-graph watchlists (attention arriving on an account, or a set converging on one)	Strong	Native x_follow_received / x_follow_made / x_follow_overlap conditions over accounts Elfa monitors — catch a fund or founder cluster moving on a name before it is posted about. Alerts are not real time. See Follow Graph.
Event-triggered LLM research and summaries	Strong	Run LLM actions on trigger and retrieve outputs via sessions APIs.
Portfolio-level strategy packs	Strong	Operate many concurrent queries with consistent lifecycle controls.
Continuous monitoring with low ops overhead	Strong	Offload scheduling/evaluation/trigger plumbing to Auto.

Prompting Tips for Better Builder Output

To keep Builder Chat focused on Auto runtime constraints, include:

• Human-readable title and description — surfaced in delivered notifications so the recipient knows what/why without re-opening the query.
• Scope: symbols/universe to monitor
• Trigger definition: condition + timeframe/period
• For Signal triggers: source identity (X handle or Telegram channel when needed) and factual text description (avoid vague phrasing)
• Trigger behavior: one-time (default) vs recurring — for recurring on the same condition, ask for the repeat object (cooldown + maxTriggers); for a fixed schedule, use a cron condition
• Delivery target: webhook/notify/telegram_bot/llm
• Expiry: expiresIn window — prefer 24h–3d to stay tied to current intent.

Reference for supported condition sources, indicators, operators, and timeframes: Triggers. Signal-specific contracts and examples: Signal. For exact per-method TA args (including required vs optional fields), see TA Args Contract.

Example prompt:

Build an Auto query:
- title: "BTC/ETH RSI oversold on 1h"
- description: human-readable thesis for why we want this alert (1-2 sentences)
- monitor BTC and ETH RSI(14) on 1h
- trigger when crosses below 30
- one-time trigger, expires in 24h
- action: webhook to my endpoint
Return ready-to-submit query JSON.

High-Impact Builder Chat Prompt Pack

1. Complex TA breakout with direction filter

Build an Auto query:
- title + description: short human-readable summary and 1-2 sentence thesis
- symbols: BTC, ETH, SOL
- timeframe: 5m
- trigger when price breaks previous 1h range high or low
- confirm direction with RSI(14): >55 for upside, <45 for downside
- actions: telegram alert + webhook to https://your-runner.example/auto/events
- one-time trigger, expires in 48h
If anything is unsupported, return the closest supported query and list substitutions.

2. CEX + DEX monitoring pack

Build an Auto query pack for supported CEX + DEX symbols:
- title + description per query: short summary and thesis sentence
- watchlist: WBTC, ETH, SOL, HYPE
- trigger when 15m volume surge aligns with price momentum
- action: webhook to https://your-runner.example/auto/events
- include symbol and trigger summary in payload
- expires in 24h
If any symbol/source is unsupported, skip it and report skipped items.

3. Signal + social context on trigger

Build an Auto query pack, or one OR query if the same action should run for any Signal match:
- title + description: short summary and the thesis behind watching this
- monitor one or more Signal alternatives:
  - Signal trigger for Event: "SEC approves a spot ETH ETF"
  - Signal trigger for X/Twitter Post from a specific account using a factual match description
  - Signal trigger for Telegram Channel from a monitored public channel username, match "new Binance listing rumor"
- on trigger run llm action that adds:
  - latest market news context
  - X/Telegram sentiment summary
  - risk note
- also send telegram alert with a short summary
- expires in 24h

4. Prediction-market thesis watcher (Kalshi)

Build an Auto query:
- title + description: name the market thesis and the move you're watching for
- source: kalshi
- ticker: <a confirmed-open Kalshi market ticker, e.g. KXBTC-26APR0803-T77799.99>
- trigger when the YES implied probability crosses above 0.6
- action: llm to produce a catalyst hypothesis + invalidation level
- deliver to webhook: https://your-runner.example/auto/events
- include decision priority: high/medium/low
- expires in 2d
If the ticker is not open or anything is unsupported, return the closest supported query and list substitutions.

See Prediction Markets for the full method/operator reference and the open-markets-only rule. The same pattern applies to Polymarket — use source: polymarket with the outcome-token asset_id as ticker and the price/bid/ask/size/side methods.

5. Portfolio risk guardrail

Build an Auto query:
- title + description: portfolio guardrail label and the risk scenario it covers
- watch my portfolio symbols: BTC, ETH, SOL, HYPE
- trigger on downside acceleration and momentum weakness
- action: telegram alert with severity and suggested next check
- recurring checks, expires in 3d

6. Agent handoff with strict follow-up contract

Build an Auto query:
- title + description: breakout playbook name and the follow-up intent
- trigger on breakout + trend-confirmation conditions
- action: webhook to https://your-runner.example/auto/events
- include fields: eventId, symbol, triggerReason, priority, queryId
- objective: downstream agent decides next action under policy constraints
- expires in 24h

7. Event-first catalyst watcher

Build an Auto query:
- title + description: catalyst name + why it matters now
- use Signal category:
  - condition source: news
  - match description: "Major DeFi protocol suffers a $200M exploit"
  - minConfidence: 80
- action: webhook to https://your-runner.example/auto/events
- include queryId, eventId, and short trigger reason in payload
- expires in 24h
If unsupported, return closest supported query and list substitutions.

For a channel-scoped version of the same pattern, use source: "telegram" with a monitored public chatUsername and a focused match description.

8. Market-structure stress watcher (funding + liquidations)

Build an Auto query:
- title + description: name the positioning risk you're watching for
- source: liquidation, ticker BTC:BYBIT
- trigger when total liquidations cross above $1,000,000 in a 5m window
- AND source: funding, ticker BTC:BINANCE, annualized_rate above 20 (% APR)
  (i.e. longs were crowded going into the flush)
- recurring: repeat with a 1h cooldown, max 10 triggers
- action: telegram alert with the trigger context
- expires in 7d
Use composite SYMBOL:EXCHANGE tickers. If anything is unsupported, return the
closest supported query and list substitutions.

Note the venue choice: Bybit's liquidation feed is complete, while Binance's is sampled (a lower bound) — so the same dollar threshold is not equivalent across the two. See Feed quality by venue.

9. Catalyst alert on an equity/index perp (HIP-3)

Build an Auto query:
- title + description: name the catalyst and the asset context to review
- catalyst: a currently-open Kalshi market on the next Fed rate decision
- trigger when the YES probability crosses above 0.6
- action: webhook to https://your-runner.example/auto/events with symbol xyz:SP500 in the title/description
- recurring: repeat with a 4h cooldown, max 3 triggers
- expires in 7d
Use the DEX-prefixed HIP-3 symbol. If the ticker is not open or anything is
unsupported, return the closest supported query and list substitutions.

These perps trade 24/7, so this fires overnight and at weekends — exactly when the cash equity market can't help you. See Catalyst Triggers for the catalyst→asset-class bridge and four more setups.

For Advanced Strategies

If you have proprietary selection logic or custom signal preprocessing, keep Auto as your runtime control plane:

1. Compute selector/signal logic in your own service.
2. Feed resulting strategy inputs into Auto queries.
3. Use Auto for monitoring, triggering, and delivery.

Next Guides

• Triggers (Conditions + Indicators)
• Signal Triggers
• SEC Filings
• Funding and Liquidations
• Query Model and Templates
• Notifications
• Agent Runner
• x402-Specific Instructions