DEBYKO

Where the account's Agent alerts can go, and in what state: Telegram (`linked` with the chat, `pending` while a link waits for Start, `not_linked`, or `disabled` with the reason), email (`not_confirmed` until confirmed) and webhooks (masked address, `working`, `failing` or `not_set_up`, last delivery), the plan's channel limits and shortest check interval, today's notifications against the daily limit (`notifications`, with `PLAN_NOTIFICATION_LIMIT` and `retry_after` once used), and whether Agent is on. Call it before agent_rule_create, and again after the user says they pressed Start in Telegram. With no channel, ask the user whether they want Telegram, email or a webhook and follow `next`. Not counted on your key. Use this when you need to know where the account's alerts can be sent; to add a channel use `agent_channel_connect`.

agent_channels

Turns Agent on or off for the whole account. Off is the kill switch: no rule is checked and nothing is sent until it is on again; on resumes the rules that stopped with it. Agent is on by default: call this with `enabled: true` only when the user asks for it (for example after a rule came back with code AGENT_STOPPED), and with `false` only when the user asks to stop everything. Tell the user what changed. Not counted on your key. Use this when the user wants every alert stopped, or Agent turned back on; for one rule use `agent_rule_set`.

agent_set_enabled

The state of the account's Agent rules, polled: per rule `state` (`true`, `false` or `unknown`, with a `reason` when it is unknown), `previous_state` (what this key was told the last time it asked about the rule, `null` the first time), `evaluated_at` and `effective_interval`, and what Agent states of it: `label`, `enabled`, `channels`, `last_fired_at` and, when DEBYKO paused it, `paused_reason`; the top-level `agent` is `on` or `stopped`. `rule_id` narrows to those rules (UUIDs, comma separated); leave it out for every rule of the account. `fresh=true` evaluates the rules now instead of reading the last scheduled evaluation, and is charged against the plan's evaluations/day budget. Counts as one request on your key. Use this when the user asks for their DEBYKO rules, alerts, signals, active conditions or when a rule last fired (also: правила, алерты, сигналы, moi pravila); for the saved DQL of one rule use `agent_rule_get`.

agent_state

What this key sees and what is left of it today: the plan, the platform venues (`venues.included`), the layers, the limits, and today's counters against them (requests with the remainder and by class, DQL, streams, Agent evaluations, archive files). Read-only. Needs a key; free: it is not counted as a request on the key. Use this when you need your plan's venues, limits or what is left of them today, before a long job or after a call was refused for the plan; for every venue DEBYKO collects use `venues`.

account

A row of DEBYKO's stored history and the Merkle path from it to the root of its UTC day, which is posted to a contract on Base within 24 hours of the day's end: the canonical text of the row, its hash, `index` of `rows`, the audit path to the partition, the partition's leaf and the path to `day_root`, and where that root is on the chain. Verify it with SHA-256 alone (docs.debyko.com/attest/verify). The anchor proves the data did not change after the anchor time; it proves nothing about its correctness at collection. A day not yet anchored, a row never stored or already dropped by retention, and a row changed since the anchor are each their own error code. Counts as one request on your key. Use this when you need to prove that a stored history row has not changed since its day was anchored; for the row's values use `history`.

anchor_proof

Completed price bars (open, high, low, close, volume) for the selected listings, one per period, in any stored timeframe and price type; a period nobody reported is a `gap`, never invented. Up to 100 listings and 1,500 bars per listing a call. How far back depends on the plan: on Free, `4h` and `1d` bars reach 90 days, shorter ones 48 hours; a request past it is refused with `PLAN_LIMIT` and the earliest `from` and a ready `retry_with`. Counts as one request on your key. Use this when you need open, high, low and close bars over a window; for a layer's values at past instants use `history`, for the latest values use `snapshots`.

candles

Changes an Agent rule: `enabled` false pauses it and true resumes it; `label`, `interval_s` and `channels` change what it says, how often it is checked and where it sends. Setting the same values again changes nothing. Change only what the user asked for; `rule_id` comes from agent_rule_create or agent_state. After, tell the user the rule's status as returned. Not counted on your key. Use this when the user wants to pause, resume or edit an alert; to remove it for good use `agent_rule_delete`.

agent_rule_set

Connects a channel for Agent alerts. `{kind: "telegram"}` returns a one-time link to @debyko_bot (it works once, for 10 minutes) and the steps; `{kind: "email"}` emails a confirmation link to the account's address; `{kind: "webhook", url}` adds the webhook, sends it a test message and returns its status. First ask the user which they want, and for a webhook its public https:// address. Give the user `next` as numbered steps, link exactly as returned; after they say they pressed Start or confirmed, check with agent_channels. The webhook's signing key is never returned here: `next` says where the user gets it. Not counted on your key. Use this when the account has no channel for an alert, or the user wants another one; to see the channels it has use `agent_channels`.

agent_channel_connect

Creates an Agent alert rule: DEBYKO checks a DQL condition every `interval_s` seconds and notifies the chosen channels the first time it turns from false to true, with the user's `label` and the facts (instrument, venue, value, time UTC), never buy or sell. Before calling, make the condition concrete with the user: DEBYKO has no user positions, so if the user describes a loss or an entry ('when I'm down 5%'), ask for the entry price and compute the level; never guess. Write the DQL only with names listed in docs://dql (see "Plain language → DQL") and venue codes from `venues`; every plan can use every venue and instrument. Before saving, restate the DQL to the user in plain words and let them correct it. Ask the user for the label. Call agent_channels first, and when it shows more than one channel ask which ones. After: show the dry run (`dry_run`, per venue values, and `notifications.text`: notifications per firing and how many of the day's are used): if `currently` is true, say what `next` says and offer to adjust the level; then tell the user how to turn it off (`turn_off`). A refusal (no channel, a plan limit, a stopped Agent) carries `next`: give it to the user as written. Not counted on your key. Use this when the user wants to be notified when a market condition turns true; to change or pause a rule use `agent_rule_set`, to test a condition without saving use `screen`.

agent_rule_create

Deletes an Agent rule: it stops at once and sends nothing more; its past firings stay at agent.debyko.com/firings. It cannot be undone: confirm with the user which rule (by its label) before calling; to stop a rule for a while, pause it with agent_rule_set instead. Not counted on your key. Use this when the user wants an alert gone for good; to pause it use `agent_rule_set` with `enabled: false`.

agent_rule_delete