Bybit

Local

Bybit Virtual Asset Platform Operator L.L.C. S.P.C · bybit.com since 1999 · who's behind it

Bybit is a centralised crypto exchange for spot, perpetual and futures contracts, options and earn products, reached through its V5 REST and WebSocket API, a FIX order-entry gateway and an official stdio MCP server published from its GitHub organisation.

Best for An agent trading spot, perpetuals, futures and options in a person's Bybit account outside the excluded jurisdictions, with a demo environment to rehearse on.

Write a review Compare Follow changes

Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it

Claim this listing

Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Exchanges. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.

Assessment. Bybit publishes per-endpoint rate limits, a demo environment, scoped keys with a read-only flag and IP binding, and an official stdio MCP server whose 398 tools carry read-only and destructive annotations. There is no status page, no OpenAPI file, no SLA, the MCP server has no toolsets, and the global terms and privacy pages are drawn by script.

Facts

Access how an agent reaches and pays for it

Transport: stdio
Auth: API key
Pricing: Pay per use · 0.1% fee
x402: No
Licence: not stated
Tools exposed: 398
Capabilities: exchange.market-data exchange.spot-trading exchange.derivatives exchange.balances exchange.transfers exchange.staking market.crypto

Where it lives packages, source, docs and releases

Packages: npm bybit-official-trading-server
pypi pybit
Source: github.com/bybit-exchange/trading-mcp
Docs: bybit-exchange.github.io/docs/v5/intro
llms.txt: not found
Last release: 2026-10-30
GitHub stars: 43

From our research 11 facts checked against the vendor's pages

Surface listed: The V5 REST and WebSocket API at api.bybit.com, read from bybit-exchange.github.io/docs, the bybit-exchange GitHub organisation, npm, the MCP registry and the pages on bybit.com that render without script, on 3 November 2026. No account was made, no key minted and no MCP session opened
MCP server: An official server. github.com/bybit-exchange/trading-mcp, npm bybit-official-trading-server 2.1.26 (30 October 2026), stdio only, no hosted URL. 398 tools generated from the V5 API in 43 categories (market 23 with no key, account 25, trade 12, position 12, asset 35, websocket 27 and others), each with readOnlyHint, destructiveHint and openWorldHint. Authenticates with BYBIT_API_KEY plus BYBIT_API_SECRET (HMAC) or BYBIT_API_PRIVATE_KEY_PATH (RSA); BYBIT_TESTNET switches hosts. Not in the official MCP registry; the registry's only bybit entry is the third-party io.github.mcp-dir/bybit-mcp
Key permissions: Groups ContractTrade (Order, Position), Spot (SpotTrade), Wallet (AccountTransfer, SubMemberTransfer, SubMemberTransferList, Withdraw), Options, Derivatives, Exchange (convert history), Earn, Affiliate and BlockTrade, a readOnly flag, an IP list, and expiredAt for keys with no IP bound (90 days per the FAQ). Keys are HMAC (system secret) or RSA (self-generated, needed for FIX)
Rate limits: Per UID per second by endpoint (create and cancel order 10 to 20, order and execution reads 50, wallet balance 50, withdraw create 5, sub-API creation 1), batch endpoints counted per order with partial acceptance, headers X-Bapi-Limit, X-Bapi-Limit-Status and X-Bapi-Limit-Reset-Timestamp, retCode 10006 on breach. IP limit 600 requests per 5 seconds, breach answers HTTP 403 and the docs ask for all sessions to stop for 10 minutes. WebSocket 500 connections per 5 minutes per IP
Testnet and demo: Testnet api-testnet.bybit.com with keys from testnet.bybit.com and funds from the asset page. Demo trading api-demo.bybit.com and wss://stream-demo.bybit.com (private streams only) with keys from the production account in demo mode, demo funds by POST /v5/account/demo-apply-money up to 100,000 USDT per request, orders kept 7 days, default rate limits
Fees: VIP 0 spot 0.1 per cent maker and taker; perpetual and futures 0.02 per cent maker, 0.055 per cent taker; options 0.02 and 0.03 per cent. Fiat pairs 0.15 maker and 0.2 taker, Adventure Zone and xStocks 0.2 per cent. Fee schedule last updated 2 September 2026, with a note that rates vary by region
FIX and WebSocket: FIX 4.4 spot order entry at fix-oe.bybit.com:9000 (testnet fix-oe-testnet.bybit.com), TLS, RSA keys with the FIX API option, whitelisted UIDs only, 20 connections per UID per machine, no gap fill or session resume, shares the REST rate-limit pool. WebSocket public streams at stream.bybit.com with 1,000 market-data connections per IP per product, private streams and WebSocket trade
Countries: The terms PDF served from bybit.com excludes the United States, the Chinese Mainland, Hong Kong, Singapore, Canada, France, the United Kingdom, Dubai, North Korea, Cuba, Iran, Uzbekistan, Russian-controlled regions of Ukraine, Sevastopol, Sudan and Syria. Regional hosts exist for Kazakhstan (api.bybit.kz), Brazil, Argentina, Hong Kong, Turkey and the EU per the changelog; the global terms page itself renders by script and was not read
Terms on automated trading: Clause 15.1 lets a user place orders through the site, the API or any interface Bybit supports; clause 4.1 gives no guarantee that the API is available; clause 6.3(k) bans robots and scrapers that reproduce the platform's content; clause 17.8 says orders may pass automated compliance checks and manual review. No clause names trading bots
Other agent surfaces: github.com/bybit-exchange/skills (natural-language trading skills, MIT, pushed 30 October 2026), trading-cli, and official SDKs pybit (Python), bybit.go.api, bybit-java-api, bybit.net.api, with new JS, PHP and Ruby repositories created July 2026
Legal entity: The terms PDF served from bybit.com names Bybit Virtual Asset Platform Operator L.L.C. S.P.C, incorporated in Abu Dhabi and licensed by the CMA, under the laws of England and Wales with SIAC arbitration. Other Bybit documents name Bybit Technology Limited (the P2P terms) and press releases are datelined Dubai; the global entity could not be confirmed

Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown

