Take Bitget away and it stops.
One real order, run by the engine. With every Bitget input, the answer is 36.87 bps, over your ceiling, with the largest size that fits named. Withhold any one of them and this is what the same engine does, on the same recorded book.
“Sell 178.4121 rHIMS. I pay 0.05% taker, keep it under 0.3% all-in, and I must be out before the 8th.”
- Spot order bookBitget public API
The depth the order is walked through, level by level, at your exact size.
GET /api/v2/spot/market/orderbook?limit=150with it36.87 bps, overwithout itNO_EXECUTABLE_QUOTEempty book.
With no book there is no price at your size, only a guess, so nothing is answered.
- Reality stock-infoBitget public API
Which rTokens exist, and which Bitget flags weekend-tradable.
GET /api/v3/reality/market/stock-infowith it36.87 bps, overwithout itINVALID_INSTRUMENTsymbol not present in Bitget Reality stock-info.
Without Bitget's list it cannot tell a real rToken from a typo, or whether this one trades on a weekend, so it refuses rather than sound a name that may not trade.
- Market states and calendarBitget public API
Which session is open, the holidays, and when the next session starts: the weekend and holiday sessions, when Bitget's own book is the market, are the only ones Sounding prices.
GET /api/v3/reality/market/states · /calendarwith it36.87 bps, overwithout itSESSION_UNKNOWNmarket states or calendar unavailable.
In US sessions Bitget routes the order to NASDAQ/NYSE; on weekends and holidays it fills on Bitget's own market-maker book. Without the session it cannot say which venue the order meets, or when the book closes.
- Instrument rulesBitget public API
Quantity precision and minimum order, so a size the exchange would reject is refused first.
GET /api/v3/market/instruments?category=SPOTwith it36.87 bps, overwithout itINVALID_INSTRUMENTinstrument order constraints unavailable (GET /api/v3/market/instruments).
Without the rules it cannot tell whether 178.4121 shares is a size Bitget accepts, so it refuses rather than price an order the exchange would reject.
- Qwen 3.8 MaxBitget S2 model endpoint
Reads the trader's own words, English or 中文, and quotes them for every limit; code checks each quote before the engine uses it.
POST hackathon.bitgetops.com/v1/chat/completionswith it36.87 bps, overfee from "I pay 0.05% taker" and ceiling from "keep it under 0.3% all-in", each confirmed by code
without itAsked, not answeredYou mentioned your taker fee ("taker") but I could not read it. What is your taker fee, exactly?.
Limits said the way traders say them (a percent, "before the 8th") are beyond the fallback reader, so it cannot answer on this trader's own limits and asks for them again.
Computed when this page was built, from the frozen fixtures, by the same sound() the desk calls. The build runs a test first that fails if any removal stops breaking it.
Qwen reads. Code checks. Bitget decides.
Qwen never does the arithmetic. It reads the trader’s words, in English or 中文, and must quote them for every limit. Code finds each quote in the message and reads the number or date itself. Bitget’s data then decides, and Qwen explains the ruling under rules code enforces.
Without Qwen, the fallback reader takes the same sentence and finds no fee, no ceiling and no deadline. It cannot answer on this trader’s own limits, so it asks for them again: “You mentioned your taker fee ("taker") but I could not read it. What is your taker fee, exactly?”
limits read correctly with Qwen, on 40 blind messages
without it, by the regex reader
The card says what you are sending. Sounding adds what it costs.
Bitget Agent Hub lets an AI agent trade a Bitget account: its flow is a dry run, a confirmation card naming pair, side and quantity, then the send. Its own pre_trade_check reads the ticker price, the balance and the positions; nothing in it walks the book at the order’s size. Sounding sits at that step: the agent reads the trader’s own fee with Agent Hub’s account_overview and passes it in, Sounding walks the book at the full size, and hands back the exact Agent Hub order only when it fits: a limit IOC at the trader’s ceiling price, bound to its receipt, so Bitget fills no share that costs more than the ceiling. Anything else comes back as a reason. It is a check an agent chooses to run: it cannot stop a client that skips it, which is why the skill tells the agent to send only the order Sounding prepared.
| order, recorded Sunday rHIMS book, 40 bps ceiling | Agent Hub dry run (bgc 3.0.0) | Sounding |
|---|---|---|
| sell 5000 RHIMSUSDT | previews it | refused: the visible book cannot fill this order; 66.0764 sh offered as a new order |
| hold -5 RHIMSUSDT | previews it | rejected: symbol and side (buy or sell) required |
| sell 50 RHIMSUSDT | previews it | prepared: 19.89 bps all-in at 5 bps (stated), within 40, as a limit IOC at 27.93 (no fill can cost more than 38.88 bps) |
Recorded 2026-10-08 (evidence/agenthub-20261008). On a weekday Bitget routes rToken orders to NASDAQ/NYSE, so Sounding prices them only on weekends and US holidays, when Bitget’s own book is the market. For agents: an MCP tool, sounding_prepare_order, and a skill in Agent Hub’s own format that adds the at-size cost to its confirmation card and sends only the order Sounding prepared (agent/ in the repository). The account fee was read with a read-only key on the developer’s machine; this site holds no key.
What it leaves out, and why.
- bitget-signal
Every upstream feed we queried returned empty when checked on 2026-10-02. A signal with nothing in it would be decoration, so it is not on the page.
- Paper trading
Bitget's demo environment lists 6 of the 90 weekend-tradable rTokens, all with empty books (checked 2026-10-05), so a paper fill would prove nothing about a real one. The order path is shown as a dry run instead.
- GetAgent
A research assistant across assets. Its published material shows no walk of a Bitget book at a given size, which is the one thing a decision here rests on.