Public discovery & help
Public source reads and documentation exist; provider reachability is not verified here.
Scope & limitsInteractive real-money tickets ask for your approval. Automation needs separate authorization, and available controls depend on your account. This page explains the flow with examples; your account shows its actual permissions and order status.
Follow an interactive real-money ticket from request to status. Wallet custody, delegated automation and available controls depend on the account and deployment.
Request → execution
CAN
CANNOT
Your wallet, your word. Nothing moves without it, and everything that moves is logged.
Start with conversation, then check which account features are available. Setup does not authorize moving money. Never send keys in chat.
Start with a Telegram message. Account actions require verified identity and the access allowed for that action.
Wallet setup depends on account eligibility, provider configuration and supported signing. An address alone does not mean funding or trading is ready. Never send keys in chat.
Use only the supported chain and token shown in your account's verified deposit instructions. Check the destination before sending; never assume a trading address or exchange deposit address accepts the transfer.
Research and paper trading are built. Real-money actions remain gated until account, provider and recovery checks pass. Swaps and perps execution stay off.
This example explains the controls. Your account’s actual limits and available actions come from the server and can differ from this overview.
Illustrative overview · this page does not read or change your account permissions.
Before a supported trading request reaches a venue, server checks validate the contract, permissions, quote, limits and required confirmation.
For a trading request, the model helps turn your words into a structured intent. Software validates that intent before execution. The model cannot grant signing authority or skip a required check.
The model’s answer cannot replace the required permission or confirmation.
Every order Bookie builds becomes two things you can inspect: the order itself, and afterward, a full receipt. Try it below.
Interactive example · no real order is placed.BUY
YES · England moneyline
England vs France · Polymarket
Venue · Polymarket
This is a live-replaying example of one order’s full trail: the same shape every real one leaves behind.
Illustrative replay · real orders log the same steps.
Compare it directly.
| Typical AI trading bot | Bookie |
|---|---|
| Buy whatever the AI thinks | You describe the position, Bookie finds it |
| Execution is a black box | Every step is shown before it happens |
| Executes automatically | Confirms with you first, every time |
| Discretionary picks, hot tips | You’re always the one calling the position |
| Wants your exchange login or API keys in chat | Wallet setup outside chat · custody depends on the signer |
Controls implemented in the product, with availability depending on deployment and account. These labels are not an independent security certification.
Implemented controls
On the roadmap
Found something?
Report anything affecting the safety of funds, accounts, or data to security@bookie.dog. We acknowledge within three working days and keep you updated until it is resolved. Give us a reasonable window to ship a fix before disclosing publicly, and please don’t access, change, or keep data that isn’t yours while you’re looking.
Machine-readable at /.well-known/security.txt. No bug bounty yet; we will say so here the day there is one.
No live trading readiness is asserted. Code, tests and a responding server do not prove admitted-account, provider, custody or funded acceptance.
Public source reads and documentation exist; provider reachability is not verified here.
Scope & limitsAccount, research, exact scenario math, saved paper records and restricted stored-evidence/source review are built; configured account access is required.
Scope & limitsManual review flows exist; target-host, provider, native-session and funded acceptance remain.
Scope & limitsExecution stays off while engineering and independent live acceptance remain.
Scope & limitsResearch and paper foundations do not enable supported real execution.
Scope & limitsThese complete user journeys are not available in the current release.
Scope & limitsImplementation notes reviewed 2026-09-30 · Authored implementation notes, not a live uptime or incident feed.
What is implemented, what still needs acceptance and what remains outside this beta. A built feature does not mean it is available for real money.
Implemented foundation
Built · acceptance pending
Execution · gated
Outside this beta
Telegram conversation, research and paper testing are the beta focus. Live execution stays gated; credentials alone do not complete missing signing, exit or recovery work.
Why should I trust Bookie?
“You shouldn’t trust us blindly. We’ve built Bookie so that trust comes from technical safeguards, transparent permissions, and your continued control, not from asking you to take our word for it.”
Nothing moves without you.