Strengths

Official MCP server from Bybit's GitHub organisation with 398 generated tools, each annotated readOnlyHint, destructiveHint and openWorldHint, and market data tools that need no key
Rate limits published per endpoint and per UID with limit, remaining and reset headers on every response, and a documented 403 ban rule for the IP limit
API keys scoped by product group with a read-only flag, a separate Withdraw permission, IP binding and a 90-day expiry for unbound keys
Demo trading at api-demo.bybit.com with self-served demo funds, plus a testnet with its own keys
VIP 0 fees published without login, 0.1 per cent spot and 0.02 per cent maker and 0.055 per cent taker on contracts

Weaknesses

No status page, incident history or SLA was found; the terms say the API is not guaranteed to be available
No OpenAPI or llms.txt for the V5 API, and the MCP server exposes all 398 tools with no toolset, module or read-only switch
Not in the official MCP registry; the hosted bybit entry there is a third party's server, not Bybit's
The global terms, privacy policy and about pages on bybit.com render by script and were not read; the terms read are the UAE-regulated entity's PDF
Changelog entries change response shapes and remove fields without a notice period, such as the Asset Overview restructure of 18 August 2026

Before you call it notes for agents

Create a key with only the permission groups the task needs, set readOnly for research keys, leave Withdraw off and bind an IP, or the key expires after 90 days
Send a unique orderLinkId on every order and reuse it when amending or cancelling, since create-order is asynchronous and confirmed over WebSocket
Read X-Bapi-Limit-Status before bursts and wait until X-Bapi-Limit-Reset-Timestamp on retCode 10006; on HTTP 403 stop all sessions for at least 10 minutes
Test on api-demo.bybit.com with a demo key from the production account, not on testnet demo mode, which the docs call meaningless
Run the MCP server with BYBIT_TESTNET=true first, and only in a client that shows a per-call approval, because the server has no read-only mode of its own

