Portal Community
Spot only, by design: the node's own routing documentation states plainly that Margin/Futures and any trigger/streaming design are explicitly out of scope for this version — not simply "not built yet," but a deliberate v1 boundary.

Out of Scope for v1

AreaStatus
Margin APIOut of scope — this node only calls the Spot v3 REST API.
Futures APIOut of scope — same reason.
WebSocket streaming (live price/order-book/user-data streams)Out of scope — every operation here is a request/response REST call; there is no push/streaming design on this node.

Known Gap: No Dedicated Environment Toggle

BinanceApiClientOptions has no explicit "testnet vs. production" field yet — v1 defaults BaseUrl to the production host (https://api.binance.com/). Until a dedicated toggle is added, overriding Binance:BaseUrl directly (e.g. to https://testnet.binance.vision/api) in appsettings is the escape hatch for pointing a non-production deployment at Binance's Spot testnet. See Configuration.

Everything documented elsewhere in this guide is implemented today. This page only covers what's explicitly excluded from v1 and the one configuration gap noted above — the 11 operations across account, order, and marketData (see Overview) are all live, working REST calls.