Binance Public Spot API

Can I place spot and margin orders through the Binance API?

Yes. POST /api/v3/order places spot orders and supports MARKET, LIMIT, STOP_LOSS, and other order types, while POST /api/v3/orderList/oco places OCO order pairs. For margin trading, POST /sapi/v1/margin/order places cross or isolated margin orders, and POST /sapi/v1/margin/borrow-repay handles borrowing and repaying.

What are the rate limits for the Binance Spot API?

Binance limits by IP rather than by API key, and its REST reference states this directly: 'The limits on the API are based on the IPs, not the API keys.' Each route carries a weight, and every response returns an X-MBX-USED-WEIGHT header for the interval showing how much of the allowance the IP has consumed. The current ceilings and weights live in the rateLimits array returned by GET /api/v3/exchangeInfo, covering RAW_REQUESTS, REQUEST_WEIGHT, and ORDERS. Unfilled order counts are tracked per account and can be read at GET /api/v3/rateLimit/order. Exceeding a limit returns a 429 with a Retry-After header, and continuing to send requests after that leads to an automated IP ban.

Is there a Binance MCP server?

You don't need an MCP server to give your agent the Binance Public Spot API. Jentic connects it directly from the API Directory: install self-hosted Jentic One, add the API, store your key and secret once, and your agent can call any of the 340 operations. Because the instance runs on your own infrastructure, your rules decide which Binance operations the agent may reach, and the credentials stay in the instance instead of an agent-side config file.

How do I place an order through Jentic?

Install self-hosted Jentic One on the machine that will host it, then run jentic register on the separate machine where your agent runs, and add the Binance Public Spot API to your workspace. Ask for 'place a Binance spot order' and Jentic returns POST /api/v3/order with its input schema, so the agent supplies symbol, side, type, quantity, and price and executes. Keep the agent off the instance's machine before you load real trading keys: an agent running as the same OS user as Jentic One can read its stored keys directly.

Is the Binance Spot API free to use?

Binance charges trading commission per executed order, and GET /api/v3/account/commission returns the rates that actually apply for a symbol: a standardCommission and a taxCommission block, each carrying maker, taker, buyer, and seller rates, plus a discount block showing whether a discount is enabled for the account and the symbol and in which asset. Access itself comes from creating a key on the API Management page of a Binance account, and by default that key cannot trade, so trading has to be enabled there before any fee-bearing call will succeed.

Can I subscribe to real-time order and balance updates?

Yes. The /api/v3/userDataStream-style endpoints in the Stream group open and renew user-data streams that deliver real-time order, balance, and position updates over websocket. The REST API issues the listen key, and the websocket connection is then opened against the streaming endpoint.

Can I limit what my agent is allowed to do with the Binance Public Spot API?

Yes. Because Jentic One is self-hosted, you decide which Binance operations your agent may call, and Binance passes the trading symbol and order parameters in the query and body rather than a path segment, so you scope by operation. You can allow read-only calls such as GET /api/v3/klines, GET /api/v3/depth, and GET /api/v3/account while withholding order placement. Write operations like POST /api/v3/order, DELETE /api/v3/order, and margin borrow-repay via POST /sapi/v1/margin/borrow-repay stay unreachable unless you include them in the set the agent is permitted to use.