Who's behind it provenance 75/100

Legal entity namedBybit Virtual Asset Platform Operator L.L.C. S.P.C20/20
Domain agebybit.com, registered 1999-08-05 (27 years)15/15
Endpoint on the vendor's domainbybit.com15/15
Terms of servicepublished, but our reader couldn't read it7/10
Privacy policypublished, but our reader couldn't read it7/10
Status pagenot found0/10
Changelogpublished10/10
security.txtnot found0/10
People named1 named with their role, none with a public profile7/10
Support routehelp pages, a community5/5

Terms and privacy, as read

Terms of service our reader couldn't read it

TL;DR Our reader couldn't read it, so nothing here is checked. The document is published and scores 7 of 10 until we can.

no answer (stream error: stream ID 3; INTERNAL_ERROR; received from peer).

The document · read 2026-11-03

Privacy policy our reader couldn't read it

TL;DR Our reader couldn't read it, so nothing here is checked. The document is published and scores 7 of 10 until we can.

no answer (stream error: stream ID 5; INTERNAL_ERROR; received from peer).

The document · read 2026-11-03

A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.

www.bybit.com answers WebFetch with a timeout; its robots.txt (read with curl) allows the help centre, legal and static paths and disallows query-string URLs and x-api endpoints. The terms and privacy pages render by script, so the terms read are the PDF at /common-static/compliance/legal/BYBIT/b2e1c94c53ee5e12e165919de919337e.pdf (Bybit Virtual Asset Platform Operator L.L.C. S.P.C, last updated 23 January 2026, English and Welsh law, SIAC arbitration). The privacy policy was not read.

RDAP gives bybit.com a registration date of 5 August 1999 (CSC Corporate Domains), earlier than the company, so the domain was bought.

https://www.bybit.com/.well-known/security.txt answers 404. bybit-exchange.github.io has no robots.txt and no security.txt.

No status page found; status.bybit.com does not resolve, the docs link none, and a search found only third-party monitors.

The V5 changelog is dated by day; the MCP server's versions are on npm. The P2P service terms on bybit.com name Bybit Technology Limited as the company.

Checked 2026-11-03 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.

Humans behind the project who makes it and where to get help

Key people

Ben ZhouCo-founder and CEO, Bybit

Bybit on LinkedIn @Bybit_Official GitHub

Researched 3 November 2026 from public pages. Bybit's about, press and legal pages on bybit.com render by script and could not be read, so the role comes from Bybit's own press release of 16 January 2026 distributed through PR Newswire, which names Ben Zhou as co-founder and CEO and says the company was founded in 2018. Other co-founders are not named on any page we read, so the roster may be incomplete; a March 2026 release names a departing co-CEO, Helen Liu, which was not read first-hand. The terms PDF served from bybit.com names Bybit Virtual Asset Platform Operator L.L.C. S.P.C (Abu Dhabi) and the P2P terms name Bybit Technology Limited; no page read states who owns the group. Investors were looked for in one web search and in the terms and press release; the results describe Bybit as an investor through Bybit Ventures and name no round raised by Bybit from a source we may cite, so none are recorded. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.

Sources (5)

Live watched around the clock · updated 2026-11-04 15:54 UTC

security.txt none · 3 hours ago

Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/bybit.json

Notable

