/vendor/bybit/AgentRouting.json or
/vendor/bybit/AgentContext.json directly.
bybit.com
Overview
Does bybit.com support MCP?
Yes. bybit.com has a confirmed MCP implementation. Full-scope trading and market data interface: live market data (orderbook, klines, tickers), account management, order placement and cancellation, and real-time WebSocket streams across spot, derivatives, and options markets via Bybit V5 API.
What agentic protocols does bybit.com support?
As of 2026-06-29, bybit.com has confirmed support for MCP and proprietary.
Is bybit.com's API publicly accessible or partner-gated?
Open.
Does bybit.com explicitly prohibit automated access?
Yes. bybit.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is bybit.com agent-ready?
Yes. bybit.com has a confirmed, agent-callable interface that supports end-to-end workflow completion.
Protocols
No usable finding available for this protocol (no legitimate scan available within the candidate window).
No evidence found that Bybit (bybit.com), a cryptocurrency derivatives and spot exchange, has any involvement with or implementation of the Agentic Commerce Protocol (OpenAI/Stripe). ACP launch partners and early implementors identified in search results are e-commerce and fintech merchants (e.g., Eco), not crypto trading platforms. Bybit's public-facing presence relates to crypto trading infrastructure, with no connection to ACP's product-catalog and checkout-flow model.
No evidence that Bybit (bybit.com) is among the 60+ named AP2 launch partners. Confirmed launch partners include payment networks and processors (Mastercard, American Express, Adyen, PayPal, Worldpay), crypto/wallet players (Coinbase, MetaMask, ConsenSys), enterprise platforms (Salesforce, ServiceNow, Intuit), and merchants (Etsy, Shopee, Lowe's Innovation Labs) — Bybit does not appear in any published partner list. No vendor-specific statement, integration documentation, or deprecation notice from Bybit regarding AP2 was found.
Full-scope trading and market data interface: live market data (orderbook, klines, tickers), account management, order placement and cancellation, and real-time WebSocket streams across spot, derivatives, and options markets via Bybit V5 API. Auth-gated tools require a Bybit API key and secret (or RSA private key); public market data tools are accessible without credentials.
Bybit operates two official MCP repos under the bybit-exchange GitHub org: bybit-exchange/bybit-mcp and bybit-exchange/trading-mcp, both referenced from the official Bybit API documentation at https://bybit-exchange.github.io/docs/. The API docs page explicitly promotes the MCP server for agent-driven trading workflows. Multiple independent third-party community implementations also exist (ethancod1ng, dlwjdtn535, sammcj, BCusack), confirming broad adoption, but the bybit-exchange org repos are the vendor-official surface.
MPP (co-authored by Stripe and Tempo) launched with named partners including Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and Visa — Bybit does not appear in any launch partner list or MPP-related announcement. Bybit is a cryptocurrency derivatives exchange with no documented connection to the Stripe/Tempo MPP ecosystem. No vendor-specific evidence found associating bybit.com with MPP adoption.
No evidence that bybit.com has implemented NLWeb. The first search confirmed that Bybit does operate a trading-focused MCP server (github.com/bybit-exchange/trading-mcp), but this is a proprietary MCP integration unrelated to NLWeb's /ask and /mcp schema.org-grounded endpoints. The second search found no bybit.com presence in any NLWeb launch partner list or related coverage; confirmed NLWeb adopters include Cloudflare and Salespeak, not Bybit.
Bybit is a cryptocurrency derivatives and spot trading exchange, not a retail merchant. No evidence was found of Bybit implementing or participating in the Universal Commerce Protocol (UCP) — the Google/Shopify-led open standard for AI-powered checkout discovery. Searches returned UCP documentation for retail merchants and Bybit's own trading MCP server (github.com/bybit-exchange/trading-mcp), which is unrelated to UCP. UCP targets retail e-commerce merchants integrating checkout into Google AI Mode; Bybit's product category falls outside the protocol's designed scope.
No evidence that Bybit has implemented or announced WebMCP, the Google/Microsoft W3C browser-native agent protocol. Bybit did launch a server-side MCP (Anthropic-style Model Context Protocol) for AI-driven multi-agent trading in April 2026, but that is a distinct protocol. Named WebMCP participants in launch and early-adoption coverage include Google, Microsoft, Mozilla, Apple, Cloudflare, and HubSpot — Bybit does not appear in any of these contexts.
No evidence that Bybit has adopted or integrated the x402 protocol. Search results surface the x402 ecosystem's confirmed partners (Coinbase, Cloudflare, Solana Foundation, Stellar) and Bybit's own payment product (Bybit Pay), but no intersection between Bybit and x402. Bybit Pay focuses on fiat/crypto merchant settlement and is unrelated to the HTTP 402 stablecoin micropayment mechanism.
No evidence found that Bybit has built or submitted an app for the OpenAI ChatGPT Apps platform (the Apps SDK / chatgpt.com/apps directory). Bybit operates its own internal AI product called TradeGPT (built on ChatGPT technology, embedded in the Bybit platform itself) and an 'AI Hub' skill layer, but these are Bybit-native surfaces, not apps published to OpenAI's ChatGPT app directory. The one ChatGPT-hosted result found (chatgpt.com/g/g-zNBXpFmfl) appears to be a third-party or community-created Custom GPT, not an official Bybit-published Apps SDK entry.
REST + WebSocket API for spot, USDT/USDC/inverse derivatives trading, order management, account data, and market data (v5 unified API)
Broker API layer: sub-account registration, user onboarding (one-click KYC signup), rebate management, and Broker Dedicated Connection (low-latency premium routing for institutional brokers); separate from the standard trading API and requires approved Broker Program enrollment plus IP whitelisting
Direct HTTP checks to bybit.com for /llms.txt, /.well-known/ai-plugin.json, /.well-known/agent, /AGENTS.md, and /agents.md all returned connection failures (HTTP 000), indicating the domain blocks automated requests from this environment. Web searches found no evidence of Bybit publishing any self-declaration convention file at a predictable URL on their domain. The GitHub result found (bybit-exchange/skills SKILL.md) is a repository-level skill file, not a domain-level self-declaration file at bybit.com itself.
Summary
Has agent interface: true
Verify and catalog both official Bybit MCP repositories (bybit-exchange/bybit-mcp and bybit-exchange/trading-mcp) in detail: confirm current endpoint lists, tool schemas, supported markets, and any rate limits or credential requirements beyond the API key pair. Also verify whether the proprietary Broker API layer has any MCP-exposed surface or remains entirely separate from the MCP offering.
AgentContext
Verified discrepancies
Vendor claim: Bybit's stated policy is that account reviews and withdrawal verifications are completed within defined timeframes (e.g., support emails citing a 48-hour response window), and that users will be notified once a compliance review is resolved. The platform presents withdrawals as accessible subject to standard verification.
What actually happens: In practice, documented user reports from 2024 through 2026 show accounts frozen indefinitely — with no clear timeline, no actionable instructions from support, and no meaningful communication until users escalate publicly or involve regulators. In one documented case, 14,000 USDT was locked for over 20 days before being released only after public escalation and UAE regulatory involvement, at which point the account was permanently closed. Multiple users report stated 48-hour review windows routinely stretching to 12+ days or months, with support responses being generic and non-committal.
Agent guidance: Do not assume a Bybit withdrawal or fund-access request will complete within any timeframe stated by Bybit support or documented policy. An agent initiating a withdrawal or fund transfer on Bybit should treat the transaction as unconfirmed until funds are verifiably received at the destination. Flag to the user that account-level freezes with no stated resolution timeline have been widely reported; any time-sensitive transaction requiring guaranteed fund availability should not rely solely on Bybit.
- CryptoBriefing reports a pattern of Bybit account freezes from May 2025 onward where funds were locked with no timeline or explanation; in one case 14,000 USDT was frozen over 20 days and only released after public escalation and UAE regulator involvement.
- CoinSpeaker documents specific dated cases: a Sept. 2024 €10,000 deposit inaccessible for 20+ days, a Feb. 2024 withdrawal restriction unresolved after 13 days with no support contact, and an Oct. 2025 €29,000 deposit that never appeared — despite Bybit's stated support and compliance processes.
Vendor claim: Bybit markets itself as a comprehensive crypto exchange supporting withdrawals across major cryptocurrencies and networks, implying that standard wallet address formats for BTC and ETH are supported without restriction.
What actually happens: Bybit does not support BTC withdrawals to native SegWit (bech32) addresses beginning with 'bc1', which are now the most common default output format in modern wallets. Only legacy addresses starting with '1' or P2SH addresses starting with '3' are accepted. Similarly, Bybit does not support ETH withdrawals via Smart Contract method — only Direct Transfer is permitted. These constraints are not surfaced during account onboarding or when initiating a trade, but produce a hard failure when an agent attempts a withdrawal to a non-supported address format.
Agent guidance: Before attempting a BTC withdrawal on Bybit, verify that the destination address begins with '1' or '3' — do not use native SegWit (bc1) addresses. For ETH withdrawals, ensure the destination is a standard EOA (externally owned account) and not a smart contract address. If the user's wallet defaults to bech32 or uses a contract wallet, the withdrawal will fail and the agent must request an alternative address format before submitting.
- Third-party fee aggregator documents that Bybit explicitly does not support bech32 BTC addresses ('bc1') for withdrawals, only legacy ('1') and P2SH ('3') formats, and does not support ETH Smart Contract withdrawals.
- Bybit's own help center FAQ on crypto withdrawals references withdrawal limits and supported formats, serving as the platform's primary disclosure point — constraints are buried in FAQ rather than presented upfront during withdrawal flows.
Human handoff required for
Escalate to a human when a Bybit withdrawal or fund transfer has not completed within the timeframe stated by Bybit support (e.g., 48 hours) and funds have not arrived at the destination — particularly if the account has entered a compliance or account-review state with no actionable resolution instructions from support.
- Multiple independently-reported incidents from 2024–2026 show Bybit accounts frozen indefinitely after support cites short review windows; in one documented case 14,000 USDT was locked for over 20 days and only released after public escalation and UAE regulatory involvement, at which point the account was permanently closed.
- Bybit support responses during freeze periods are reported as generic and non-committal, with stated 48-hour review windows routinely stretching to 12+ days or months, leaving users with no actionable path to funds.
Escalate to a human when a time-sensitive transaction (e.g., arbitrage, margin call coverage, scheduled payment) depends on guaranteed fund availability from Bybit, because account-level freezes with no stated resolution timeline have been documented and cannot be ruled out at transaction initiation.
Escalate to a human when the user's intended BTC withdrawal destination address begins with 'bc1' (native SegWit / bech32 format), as Bybit does not support this address type and the withdrawal will hard-fail — the agent must obtain a legacy ('1') or P2SH ('3') address from the user before proceeding.
Escalate to a human when the user's intended ETH withdrawal destination is a smart contract wallet or contract address, as Bybit only supports Direct Transfer (EOA-to-EOA) and the withdrawal will hard-fail — the agent must confirm the destination is a standard externally owned account before submitting.
Escalate to a human when a Bybit account freeze has persisted beyond the stated review window and the user is considering public escalation or regulatory complaint as the only path to fund release, so that a human can advise on appropriate regulatory bodies (e.g., UAE VARA) and document the case before taking public action.
Five categories were checked for bybit.com. Discrepancy_pricing: searched for hidden fees, undisclosed charges, and deceptive pricing; found only an unverified social-media allegation about token-listing fees (denied by Bybit's CEO) and unrelated regulatory actions — no independently verified end-user pricing discrepancy was found. Discrepancy_availability: searched for ghost inventory, bait-and-switch pricing, or offers that fail at execution; no independent reports or regulatory findings substantiating a systematic availability discrepancy were found. Discrepancy_identity: searched for merchant-of-record ambiguity and liability deflection; Bybit's P2P counterparty structure is publicly documented and no enforcement actions alleging undisclosed identity issues were found. Discrepancy_policy: a finding was made — documented pattern of account freezes far exceeding stated review timelines (48 hours vs. weeks or months), with funds released in some cases only after public escalation or regulator involvement. Discrepancy_undisclosed_constraint: a finding was made — Bybit does not support BTC withdrawals to native SegWit (bc1) addresses or ETH withdrawals to smart contract addresses, constraints not disclosed during onboarding or trade initiation that cause hard withdrawal failures.