Alerts from an AI client
Ask your AI for an alert in your own words — for example “alert me in Telegram when BTC drops below 80,000” — and it makes it with the Agent tools: the same rules you would make by hand at https://agent.debyko.com, on the same pages afterwards.
- It makes the condition concrete with you: the level, the instrument and venue. Every plan can use every venue and instrument. DEBYKO knows nothing about your positions, so for “when I’m down 5%” it asks for your entry price instead of guessing.
- It checks where alerts can go (
agent_channels). A rule can send to as many of your channels as you want, Telegram chats and webhooks mixed; each channel a firing reaches is one notification. With no channel, it asks: Telegram or a webhook. For Telegram it gives you a one-time link (agent_channel_connect): open it, press Start in @debyko_bot, and tell it you did. A webhook gets a test message; its signing key is never shown in a chat: you make one with New signing key on the webhook’s card at https://agent.debyko.com/channels. - It asks you for the alert’s label, the first line of every notification, and creates the rule (
agent_rule_create). - It shows the dry run: what the rule answers right now, per venue. A rule fires when its condition turns from false to true, so a condition that is already true does not fire until it has been false first; the AI says so and offers to move the level.
- It tells you how to turn the rule off: ask it to pause (
agent_rule_set) or delete (agent_rule_delete) the rule, press Turn off this rule in any notification, or open the rule at https://agent.debyko.com.
When something is in the way — no account, no channel, a link not opened yet, or a plan limit — the server says what to do and the AI passes it on (every code is in Errors). Agent is on for every account until you switch it off; a rule created while it is off is kept and does not run until Agent is on again (ask the AI, or switch Agent is on at https://agent.debyko.com), and the AI tells you so (AGENT_STOPPED).
The Agent tools are turned on account by account. Until they are on for yours, the AI gives you the steps to make the same rule by hand, which follow.
By hand at agent.debyko.com
Section titled “By hand at agent.debyko.com”Agent runs your rules on DEBYKO’s side and notifies you when one turns true. It never trades: a notification states facts, never buy or sell. The cabinet is https://agent.debyko.com, open to every DEBYKO account, the Free one included; sign in with the same email and code as at studio.debyko.com. It has three pages: Rules (/), Firings (/firings) and Channels (/channels).
Agent on and off
Section titled “Agent on and off”Open https://agent.debyko.com (sign in with the same email and code). Agent is on for every account until someone switches it off: if the switch at the top of Rules says Agent is off — no rule is checked, switch it on, and it says Agent is on. A rule saved while Agent is off is kept, and does not run until Agent is on again. The same switch turns every rule off at once (Agent is off — no rule is checked).
A rule is one DQL condition, the instruments it watches and when it is checked (CHECK: at each candle close of the rule’s timeframe), where the notification goes (THEN FIRE: any number of the account’s channels, Telegram chats and webhooks mixed) and, for Telegram, the message you write (Telegram message). The DQL is the language of the screen tool (docs://dql), for example:
any(venues where venue in (MEXC-PERP) and last < 80000) where instrument = BTC-PERPA rule can read every venue and instrument on every plan. account lists the venues available on the platform.
Make a rule by hand:
- On https://agent.debyko.com press New rule. 2. Choose Build by hand on an empty page, then Edit conditions to open the pill editor. Set the condition: click the pills of the lines (WATCH holds the instruments, the venue and the candles; + line adds a line under IF), or press Edit as text, paste the DQL condition and press Done. 3. In THEN FIRE, press choose channels and pick the channels: as many as you want, Telegram chats and webhooks mixed (add them in Channels first). 4. For Telegram, press the Telegram message pill and write the message: the first line of every notification. 5. WHAT ARRIVES · WEBHOOK BODY shows the body a webhook gets; press Create rule in the bar at the bottom: the rule is saved and starts, and the switch at the top says Running. 6. Send test at the end of the THEN FIRE row sends a test message to each chosen channel and shows what each answered. An account opened from Agent’s front door lands on this page with a first rule already filled in (BTC funding turns negative: the funding 8 h is below 0%): check the Preview, change what you want and press Create rule.
Change one: press Edit on its row, then Edit conditions and click a pill; changes wait in the page (Unsaved changes) until you press Apply, which saves them as one new version that the next check uses; Discard puts back the saved rule. Leaving the page with unsaved changes asks first. To rename a rule, click its name at the top of its page (or choose Rename in the ⋯ menu, here or on its row in Rules), type the new name and press Enter; Esc keeps the old one. The ⋯ menu beside the Running switch has Rename, Duplicate (the copy opens as a new rule, saved with Create rule) and Delete. A rule whose DQL is not made of the editor’s lines opens as text: press Edit as text, change it, press Done.
The first screen shows the rule summary, collapsed conditions, Check on history, How does this rule work?, then ADVANCED SETTINGS (the existing DATA and CHECK controls). Edit conditions opens the unchanged pill editor; Done editing collapses it. A line says yes or no when evaluated and unknown when data cannot answer; while a new evaluation is in flight it keeps its last answer with its time (as of 14:03 UTC), and says checking… only before it has any. Every line is said in words, a line written as DQL included; if one line cannot be said in words, every line of the rule shows its DQL with an English gloss under it. The summary chart and counts use the actual checked window and instrument, never an assumed 24 hours. Check on history opens the existing Preview with candles and FIRE markers; DQL and Webhook keep their existing behavior. On mobile, the bottom RULE · PREVIEW · DQL · ALERTS · WEBHOOK tabs remain available. Candle rules keep their saved live or settled mode, rearm, cooldown and data requirements.
DEBYKO AI in the rule header restores BUILD WITH AI after Hide; this preference is saved on the account. Describe the rule in LT, EN or RU and press Build. The proposal shows the validated DQL’s current matches and full 24-hour replay, or explicitly says a result could not be evaluated. Open the rule accepts it only into the unsaved draft; Apply or Create rule is still required to save and enable it. Explain with AI writes an explanation in the interface language; a rule edit marks it outdated and Regenerate refreshes it. Worth checking is labeled AI opinion. Built-in AI is unavailable until the owner configures the provider/model, plan quotas and privacy disclosure.
Use your own AI → Copy prompt copies generated DQL documentation, the request and current rule. Open Claude / Open ChatGPT open those services without sending rule text in the URL. Paste the returned DQL through Paste DQL and Use as draft: it is parsed through the existing editor and still requires an explicit save.
On and off: the switch on each row of Rules pauses and resumes a rule; on the rule’s own page, the Running / Paused switch at the top does the same, and Delete in its ⋯ menu deletes the rule (its firings stay in Firings).
Statuses in the list: Running; Paused — by you; Paused — by Stop all; Paused by DEBYKO — a reason (a rule held by a venue limit from an older plan version is rechecked and resumes when the API accepts it; the API did not know a code of the rule — it resumes on its own once the code is known again —; more than 500 instruments in the answer; the Agent key was refused); Can’t see since a time — what the rule cannot read and why (for an indicator: a candle missing in its own lookback, with the recorded cause when there is one); it clears by itself on the first candle whose lookbacks are clean; Agent is off.
When a rule fires
Section titled “When a rule fires”A rule fires when Agent has seen its condition false, with every value it reads present, and then true. A condition that is already true when the rule is saved does not fire until it has been false and true again; unknown or stale values neither fire nor re-arm a rule.
Channels
Section titled “Channels”At https://agent.debyko.com/channels:
- Telegram: 1. Open https://agent.debyko.com/channels. 2. Under Add a channel press Telegram, then Connect Telegram. 3. Press Open @debyko_bot (the link works once and expires in 10 minutes) and press Start in Telegram. 4. The bot answers “Linked to DEBYKO account …” with your masked email, and the page says Telegram linked. Disconnect on the chat’s card forgets it; Send test sends a test message.
- Webhook: 1. Open https://agent.debyko.com/channels. 2. Under Add a channel press Webhook, fill in Name and Address (https://), paste a Signing key or press Generate, and press Add webhook. 3. A generated key is shown once: press Copy, put it in your receiver, then Done. 4. Press Send test on the webhook’s card. Remove deletes it. DEBYKO signs every message so the receiver can check it came from DEBYKO. New signing key on the webhook’s card makes a new key and shows it once (Copy, then Done): messages are signed with it from the next one on, and for 24 hours with the old key as well. A webhook added from an AI client gets its key this way, since a key is never shown in a chat.
- Email: 1. Open https://agent.debyko.com/channels. 2. Under Add a channel press Email, then Add email: a confirmation email goes to the address you sign in with (nothing else is ever sent to it before you confirm). 3. Open that email and press Confirm email channel; the card on Channels says Working. 4. If no email comes, press Resend confirmation on the Email card (one a minute, five a day), and look in Spam. 5. Choose Email in a rule’s channels. Every notification email ends with a Stop this channel button (and the mail client’s own Unsubscribe): the channel is then Stopped, and to turn it on again press Add email and confirm the new email. Send test sends a test email.
A webhook whose deliveries keep failing shows Failing, and the Rules page shows a banner with Fix in Channels: fix the receiver, then press Send test. A Telegram chat the bot can no longer reach (the bot was blocked or the chat deleted) shows Disabled with the reason, and nothing is sent there: unblock @debyko_bot and connect the chat again with Connect Telegram.
What a Telegram notification looks like
Section titled “What a Telegram notification looks like”<your Telegram message, in bold>BTC-PERP · KRAKEN-FUTURES · last <value> <unit> · 2026-10-07 12:00:40 UTCTurn off this ruleThe first line is your text; the second is the instrument, venue, the value as the API returned it with its unit, and the time (UTC); the link opens the rule’s page.
Firings
Section titled “Firings”https://agent.debyko.com/firings: every firing and every check that could not answer, filtered by All, Fired, Not fired, Delivery failed; each record keeps the values it used, their age, and what each channel replied (Resend to failed channels). A firing over the day’s notifications says not delivered: daily notification limit for each channel.
Notifications
Section titled “Notifications”Every channel a firing reaches is one notification: a firing sent to 1 channel is 1, to 10 channels 10. A rule that can’t see for more than 15 minutes is told to its channels the same way: one notification saying since when and what it could not read, and one more when it sees again; each counts like a firing. A retry or a Resend of the same delivery is not counted again. Notifications are counted per account per UTC day; a rule that sends to 3 channels costs 3 notifications per firing, and the top of Rules shows today’s count. Over the plan’s notifications a day, a firing is still recorded but nothing is delivered (not delivered: daily notification limit); the rule is not paused, and delivery resumes at 00:00 UTC. The daily notifications per plan (owner, 2026-10-09; docs://plans has the table as it is now): Free 100, Mini 1,000, Standard 5,000, Pro 20,000, Pro Plus 50,000.
Stopping
Section titled “Stopping”To pause one rule, switch it off in the list on https://agent.debyko.com, or open it and switch Running off (it then says Paused); Delete is in the ⋯ menu beside that switch. Every Telegram notification ends with a Turn off this rule link to that page. To stop everything at once, press Stop all at the bottom of Rules (it pauses every rule, switches Agent off and sends close_all to every webhook), or switch Agent off. Either way Agent stays off, and a rule saved meanwhile does not run, until you switch it on again (Agent is on), which resumes the rules that were stopped.
Limits
Section titled “Limits”How many rules run at once, the shortest check interval, the checks per minute of all running rules together, how many webhooks and Telegram chats a plan holds and its notifications a day are in docs://plans, read from the plan table Agent enforces. A rule takes any number of the account’s channels; only how many the account holds is limited. The checks-per-minute budget is the hard cap: a rule checked at the shortest interval takes a little more than its own checks (retries are counted), so on a small budget fewer rules fit at the shortest interval than the rule count allows; a longer interval or candle timeframe fits more. A refusal says which limit it was (PLAN_RULE_LIMIT, PLAN_INTERVAL_TOO_SHORT, PLAN_CHECK_BUDGET, PLAN_CHANNEL_LIMIT) and what to do; the day’s notifications used up is PLAN_NOTIFICATION_LIMIT, with retry_after until 00:00 UTC.