bingx-net

A set of coding conventions for using the BingX.Net C#/.NET library to connect to the BingX cryptocurrency exchange. It covers client setup, result checking, market symbols, REST APIs, and WebSocket APIs.

In plain words
What is it for?
Use it when generating or reviewing C#/.NET code for BingX market data, accounts, trading, spot markets, perpetual futures, subaccounts, or WebSocket subscriptions.
Why use it?
It keeps exchange integrations consistent with the library already used by the codebase and avoids writing unsupported direct HTTP calls to BingX endpoints.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/jkorf/bingx.net/bingx-net
Clone the repo
git clone --depth 1 https://github.com/JKorf/BingX.Net

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 907 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00907
Opus 5 $0.00000 $0.00453
Sonnet 5 $0.00000 $0.00181
Haiku 4.5 $0.00000 $0.00091

Measured 3d ago against content hash 037c806eb86e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bingx-net scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/bingx-net.mdc · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

BingX.Net Conventions

This codebase uses BingX.Net for BingX exchange access. Do not write raw HttpClient calls to BingX endpoints.

Client setup pattern

using BingX.Net;
using BingX.Net.Clients;

var restClient = new BingXRestClient(options =>
{
    options.ApiCredentials = new BingXCredentials("API_KEY", "API_SECRET");
});

For public market data only, no credentials are needed: new BingXRestClient().

Result pattern

All methods return WebCallResult<T> (REST) or CallResult<T> (WebSocket). Always check .Success before reading .Data:

var ticker = await restClient.SpotApi.ExchangeData.GetTickersAsync("BTC-USDT");
if (!ticker.Success) { /* ticker.Error */ return; }
var price = ticker.Data.Single().LastPrice;

API surface

  • restClient.SpotApi.{ExchangeData|Account|Trading}
  • restClient.PerpetualFuturesApi.{ExchangeData|Account|Trading}
  • restClient.SubAccountApi
  • socketClient.SpotApi for Spot WebSocket subscriptions
  • socketClient.PerpetualFuturesApi for Perpetual Futures WebSocket subscriptions

BingX spot symbols use hyphenated names such as BTC-USDT. Perpetual futures methods also use symbols such as ETH-USDT.

Order placement

Let the library auto-generate clientOrderId. Do not pass a custom one unless required for an existing operational flow:

var order = await restClient.SpotApi.Trading.PlaceOrderAsync(
    "BTC-USDT", OrderSide.Buy, OrderType.Limit,
    quantity: 0.001m, price: 50000m, timeInForce: TimeInForce.GoodTillCanceled);

WebSocket pattern

var socketClient = new BingXSocketClient();
var sub = await socketClient.SpotApi.SubscribeToTickerUpdatesAsync(
    "BTC-USDT",
    update => { /* update.Data.LastPrice */ });
if (!sub.Success) { /* sub.Error */ return; }

// On shutdown:
await socketClient.UnsubscribeAsync(sub.Data);

Multi-exchange code

For exchange-agnostic code, use CryptoExchange.Net.SharedApis:

using CryptoExchange.Net.SharedApis;

var shared = new BingXRestClient().SpotApi.SharedClient;
var ticker = await shared.GetSpotTickerAsync(
    new GetTickerRequest(new SharedSymbol(TradingMode.Spot, "BTC", "USDT")));

Read the full file on GitHub · 104 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 104 lines · 0 tokens per session scan A 037c806eb86e

Subscribe to this mod's changes

bingx-net is a cursor rule published in the GitHub repository JKorf/BingX.Net (21 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 907 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.