Getting started with an AI client
DEBYKO collects market data from perpetual-futures venues and stores it as each venue published it. You read it through the API, through an AI client connected to the DEBYKO MCP server, or in Studio; Agent watches it for you and notifies your Telegram or webhook when a condition you wrote turns true.
1. An account
Section titled “1. An account”Open https://studio.debyko.com/account/signin, enter your email and press Send the code, then enter the code from the email and press Sign in. The Free plan is free and needs no card.
2. Connect an AI client
Section titled “2. Connect an AI client”The MCP server is https://mcp.debyko.com/mcp (Streamable HTTP).
- claude.ai, Claude Desktop: Customize → Connectors → + Add → Add custom connector, paste the URL, then Continue → Add → Connect. The client sends you to studio.debyko.com: sign in, check the request and press Allow.
- ChatGPT (chatgpt.com on a computer only): Plugins → + → Add custom MCP server, paste the URL, choose OAuth, then Create; it signs in the same way (Allow). Developer mode, if ChatGPT asks for it, is under Settings → Apps → Advanced settings.
- Claude Code:
claude mcp add --transport http debyko https://mcp.debyko.com/mcp, then run/mcpand authenticate. With a key instead: add--header "Authorization: Bearer <key>". - Cursor: in
.cursor/mcp.json,{"mcpServers": {"debyko": {"url": "https://mcp.debyko.com/mcp"}}}signs in with OAuth; add"headers": {"Authorization": "Bearer <key>"}to use a key. - Any MCP client that sets a header: the URL and
Authorization: Bearer <key>. An account opened by signing in on the sign-in page (or from the documentation, or from a plan button) shows its API key once, on the page Your account is open: press Copy; under the key the page has the first request, ready to paste with the key in it (an account opened by connecting an AI client with OAuth, or from Studio or Agent, has no key of its own until you make one). For another key later, open https://studio.debyko.com/account and under API keys press Issue a key (or open the ⋯ menu of the key you have and press Rotate, then Rotate key: a new key with the same label is shown once, and the old one stops working within 30 seconds).
After Allow the client gets its code at once and takes over. The consent page and the Application connected page show After connecting, ask your AI: “Compare BTC funding across all venues right now, with the age of each value.” Paste that question into your AI chat; connecting does not run a market-data request by itself. Until you ask something, studio.debyko.com/account also shows Connected — ask this in your chat, as a card you can Dismiss.
If the consent page is submitted or refreshed again from the same signed-in session, the original decision is kept: an unexchanged, unexpired approval returns the same code; a completed connection says This application is already connected. An expired approval says Start a new connection from the application. A repeated Deny keeps the original denial; an old Deny form cannot undo an approval. End access under Connected applications instead.
A connection is ended under Connected applications at https://studio.debyko.com/account (End).
3. Link Telegram
Section titled “3. Link Telegram”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.
- 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.
A webhook instead: 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.
4. A first rule
Section titled “4. A first rule”- 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.
Rules fire when the condition turns from false to true. A condition that is already true when you save it does not fire until it has been false and then true again.
5. Where firings are
Section titled “5. Where firings are”https://agent.debyko.com/firings lists every time a rule turned true and every check that could not answer, with the values used and what each channel replied.
6. How to stop
Section titled “6. How to stop”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.
More: docs://agent (rules and channels in detail), docs://plans (what each plan allows), docs://dql (the query language).