/vendor/binance/AgentRouting.json or
/vendor/binance/AgentContext.json directly.
binance.com
Overview
Does binance.com support MCP?
No confirmed MCP support was found for binance.com as of 2026-06-28.
What agentic protocols does binance.com support?
As of 2026-06-28, binance.com has confirmed support for x402 and proprietary.
Is binance.com's API publicly accessible or partner-gated?
Open.
Does binance.com explicitly prohibit automated access?
Yes. binance.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is binance.com agent-ready?
Partial. binance.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence that Binance (binance.com) is a launch partner, adopter, or implementer of the Agent2Agent (A2A) protocol. The confirmed launch partner list from the April 2025 Google announcement names over 50 firms including Atlassian, Box, Cohere, PayPal, Salesforce, SAP, and ServiceNow — Binance does not appear. No Binance-specific A2A documentation, announcement, or integration was found. Chose not_found rather than confirmed_absent because the absence is from public search results, not from a Binance-issued deprecation or exclusion statement.
No evidence that Binance is a participant in the Agentic Commerce Protocol (ACP). Confirmed launch partners include URBN, Coach, Kate Spade, Revolve, Ashley Furniture (merchants), and Shopify, Etsy (platforms), with Stripe and OpenAI as founding maintainers. Binance does have an unrelated 'Agentic Wallet' product (developers.binance.com/docs/agentic-wallet/welcome) and a crypto checkout product (Binance Pay), but neither involves ACP. Not confirmed_absent because no Binance-specific statement or deprecation notice rules it out — it simply does not appear.
No evidence of Binance appearing in any AP2 launch partner list or contributor announcement. Named partners across multiple sources include Mastercard, PayPal, Adyen, Coinbase, Coinbase, American Express, Revolut, Mysten Labs, Ethereum Foundation, and Worldpay — Binance is absent from all. No Binance-specific AP2 documentation, integration notice, or FIDO Alliance working group participation was found.
All MCP server implementations found for Binance are unofficial, third-party community projects (e.g., on GitHub by users such as ethancod1ng, AnalyticAce, nirholas, TermiX-official, danishashko) — none originate from Binance itself. The mention of 'miniprogram mcp server' in Binance developer changelogs (developers.binance.com) refers to a devtool CLI feature for building Binance Mini Programs, not an MCP protocol server for the exchange API. No official Binance announcement, documentation page, or vendor-published MCP server was found.
No evidence that Binance (binance.com) is among MPP's launch partners or adopters. Named launch partners and integrators confirmed in multiple sources include Anthropic, OpenAI, Shopify, DoorDash, Mastercard, Nubank, Ramp, Revolut, Standard Chartered, Visa, Lightspark, Alchemy, Dune Analytics, Cloudflare, and MultiversX — Binance does not appear in any of them. Binance's own crypto-exchange infrastructure has no documented MPP integration or announced roadmap for it.
No evidence that Binance (binance.com) has adopted or piloted NLWeb. Known Microsoft Build 2025 launch partners include Tripadvisor, Shopify, and other publishing/commerce platforms — no crypto exchanges appear among them. Binance's API surface is focused on trading, market data, and exchange operations, none of which map to NLWeb's schema.org-grounded conversational endpoint model.
No evidence found that Binance (binance.com) has implemented or announced support for the Universal Commerce Protocol. Multiple targeted searches returned only UCP ecosystem participants such as Shopify, Google, and Eco — not Binance. The /.well-known/ucp discovery endpoint on www.binance.com timed out (HTTP 000, connection not established), consistent with network blocking of the sandbox rather than a published UCP manifest; this prevents a definitive programmatic check but the broader web searches found zero Binance-specific UCP announcements, integrations, or documentation. Binance is a cryptocurrency exchange, not a retail merchant, and sits outside the retail/e-commerce merchant segment that UCP is designed for.
No evidence that binance.com has implemented WebMCP. The protocol is in early preview (Chrome 146 Canary, W3C draft), and known adopters include demo/lab sites and a third-party crypto price aggregator listed on webmcp.cool — none of which is Binance. No Binance-specific WebMCP announcement, tool registration, or documentation was found.
Merchant-side x402 payment settlement and endpoint discovery via B402 (Binance's x402 implementation), enabling AI agents and API clients to pay and discover HTTP endpoints that accept stablecoin micropayments over x402; covers V2 settle calls and Bazaar endpoint registration, not a general exchange trading or order-routing surface
Binance operates B402, its own branded x402-compatible implementation, documented at developers.binance.com/docs/onchainpay-x402. The B402 Bazaar discovery layer is Coinbase CDP-compatible (matching @coinbase/x402-fetch and the Python SDK blob shapes field-for-field), confirming genuine x402 protocol conformance. This is a vendor-specific x402 endpoint, not merely informational Binance Square blog posts about the protocol.
Spot Trading REST API: order placement, order management, account data, market data, and wallet operations for spot markets via HTTPS REST endpoints (/api/v3/*); supports HMAC, RSA, and Ed25519 key authentication
Fully documented at developers.binance.com. Spot REST API is the primary trading interface, with optional Simple Binary Encoding (SBE) response format and a parallel FIX API for low-latency order execution on the same endpoint set.
All direct HTTP checks to binance.com and developers.binance.com for standard self-declaration paths (llms.txt, AGENTS.md, agents.md, agents.txt, /.well-known/agent, /.well-known/agent-card.json) returned HTTP 000 with zero bytes — the domain is blocking the sandbox environment's network access entirely, making it impossible to confirm presence or absence of any file. The third-party results found were a community-built GitHub toolkit with its own llms.txt (nirholas/bnb-chain-toolkit) and a third-party C# client library (JKorf/Binance.Net) with an AGENTS.md, neither of which is published by Binance at binance.com itself. No vendor-specific evidence of a self-declaration file published by Binance on their own domain was found via web search.
Summary
Has agent interface: partial
Prioritize verification of the B402/x402 implementation: load developers.binance.com/docs/onchainpay-x402/b402-bazaar directly to confirm the settle API auth headers, endpoint URL structure, and whether Bazaar registration requires any out-of-band onboarding. Separately, check developers.binance.com API reference pages for any embedded MCP or IDE connector links per pattern #9, as the developer portal was not directly fetched during this pass.
AgentContext
Verified discrepancies
Vendor claim: Binance's terms of use describe the user's counterparty as 'Binance Operators,' defined broadly as 'all parties that run Binance,' giving the impression that the user is contracting with a single, identifiable platform entity responsible for their transactions and any resulting disputes.
What actually happens: Courts in multiple jurisdictions have found that this structure deliberately obscures the true legal counterparty. The Ontario Superior Court (Lochan v. Binance Holdings Limited, 2023 ONSC 6714, affirmed 2024 ONCA 784) held that the 'Binance Operators' definition made it impossible to identify the actual counterparty. A U.S. federal court's CFTC consent findings (2023 WL 10448932, N.D. Ill.) explicitly described Binance's model as a 'maze of corporate entities designed to obscure the ownership, control, and location of the Binance platform.' When users attempt to file a dispute or refund claim, they face ambiguity about which legal entity is responsible, with liability segregated across multiple entities (exchange, custody, broker-dealer) that are not clearly disclosed at the point of transaction.
Agent guidance: Do not assume a single, identifiable legal counterparty when transacting on Binance. Before initiating any transaction that may require a dispute or refund, verify which specific Binance entity (exchange, custody, or broker-dealer) is the legal counterparty for that specific product type under the current 2026 Terms. If the product is an OTC or swap, the counterparty may be Nest Trading Limited rather than the main exchange entity. Confirm the applicable arbitration venue and entity before committing funds, as filing a claim against the wrong entity risks dismissal.
- The Ontario Superior Court found in Lochan v. Binance Holdings Limited (2023 ONSC 6714) that Binance's 'Binance Operators' definition was problematic because it obscured the identity of the true counterparty, a finding affirmed on appeal in 2024 ONCA 784.
- Legal analysis of Binance's 2026 Terms confirms that under prior Terms of Use (2017–2025) users contracted with an undefined group of 'Binance Operators,' and that CFTC consent findings characterized this as a 'maze of corporate entities designed to obscure ownership, control, and location of the Binance platform.'
Vendor claim: Binance.com presents itself as a globally accessible cryptocurrency exchange where users can trade, deposit, and withdraw across a wide range of assets and regions, without prominently flagging which jurisdictions, account states, or compliance triggers may silently restrict or terminate access mid-session.
What actually happens: Independent reports and regulatory records document that Binance applies geographic restrictions, compliance-driven account freezes, and service suspensions that are not clearly disclosed to users before they begin transacting. Users in affected jurisdictions (e.g., Nigeria, Canada, Netherlands, and FATF grey-listed countries) have experienced abrupt service terminations — sometimes with only days' notice — and in some cases had remaining fiat balances auto-converted to stablecoins without explicit prior consent. Binance.US lost USD deposit and withdrawal capability for over a year after banking partners withdrew following SEC action in June 2023, a constraint not visibly surfaced to users at account-opening. US users accessing Binance.com via VPN violate ToS and risk account closure, a constraint that can manifest mid-transaction rather than at onboarding.
Agent guidance: Before initiating any transaction on Binance.com, an agent must first verify the user's jurisdiction against Binance's current restricted-country list (published at binance.com/en/legal/list-of-prohibited-countries), confirm the account is not subject to any pending compliance review, and confirm the specific asset and fiat corridor intended are currently supported. For US-based users, confirm use is via Binance.US (not Binance.com), and verify that USD deposit/withdrawal is currently active. Do not assume that a capability visible in the UI is transactionally available — check Binance's announcements page for any active service suspensions in the relevant country or for the relevant asset before proceeding.
- LeoDex documents that Nigerian naira holders in 2024 had only days before remaining NGN balances were auto-converted to USDT upon Binance's suspension, and Dutch users received roughly one month's notice before exit — constraints not disclosed upfront at account creation.
- Arristor's 2026 guide reports that community reports from mid-2025 describe thousands of users in 'gray zone' border areas experiencing account closures when Binance updated its risk algorithms, with no advance disclosure of this possibility at onboarding.
- Eco.com support article confirms that VPN-based access to Binance.com from the US violates Binance's ToS and was cited in DOJ settlement terms, a restriction not prominently disclosed to users initiating trades.
Human handoff required for
Escalate to a human before initiating any dispute, refund claim, or legal action when it is unclear which specific Binance legal entity (e.g., exchange entity, Nest Trading Limited for OTC/swaps, custody entity, or broker-dealer entity) is the counterparty for the specific product being transacted, as filing against the wrong entity risks dismissal and the corporate structure has been judicially found to obscure this identity.
- The Ontario Superior Court in Lochan v. Binance Holdings Limited (2023 ONSC 6714, affirmed 2024 ONCA 784) held that Binance's 'Binance Operators' definition made it impossible for users to identify their actual legal counterparty.
- U.S. CFTC consent findings (N.D. Ill. 2023) explicitly described Binance's corporate model as a 'maze of corporate entities designed to obscure the ownership, control, and location of the Binance platform.'
Escalate to a human when a user's jurisdiction appears on or near Binance's restricted-country list, or when a compliance-driven account freeze or service suspension is detected mid-transaction, as abrupt terminations have historically occurred with little notice and have resulted in fiat balances being auto-converted to stablecoins without explicit user consent.
- Independent reports document that users in jurisdictions including Nigeria, Canada, and the Netherlands experienced abrupt Binance service terminations, sometimes with only days' notice and with fiat balances auto-converted to stablecoins without prior explicit consent.
- Binance's list of prohibited countries is published and updated at this URL; an agent must verify the user's jurisdiction against this list before initiating any transaction.
Escalate to a human when a US-based user attempts to transact on Binance.com (rather than Binance.US), or when there is any indication the user may be accessing Binance.com via VPN, as this violates Terms of Service and can result in mid-transaction account closure and fund inaccessibility.
- Binance.US lost USD deposit and withdrawal capability for over a year after banking partners withdrew following SEC action in June 2023, a constraint not visibly surfaced to users at account-opening or in the UI.
- Binance's Terms of Service prohibit US users from accessing Binance.com and prohibit VPN use to circumvent geographic restrictions, with account closure as a consequence that can materialize mid-transaction.
Escalate to a human before committing funds to any OTC trade or swap product on Binance where the counterparty may be Nest Trading Limited rather than the main exchange entity, as the applicable arbitration venue and liability assignment differ and are not clearly disclosed at the point of transaction.
- Binance's 2026 Terms restructure liability across multiple distinct entities including a separate OTC/swap counterparty (Nest Trading Limited), but this remediation has not been independently verified as fully resolving consumer-facing counterparty ambiguity.
- The Ontario Court of Appeal (2024 ONCA 784) affirmed that Binance's historical multi-entity structure made counterparty identification impossible for users, establishing the ongoing risk that entity-specific liability assignments are not effectively communicated at transaction time.
Escalate to a human when a deposit, trade, or withdrawal cannot be completed for an asset or fiat corridor that appeared available in the Binance UI, as UI-visible capabilities have been documented to be unavailable due to undisclosed active service suspensions, banking partner withdrawals, or asset delistings not prominently flagged to users before transaction initiation.
- Binance.US lost USD deposit and withdrawal functionality for an extended period after banking partners withdrew following regulatory action, a constraint that was not visibly surfaced to users initiating transactions through the standard UI.
- Binance's announcements page documents active service suspensions by country and asset; agents are directed to check this before proceeding, implying that UI availability alone is not a reliable signal of transactional availability.
Five categories were checked for Binance.com. Discrepancy_pricing: searches found no verified finding of a gap between advertised and charged prices at the point of transaction; major regulatory actions (CFTC, SEC, DOJ) concerned AML and unlicensed operations rather than hidden checkout fees. Discrepancy_availability: no systematic pattern of bait-and-switch pricing or ghost inventory was found; inherent crypto slippage was noted as a disclosed market mechanism, not a vendor-specific undisclosed discrepancy. Discrepancy_identity: a finding was confirmed by two independent sources — an Ontario Superior Court judgment (affirmed on appeal) and U.S. CFTC consent findings — both establishing that Binance's multi-entity corporate structure deliberately obscures the legal counterparty identity, creating material risk in dispute and refund scenarios. Discrepancy_policy: no verified gap between stated and enforced customer-facing policies was found; account freezes and geographic restrictions were documented as consistent with disclosed terms. Discrepancy_undisclosed_constraint: a finding was confirmed across multiple independently corroborated reports showing abrupt, poorly-disclosed geographic service terminations, fiat auto-conversions, and banking corridor outages that users typically discover mid-transaction; Binance.US USD withdrawal outage following the June 2023 SEC action is the clearest documented instance. No scan was blocked, but the 2026 Binance Terms restructuring of entity liability has not yet been independently reverified as resolving the counterparty ambiguity identified in the identity finding.