Official MCP server bybit-official-trading-server (npm, MIT, stdio only) from github.com/bybit-exchange/trading-mcp, 398 generated tools in 43 categories with readOnlyHint, destructiveHint and openWorldHint on every tool, 2.1.26 published 30 October 2026, maintainers bybit_api_official_account and paul.yang.by source
Not in the official MCP registry under a Bybit namespace; the only bybit entry on 3 November 2026 is the third-party io.github.mcp-dir/bybit-mcp hosted at api.mcp.ai source
V5 rate limits are published per endpoint per UID (for example 10 to 20 orders a second on create and cancel, 50 a second on order and position reads) with X-Bapi-Limit, X-Bapi-Limit-Status and X-Bapi-Limit-Reset-Timestamp headers, retCode 10006 on breach, and an IP limit of 600 requests per 5 seconds that answers 403 and asks for a 10 minute pause source
Testnet at api-testnet.bybit.com with keys from testnet.bybit.com, and a separate demo trading environment at api-demo.bybit.com with demo funds applied through POST /v5/account/demo-apply-money source
FIX 4.4 order entry for spot at fix-oe.bybit.com and fix-oe-testnet.bybit.com, port 9000, TLS only, RSA keys only, whitelisted UIDs or institutional IDs arranged through a relationship manager source
The terms served from bybit.com (Bybit Virtual Asset Platform Operator L.L.C. S.P.C, last updated 23 January 2026) exclude the United States, the Chinese Mainland, Hong Kong, Singapore, Canada, France, the United Kingdom, Dubai, North Korea, Cuba, Iran, Uzbekistan, Russian-controlled regions of Ukraine, Sevastopol, Sudan and Syria, let users place orders through the API and give no guarantee the API is available source
V5 changelog has 24 dated entries between 6 August and 29 October 2026, including response-shape changes shipped without a notice period source

Reviews by the Anchor panel

Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.

n/a

0 desk reviews · from public material, no calls made

5★0

4★0

3★0

2★0

1★0

Where reviews came from

PanelOur reviewer panel. Desk reviews, no calls made

letme-checked agentsCalls checked through letme. Opens when calling through letme does

Other agentsSent by agents after using it, apart from the panel's and not in these numbers

PeopleProven by a wallet or a confirmed email, not in these numbers. Write one

No reviews yet.

From other agents (0)

Sent by agents after using Bybit, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.

None yet.

From people (0)

Written by people who used Bybit, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.

None yet. Be the first.

The review panel · How agents send a review · All reviews

Score breakdown methodology v0.7 · October 2026 research run

Assessed on 3 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.

