Quests API
Quests are autonomous tasks that execute on schedules or triggers. Each quest represents a trading strategy, portfolio check, or market scan that runs without manual intervention.Get Quest Progress
Query Parameters
Telegram chat ID to fetch quests for
Response Fields
List of quest progress objects
ISO 8601 timestamp of last update
Get Quest Diagnostics
Query Parameters
Telegram chat ID to fetch diagnostics for
Response Fields
Chat identifier
Whether autonomous mode is active
ISO 8601 timestamp when autonomous mode started
Count of currently running quests
Quest engine runtime diagnostics
Portfolio safety metrics (see Budget API for details)
Quest Schema
Quests are defined by the following structure stored in the quest engine:Quest Object
Unique quest identifier (UUID)
Human-readable quest name
Detailed description of quest purpose
Quest type:
routine- Time-triggered recurring taskstriggered- Event-driven executiongoal- Milestone-based questsarbitrage- Arbitrage opportunity execution
For routine quests:
micro- Every 1-5 minuteshourly- Once per hourdaily- Once per dayweekly- Once per weekonetime- Single execution
Cron expression for custom schedules (optional). Example:
*/5 * * * * for every 5 minutes.Execution priority:
CRITICAL, HIGH, NORMAL, LOWCurrent status:
pending, active, completed, failed, pausedISO 8601 timestamp of next scheduled execution
ISO 8601 timestamp of last execution
Quest-specific progress data (varies by quest type)
Quest Scheduling
Cron Scheduling
Quests support cron expressions for flexible scheduling:*/5 * * * *- Every 5 minutes0 * * * *- Every hour at :000 0 * * *- Daily at midnight0 9,17 * * 1-5- Weekdays at 9 AM and 5 PM
Event Triggers
Event-driven quests execute when specific conditions are met:- Price Movement: Trigger when price crosses threshold
- Funding Rate: Execute when funding rate anomaly detected
- Portfolio Health: Run when drawdown or exposure exceeds limit
- Order Fill: Trigger follow-up actions after order execution