Capabilities
Auto is built for agents that need a reliable condition engine + trigger pipeline without building that infrastructure from scratch.
Why Build on Auto
- Managed condition monitoring for query logic
- 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)
- Draft strategy quickly with Builder Chat.
- Validate logic and preview simulation costs with Validate Query.
- Activate with Create Query.
- Connect delivery via webhook/Telegram/SSE.
- 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. |
| News + social signal reaction loops (X + market news) | Strong | Trigger agents when narrative or sentiment context shifts. |
| Prediction-market and thesis-watch workflows | Strong | Track condition changes and fan out alerts/analysis to agents quickly. |
| 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:
- Scope: symbols/universe to monitor
- Trigger definition: condition + timeframe/period
- Trigger behavior: one-time vs recurring
- Delivery target: webhook/telegram/notify/llm
- Expiry:
expiresInwindow
Example prompt:
Build an Auto query:
- 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.