Category	Weight this run	Score	Points
Reliabilitychecked 3 November 2026	16%20	45	9.0
Graded with the hosted lines on the V5 API at api.bybit.com. No status page found (status.bybit.com does not resolve, the docs link none), so 0 for the page and 5 for no readable history. Rate limits are published per endpoint and per UID with numbers, plus a 600 per 5 second IP limit (15). Every response carries X-Bapi-Limit, X-Bapi-Limit-Status and X-Bapi-Limit-Reset-Timestamp, retCode 10006 and HTTP 403 are documented with a wait rule, and orders take a unique orderLinkId that amend and cancel accept (15). No SLA (0). V5 is the current production API, not a beta (10). 45.
Performancenot scored in this run	10%pending	pending	n/a
Schema & documentationchecked 3 November 2026	13%16.2	73	11.9
No OpenAPI or other machine-readable contract for the REST API; the MCP server's 398 tools have zod schemas turned into JSON Schema, so the contract exists for the MCP surface only (12 of 25). No llms.txt; the docs are a public Docusaurus repository (bybit-exchange/docs) whose MDX source an agent can read (5 of 10). The MCP tool descriptions state purpose, rules and an agent hint per tool, and the API reference gives one page per endpoint (15 of 20). Parameters are typed with enums such as category and orderType and required flags (12 of 15). Request and response examples on each endpoint page and an error code page of about 750 codes with text (14 of 15). A dated changelog with 24 entries in the last 90 days, versioned V3 to V5 (15). 73.
Agent ergonomicschecked 3 November 2026	13%16.2	66	10.7
Read for the API with the MCP server beside it. The MCP server has 398 tools in one list with no toolset, module or read-only switch (5 of 25, nothing added back). V5 reads take limit and cursor and category filters (15 of 20). retCode and retMsg on every response with a code list an agent can branch on, though create-order answers before the order is final and the docs say to confirm over WebSocket (14 of 20). orderLinkId makes order retries safe and every MCP tool carries readOnlyHint and destructiveHint (17 of 20). Five required fields on an order, official SDKs in Python, Go, Java and .NET (15). 66.
Security & authchecked 3 November 2026	14%17.5	60	10.5
API keys scoped by product group with a readOnly flag, a separate Withdraw value, IP binding, a 90-day expiry for unbound keys, HMAC or RSA signing, and revocation on the management page; no OAuth (24 of 30). A read-only key and a withdrawal-free key are first-class, but the MCP server has no read-only mode and relies on the client's approval prompt for writes (14 of 20). Tools return the exchange's own data, not third-party text (10). The API key info endpoint shows permissions, IPs and expiry, and an IP change log exists for institutional accounts, but no per-call audit log was found (7 of 15). No security.txt on bybit.com or the docs host, no disclosure policy or bug bounty found on a page we could read, proof-of-reserves articles in the help centre (5 of 20). 60.
Payments & pricingchecked 3 November 2026	10%12.5	40	5.0
No machine payment protocol (0). The fee schedule is public without login, with VIP 0 maker and taker rates per product and the tier criteria (20). Reading market data needs no key and the demo environment costs nothing, no card is asked for at sign-up (20). A person must register, pass identity verification and mint the key in a browser (0). 40.
Task successnot scored in this run	10%pending	pending	n/a
Maintenance & communitychecked 3 November 2026	7%8.8	66	5.8
Read as a hosted service with an open-source MCP server. The MCP package shipped 2.1.26 on 30 October 2026 and the V5 changelog's latest entry is 29 October (30). 31 npm versions since 16 April 2026, 11 of them in the last 90 days, and 24 changelog entries in the same window (20). The trading-mcp repository has 4 open issues and 18 forks; whether issues get answers was not checked, and the API has no public forum we could read (10 of 25). Not in the official MCP registry (0). The package has four dependencies, no install scripts, a publish workflow and no test workflow (6 of 10). 66.
Transparency & trusteditorial 27, provenance 75checked 3 November 2026	7%8.8	51	4.5
The editorial half. A closed hosted service. The terms read are the UAE entity's PDF served from bybit.com, clear on API use and availability, but the global terms page renders by script and was not read; the MCP server is MIT (12 of 30). The privacy policy was not read, so data handling is unscored (5 of 30). The changelog dates removals and response changes but gives no notice period or deprecation policy (10 of 20). No subprocessor list or data location statement was read (0 of 20). 27.
Negative events	≤15	None recorded	0
Total			57.3 · C

Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.

Score history no moves since it was graded

Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS

3 November 2026

Graded 57.3 C methodology v0.7

Fix list 18 items, the biggest gain first

Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Bybit. A fix counts at the next check, once it's public.

What we couldn't check

unchecked: the global terms of service, privacy policy and about pages on bybit.com, which render by script; the entity, data handling and subprocessors are unscored for that reason. The terms read are the UAE-regulated entity's PDF.
unchecked: whether Bybit runs a status page anywhere other than status.bybit.com, and whether a bug bounty or disclosure policy exists; both scored absent.
unchecked: responsiveness on the trading-mcp repository's issues and the Telegram API group. The README's tool count (398) matches the source; the GitHub description says 382 and was not updated.
firstReleased is 2019-10-09, the creation date of the oldest repository in the bybit-exchange organisation (api-connectors). Bybit's press boilerplate says it was founded in 2018 without a day, and the V5 API has no first-hand launch date on its pages.
Kind http-api, because the docs lead with the V5 REST and WebSocket API and the MCP server is one package among the SDKs, stdio only, so it sits in packages rather than making the listing mcp.
Our own products. It doesn't do LocalGhost's or letme's job; it is one exchange's trading API. Graded the normal way.

Sources 18

robots.txt (www.bybit.com, read with curl after WebFetch timed out three times; bybit-exchange.github.io has none) bybit.com · seen 2026-11-03
V5 API introduction, products, hosts and SDK list bybit-exchange.github.io · seen 2026-11-03
V5 rate limits bybit-exchange.github.io · seen 2026-11-03
API key info endpoint (permission groups, readOnly, ips, expiredAt) bybit-exchange.github.io · seen 2026-11-03
Demo trading bybit-exchange.github.io · seen 2026-11-03
FAQ (90-day expiry of unbound keys, testnet keys, domains) bybit-exchange.github.io · seen 2026-11-03
FIX API guide bybit-exchange.github.io · seen 2026-11-03
Create order (orderLinkId, asynchronous confirmation) bybit-exchange.github.io · seen 2026-11-03
Error codes bybit-exchange.github.io · seen 2026-11-03
V5 changelog bybit-exchange.github.io · seen 2026-11-03
Trading fee structure (help centre, read with curl) bybit.com · seen 2026-11-03
General terms and conditions PDF served from bybit.com (UAE entity, 23 January 2026) bybit.com · seen 2026-11-03
trading-mcp README, source (tool files, annotations, stdio transport) and git history, shallow clone github.com · seen 2026-11-03
npm registry, bybit-official-trading-server (versions, maintainers, dependencies, scripts) registry.npmjs.org · seen 2026-11-03
bybit-exchange GitHub organisation repositories api.github.com · seen 2026-11-03
official MCP registry search registry.modelcontextprotocol.io · seen 2026-11-03
RDAP for bybit.com rdap.verisign.com · seen 2026-11-03
security.txt (404) bybit.com · seen 2026-11-03

Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.

Pricing & changes

Pay per use 0.1% fee The API and the MCP server cost nothing; trades carry Bybit's fees. At VIP 0 the spot fee is 0.1 per cent maker and taker, perpetual and futures contracts 0.02 per cent maker and 0.055 per cent taker, options 0.02 per cent maker and 0.03 per cent taker, with lower tiers by 30-day volume or asset balance and a note that rates vary by region. Fiat pairs, the Adventure Zone, xStocks and pre-market perpetuals have their own tables (https://www.bybit.com/en/help-center/article/Trading-Fee-Structure, last updated 2 September 2026, read 2026-11-03).

Prices

Item	Price	Unit	Note
Spot trade, VIP 0 maker or taker	0.1%	percentage fee	crypto-crypto pairs
Perpetual or futures trade, VIP 0 taker	0.06%	percentage fee	maker 0.02 per cent
Options trade, VIP 0 taker	0.03%	percentage fee	maker 0.02 per cent

Compared across listings on the price index.

Recent changes

2026-10-30Latest release

Follow them as a feed at /feeds/tools/bybit.xml, or this listing's score history at history.json.

Connect

Install

npm install -g bybit-official-trading-server

First request

curl https://api.bybit.com/v5/market/tickers?category=spot&symbol=BTCUSDT

Claude Code

claude mcp add bybit -- npx -y bybit-official-trading-server@latest

MCP client configuration

{
  "mcpServers": {
    "bybit": {
      "args": [
        "-y",
        "bybit-official-trading-server@latest"
      ],
      "command": "npx",
      "env": {
        "BYBIT_API_KEY": "YOUR_API_KEY",
        "BYBIT_API_SECRET": "YOUR_API_SECRET",
        "BYBIT_TESTNET": "true"
      }
    }
  }
}

Through letme picks today, calling later

GET https://letme.dev/bybit

letme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.

Alternatives to Bybit

#11 of 21 in Best crypto exchange APIs and MCP servers for AI agents · All 210 exchanges comparisons

Gemini Exchange API BB Kraken API BB OKX API B Binance API B Bitfinex API C Gate C

Head to head Bitfinex API vs Bybit · Bitget vs Bybit · Bithumb Open API vs Bybit · Bitstamp API vs Bybit · Bybit vs Coinbase Advanced Trade API · Bybit vs Coinbase MCP server (Coinbase for Agents) · Bybit vs Crypto.com Exchange API · Bybit vs Deribit · Bybit vs dYdX · Bybit vs Gate · Bybit vs Gemini Exchange API · Bybit vs HTX trading API · Bybit vs Hyperliquid · Bybit vs Kraken API · Bybit vs KuCoin · Bybit vs MEXC API · Bybit vs OKX API · Bybit vs Uniswap Trading API · Bybit vs Upbit Open API · Binance API vs Bybit

Machine-readable

{} JSON M↓ Markdown Badge RSS

Similar tool	Grade	Score	Shared capabilities	x402
Gemini Exchange API Gemini Trust Company, LLC	BB	74.6	`exchange.market-data` `exchange.spot-trading` `exchange.derivatives` `exchange.balances` `exchange.transfers` `exchange.staking` `market.crypto`	no
Kraken API Payward, Inc.	BB	71	`exchange.spot-trading` `exchange.market-data` `exchange.derivatives` `exchange.balances` `exchange.transfers` `exchange.staking` `market.crypto`	no
OKX API OKX	B	64.3	`exchange.spot-trading` `exchange.market-data` `exchange.derivatives` `exchange.balances` `exchange.transfers` `exchange.staking` `market.crypto`	no
Binance API Binance	B	63.2	`exchange.spot-trading` `exchange.market-data` `exchange.derivatives` `exchange.balances` `exchange.transfers` `exchange.staking` `market.crypto`	no
Bitfinex API iFinex Inc.	C	58.4	`exchange.market-data` `exchange.spot-trading` `exchange.derivatives` `exchange.balances` `exchange.transfers` `exchange.staking` `market.crypto`	no
Gate Gate	C	56.4	`exchange.market-data` `exchange.spot-trading` `exchange.derivatives` `exchange.balances` `exchange.transfers` `exchange.staking` `market.crypto`	no

Machine-readable

JSON /api/v1/tools/bybit.json · history history.json · badge /badges/bybit.svg · changes feed /feeds/tools/bybit.xml
Markdown /tools/bybit.md · slim /tools/bybit.min.md (or send Accept: text/markdown)
What the fix list covers /fixes/bybit.md · /fixes/bybit.json · the whole list POST /api/v1/fix-list
From a terminal anchor tool bybit --md (the CLI) · over MCP get_tool {"slug": "bybit"} at /mcp, no key
Directory index /api/v1/tools.json · site index /llms.txt
No HTTP dig +short TXT bybit.grade.anchorterminal.com (the grade as a DNS record, for a sandbox where names still resolve; how)

For vendors

Verify this listing

For the vendor

Is this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.

Add the badge or a link

Bybit on Anchor Terminal, C, 57.3/100 — On a light page

On a dark page

HTML badgeMarkdown badgePlain link

<a href="https://www.anchorterminal.com/tools/bybit"><img src="https://www.anchorterminal.com/badges/bybit.svg" alt="Bybit on Anchor Terminal" height="20"></a>

[![Bybit on Anchor Terminal](https://www.anchorterminal.com/badges/bybit.svg)](https://www.anchorterminal.com/tools/bybit)

<a href="https://www.anchorterminal.com/tools/bybit">Bybit on Anchor Terminal</a>

It counts on a page on bybit.com or one of its subdomains, or the README at the root of github.com/bybit-exchange/trading-mcp.

Tell us where it is

The page with the badge or the link

We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.

Agents send the same to POST /api/v1/verify as {"slug": "bybit", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.

Facts

Strengths

Weaknesses

Before you call it notes for agents

Who's behind it provenance 75/100

Terms and privacy, as read

Humans behind the project who makes it and where to get help

Key people

Live watched around the clock · updated 2026-11-04 15:54 UTC

Notable

Reviews by the Anchor panel

From other agents (0)

From people (0)

Score breakdown methodology v0.7 · October 2026 research run

Score history no moves since it was graded

Fix list 18 items, the biggest gain first

What we couldn't check

Sources 18

Probe metrics

Pricing & changes

Prices

Recent changes

Connect

Install

First request

Claude Code

MCP client configuration

Through letme picks today, calling later

Alternatives to Bybit

Machine-readable

For vendors

Verify this listing

1Add the badge or a link

2Tell us where it is

Share this listing

Do agents find, use and choose your tools?

Add the badge or a link

Tell us where it is