Binance's API covers spot, margin and futures trading, market data and account endpoints over REST, WebSocket and FIX, with a free spot testnet and a remote MCP server, documented on 30 October 2026, that trades inside a dedicated Agentic sub-account.
Best for An agent trading a funded Binance account outside the prohibited countries, with the deepest set of markets in this group and a free testnet.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
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. Binance publishes numeric rate limits, a free testnet with FIX, connectors in eight languages and, since late October 2026, a remote MCP server that trades only in a dedicated sub-account with no withdrawal scope. There is no status page, the terms and privacy notice could not be read, and the MCP tool list is not published.
Facts
Access how an agent reaches and pays for it
- Transport
- Streamable HTTP
- Endpoint
https://agent.binance.com/mcp/agentic- Auth
- OAuth or key
- Pricing
- Pay per use · 0.1% fee
- x402
- No
- Licence
- Proprietary hosted service under Binance's Terms of Use, which load by script and weren't read. The API docs, connectors, CLI and Skills Hub are open on GitHub under MIT
Where it lives packages, source, docs and releases
- llms.txt
- published
- Last release
- GitHub stars
- 4.9k
From our research 13 facts checked against the vendor's pages
- Surface listed
- The spot REST API at api.binance.com/api/v3, with its WebSocket, FIX and futures siblings, read from developers.binance.com, testnet.binance.vision, binance.com support pages and the binance GitHub organisation on 3 November 2026. No account was made, no key was used and no MCP session was opened
- MCP server
- Official, remote, at https://agent.binance.com/mcp/agentic over Streamable HTTP. OAuth in a desktop browser with scopes market data, account, trade and transfer, on a dedicated Agentic sub-account; no withdrawal scope; confirmation before orders, cancels and transfers. Tool count not published; docs dated 30 October 2026; not in the official MCP registry. Supported clients per the docs are Claude Code, Claude Desktop, Codex CLI, ChatGPT, VS Code and Grok Bot
- Key permissions
- Reading, spot and margin trading, futures and withdrawals, with an IP access restriction. Unrestricted-IP HMAC keys are reading only since 30 January 2023, withdrawals need an IP restriction, and keys need a Verified Plus account. FIX needs the FIX_API or FIX_API_READ_ONLY permission
- Rate limits
- Per IP, as weights per endpoint. 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 orders a day, 61,000 raw requests per 5 minutes, per exchangeInfo. 429 with Retry-After, 418 bans of 2 minutes to 3 days for repeat offenders, 403 for WAF blocks. FIX order entry 10,000 messages per 10 seconds
- Testnet
- testnet.binance.vision with REST (/api only), WebSocket API and streams, and FIX hosts, keys by GitHub login or registered RSA and Ed25519 public keys, virtual balances, resets about monthly with no notice
- Countries
- Prohibited per Binance's list of 27 February 2024 are Canada, the Netherlands, the United States, Cuba, North Korea, Iran, Syria, and Crimea and non-government-controlled areas of Ukraine, plus other places Binance designates. Binance.US is a separate exchange
- Fees
- 0.1 per cent standard spot fee for regular users per the fee FAQ. The maker and taker table and futures fees load by script and weren't read
- FIX and WebSocket
- FIX 4.4 over TLS (spot only) with order entry, drop copy and market data sessions and SBE ports, Ed25519 keys only. WebSocket API at ws-api.binance.com and market streams; testnet twins of each
- Terms on automated trading
- Not read. The Terms of Use at binance.com/en/terms load by script and answered with navigation only. The Skills Hub README says the person is responsible for all trading decisions and that Binance may change or discontinue the feature
- Skills and CLI
- binance-skills-hub, 21 skills under MIT for OpenClaw, Claude Code and similar, installed with npx skills add; the binance skill drives binance-cli (Rust, v2.2.0 on 20 October 2026) with profiles for prod, testnet and demo
- SDKs
- Official connectors for Python, JavaScript, TypeScript, Java, Go, Rust, PHP, Ruby and .NET on GitHub, most pushed in October 2026; a Postman collection; a Swagger spec last pushed in October 2024
- Status
- No status page found on binance.com or in the API docs
- Legal entity
- Not named on a page we could read. The about page lists three Abu Dhabi Global Market entities (Nest Exchange Limited, Nest Clearing and Custody Limited, Nest Trading Limited) regulated by the FSRA; Wikipedia gives Binance Holdings Ltd.
Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- Rate limits published as per-endpoint weights with 6,000 a minute, 50 orders per 10 seconds and Retry-After on 429 and 418
- Spot testnet with REST, WebSocket and FIX endpoints, virtual balances and production limits, free with a GitHub login
- Official remote MCP server with OAuth scopes, an isolated Agentic sub-account, no withdrawal scope and confirmation before writes
- Keys with reading, trading, futures and withdrawal permissions; unrestricted-IP HMAC keys can only read and withdrawals need an IP restriction
- Dated changelog since 2018 with retirement dates announced months ahead, llms.txt and llms-full.txt
Weaknesses
- No status page or incident history found on binance.com or in the API docs
- The Terms of Use and privacy notice load by script and weren't read, so what they say about bots and API use is unknown
- The MCP server's tool list and schemas are not published; the docs describe four scopes
- The maker and taker fee table loads by script; only the 0.1 per cent standard rate in a FAQ was read
- binance-api-swagger was last pushed in October 2024, so the machine-readable spec lags the docs
Before you call it notes for agents
- Read the X-MBX-USED-WEIGHT and X-MBX-ORDER-COUNT headers and stop on 429 for the Retry-After seconds; a 418 ban runs 2 minutes to 3 days
- Treat a 5xx on an order as unknown, not failed, and query the order by origClientOrderId before retrying
- Use an Ed25519 key with an IP restriction and only the reading and trading permissions; never enable withdrawals for an agent key
- Develop on testnet.binance.vision with BINANCE_API_ENV=testnet; it resets about monthly without notice
- For the MCP route, the person must fund the Agentic sub-account from the web UI first; the agent cannot move funds in from the main account
Who's behind it provenance 54/100
- Legal entity namednot found0/20
- Domain agebinance.com, registered 2017-04-01 (9 years)11/15
- Endpoint on the vendor's domainagent.binance.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.txtcould not be fetched0/10
- People named3 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.
the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere.
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.
the page has 0 words of text without a browser, so the document is drawn by script or sits elsewhere.
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.
The Terms of Use and the privacy pages answered our reader with navigation and footer only, so no contracting entity, governing law or data-handling statement was read. The about page names three ADGM entities as regulated subsidiaries, not as the contracting party.
RDAP gives binance.com a registration date of 1 April 2017.
https://www.binance.com/.well-known/security.txt has a Contact line (security@binance.com) and no Expires or Policy line, so its validity is unknown under RFC 9116.
No status page was found. www.binance.com/robots.txt allows the pages read and disallows */api/, */bapi/ and */my/; developers.binance.com and agent.binance.com have no robots.txt (404); api.binance.com and testnet.binance.vision disallow all crawlers, so no API call was made to either.
The spot API changelog is dated, newest 30 October 2026.
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
- Changpeng ZhaoCo-founder and former CEO, Binance
- Yi HeCo-founder and co-CEO, Binance
- Richard TengCo-CEO, Binance
Backed byMGX
Researched 3 November 2026 from public pages. The about page at binance.com/en/about names Changpeng Zhao as co-founder and former CEO and Yi He as co-CEO and co-founder; it names no other officer. Richard Teng's role rests on Wikipedia's Binance article. The Terms of Use load by script, so no page we read names the contracting company; the about page lists three Abu Dhabi Global Market subsidiaries. Investors were looked for on the about and press pages and in two searches. MGX of Abu Dhabi took a minority stake for $2 billion in March 2025, reported by The Block from a Binance release we could not read first-hand. No earlier outside investor was found; Binance describes the MGX deal as its first institutional investment. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-04 19:03 UTC
Probed every five minutes at https://agent.binance.com/mcp/agentic. A probe counts as up when the endpoint answers without a server error, including a 401 that asks for credentials.
- security.txt valid · 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/binance.json
Notable
- Binance runs an official remote MCP server at https://agent.binance.com/mcp/agentic (Streamable HTTP, OAuth in a desktop browser, scopes market data, account, trade and transfer). Agents trade spot, margin, convert and futures inside a dedicated Agentic sub-account that the person funds by hand, with no withdrawal scope and confirmation before orders, cancels and transfers. The docs pages are dated 30 October 2026. It is not in the official MCP registry, where nine Binance servers sit under io.github namespaces source
- The MCP server's protected-resource metadata names agent.binance.com as its authorisation server and lists no scopes. The tool list is not published outside tools/list, which we did not call source
- Rate limits are per IP, published per endpoint as weights. exchangeInfo reports 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 orders a day and 61,000 raw requests per 5 minutes. 429 carries Retry-After; an IP that keeps sending after 429 gets a 418 ban of 2 minutes to 3 days source
- FIX 4.4 over TLS for spot only, with order entry, drop copy and market data sessions, Ed25519 keys only, 10,000 messages per 10 seconds on order entry and a FIX_API or FIX_API_READ_ONLY key permission source
- The spot testnet at testnet.binance.vision has REST, WebSocket and FIX endpoints, virtual balances and the production limits, and resets about once a month without notice source
- binance-skills-hub (1,121 stars) publishes 21 agent skills, among them one that drives binance-cli (Rust, v2.2.0 on 20 October 2026) for spot, futures and convert; no local MCP server is in the organisation's repositories source
- The spot API changelog's newest entry is 30 October 2026, a reminder that the SBE 3:3 schema retires on 9 November; the oldest is 14 January 2018 source
- Binance lists Canada, the Netherlands, the United States, Cuba, North Korea, Iran, Syria and Crimea and non-government-controlled areas of Ukraine as prohibited, updated 27 February 2024 source
- No status page was found on binance.com or in the API docs; the Terms of Use and privacy notice load by script and answered our reader with navigation only
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.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using Binance API, 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 Binance API, 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.
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 | 9.0 | |
| Read with the hosted lines on the spot REST API. No status page was found on binance.com or in the API docs (0), so no incident record (5). Rate limits are published as per-endpoint weights with numbers from exchangeInfo, 6,000 request weight a minute, 50 orders per 10 seconds, 160,000 a day and 61,000 raw requests per 5 minutes, and FIX limits per session (15). 429 and 418 carry Retry-After, a 5xx is documented as unknown status to be queried, and orders take a client order id (15). No SLA (0). Generally available (10). 0 + 5 + 15 + 15 + 0 + 10 = 45. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 3 November 2026 | 13%16.2 | 14.0 | |
| The docs are Markdown in a public repository with a Postman collection and a Swagger spec, but the spec was last pushed in October 2024 (20 of 25). llms.txt and llms-full.txt on developers.binance.com (10). Each endpoint states its weight, parameters and notes on behaviour, with less on when not to use one (15 of 20). Enums for order types, time in force and symbol filters, required columns in the parameter tables (12 of 15). Request and response examples throughout and an error code list with messages (14 of 15). A dated changelog since 2018 with retirements announced months ahead, such as the 2 September 2026 field removal notified on 2 December 2025 (15). 20 + 10 + 15 + 12 + 14 + 15 = 86. | |||
| Agent ergonomicschecked 3 November 2026 | 13%16.2 | 12.3 | |
| limit on depth, trades and klines, a symbols filter on exchangeInfo and tickers, and SBE encoding, though fields cannot be selected (16 of 25). fromId, startTime, endTime and limit on history endpoints (16 of 20). Error codes with messages an agent can branch on, such as the rate limit and timestamp errors (17 of 20). newClientOrderId on orders, a cancel-replace endpoint and the 5xx unknown-status rule, but no idempotency key on other writes (12 of 20). Connectors in nine languages, a CLI with testnet and demo profiles, and a timestamped HMAC or Ed25519 signature on every private call (15). 16 + 16 + 17 + 12 + 15 = 76. | |||
| Security & authchecked 3 November 2026 | 14%17.5 | 12.6 | |
| API keys with HMAC, RSA or Ed25519 signatures, permissions for reading, trading, futures and withdrawals, an IP restriction, revocation in API Management, and OAuth with four scopes on the MCP server; no key expiry found (28 of 30). Read-only keys, sub-accounts, withdrawals only with an IP restriction, and the MCP server's isolated Agentic sub-account with no withdrawal scope and confirmation before writes (18 of 20). The API returns no untrusted content (10). Keys are listed in API Management and used weight is returned per call, but no per-call log for the operator was found (6 of 15). security.txt with a contact and no expiry, a Bugcrowd programme named in the proof-of-solvency repository, no certification read (10 of 20). 28 + 18 + 10 + 6 + 10 = 72. | |||
| Payments & pricingchecked 3 November 2026 | 10%12.5 | 4.4 | |
| No machine payment protocol (0). A 0.1 per cent standard spot fee is stated in the fee FAQ; the maker and taker table and futures fees load by script and weren't read (15 of 20). Public market data needs no key and the testnet is free with a GitHub login (20). A person signs up, passes Verified Plus verification, deposits and mints a key (0). 0 + 15 + 20 + 0 = 35. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 3 November 2026 | 7%8.8 | 7.1 | |
| Read as a closed service. The spot changelog's newest entry is 30 October 2026, the MCP docs are dated 30 October and binance-cli v2.2.0 shipped on 20 October (30). Changelog entries on 2 September, 18 September, 27 October and 30 October (20). A public changelog, connectors pushed in October and a Skills Hub merging pull requests weekly; issue replies not read (10 of 15). Official connectors in nine languages current as of October 2026; the MCP server is not in the official registry (15). Connector CI not read; the CLI publishes release installers (6 of 10). 30 + 20 + 10 + 15 + 6 = 81. | |||
| Transparency & trusteditorial 31, provenance 54checked 3 November 2026 | 7%8.8 | 3.8 | |
| The editorial half. A closed service whose Terms of Use couldn't be read; the docs, connectors, CLI and skills are MIT on GitHub (10 of 30). The privacy notice couldn't be read, so no retention or subprocessor statement was checked; the prohibited-countries list is public and dated (5 of 30). The changelog gives retirement dates for SBE schemas and FIX fields months ahead (16 of 20). No subprocessor or data-location statement read (0 of 20). 10 + 5 + 16 + 0 = 31. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 63.2 · B | ||
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
-
Graded 63.2 B methodology v0.7
Fix list 22 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 Binance API. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- unchecked: the Terms of Use and the privacy notice, which load by script and answered with navigation only, so the contracting entity, governing law, API and bot clauses and data handling are unread. The prohibited-countries list is from a readable legal page dated 27 February 2024.
- unchecked: the maker and taker fee table and futures fees. Only the 0.1 per cent standard spot fee in the fee FAQ was read.
- unchecked: the MCP server's tools and schemas. tools/list needs a signed-in account and was not called; the docs give four scopes and no tool count. Its launch date is not stated; the docs pages carry a last-modified date of 30 October 2026, and press coverage of a Binance Agent OS was not used.
- No status page was found on binance.com or in the docs; Binance.US has one and is a separate exchange. Scored absent.
- firstReleased is 14 January 2018, the oldest entry in the spot API changelog; the exchange launched in July 2017 per the about page.
- Kind http-api, not mcp. The MCP server is one route to the same markets, is weeks old and is documented without a tool list, while the REST, WebSocket and FIX APIs carry the docs, connectors and testnet.
- Legal entity left empty. No readable page names the contracting party; the about page lists ADGM subsidiaries and Wikipedia gives Binance Holdings Ltd.
- api.binance.com and testnet.binance.vision disallow all crawlers in robots.txt, so exchangeInfo was not called; the limit numbers come from the docs' sample response.
Sources 24
- robots.txt (www.binance.com) binance.com · seen 2026-11-03
- general API information (limits model, key types, 429 and 418) developers.binance.com · seen 2026-11-03
- limits page developers.binance.com · seen 2026-11-03
- exchangeInfo rateLimits sample developers.binance.com · seen 2026-11-03
- FIX API developers.binance.com · seen 2026-11-03
- spot API changelog (newest 30 October 2026, oldest 14 January 2018) developers.binance.com · seen 2026-11-03
- Agent Native overview developers.binance.com · seen 2026-11-03
- MCP server introduction developers.binance.com · seen 2026-11-03
- Binance MCP Server (scopes, sub-account, setup) developers.binance.com · seen 2026-11-03
- MCP protected-resource metadata agent.binance.com · seen 2026-11-03
- spot testnet testnet.binance.vision · seen 2026-11-03
- API key creation FAQ binance.com · seen 2026-11-03
- fee structure FAQ binance.com · seen 2026-11-03
- fee page (table loads by script) binance.com · seen 2026-11-03
- list of prohibited countries binance.com · seen 2026-11-03
- Terms of Use (navigation only) binance.com · seen 2026-11-03
- privacy page (navigation only) binance.com · seen 2026-11-03
- about page binance.com · seen 2026-11-03
- security.txt binance.com · seen 2026-11-03
- GitHub organisation repositories api.github.com · seen 2026-11-03
- binance-skills-hub, shallow clone github.com · seen 2026-11-03
- binance-cli, shallow clone (tags) github.com · seen 2026-11-03
- official MCP registry search registry.modelcontextprotocol.io · seen 2026-11-03
- RDAP for binance.com rdap.verisign.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 costs nothing to call. Spot trades carry a standard fee of 0.1 per cent for regular users per the fee FAQ; the maker and taker table on the fee page loads by script and wasn't read, nor were futures fees. Public market data and the spot testnet need no account; the testnet needs a GitHub login.
Prices
| Item | Price | Unit | Note |
|---|---|---|---|
| Spot trade, regular user | 0.1% | percentage fee | standard fee per the fee FAQ; maker and taker table not read |
Compared across listings on the price index.
Recent changes
- security.txt on binance.com is valid, the listing says unknown source
- Latest release
Follow them as a feed at /feeds/tools/binance.xml, or this listing's score history at history.json.
Connect
First request
curl https://api.binance.com/api/v3/ticker/price?symbol=BTCUSDTClaude Code
claude mcp add binance-mcp-server --transport http https://agent.binance.com/mcp/agenticMCP client configuration
{
"mcpServers": {
"binance-mcp-server": {
"url": "https://agent.binance.com/mcp/agentic"
}
}
}Through letme picks today, calling later
GET https://letme.dev/binanceletme.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 Binance API
#6 of 21 in Best crypto exchange APIs and MCP servers for AI agents · All 210 exchanges comparisons
Gemini Exchange API BBKraken API BBOKX API BBitfinex API CBybit CGate C
Head to head Binance API vs Bitfinex API · Binance API vs Bitget · Binance API vs Bithumb Open API · Binance API vs Bitstamp API · Binance API vs Bybit · Binance API vs Coinbase Advanced Trade API · Binance API vs Coinbase MCP server (Coinbase for Agents) · Binance API vs Crypto.com Exchange API · Binance API vs Deribit · Binance API vs Gate · Binance API vs Gemini Exchange API · Binance API vs HTX trading API · Binance API vs Hyperliquid · Binance API vs Kraken API · Binance API vs KuCoin · Binance API vs MEXC API · Binance API vs OKX API · Binance API vs Uniswap Trading API · Binance API vs Upbit Open API · Binance API vs dYdX
Machine-readable
| 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 |
| Bitfinex API iFinex Inc. | C | 58.4 | exchange.market-data exchange.spot-trading exchange.derivatives exchange.balances exchange.transfers exchange.staking market.crypto | no |
| Bybit Bybit | C | 57.3 | 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/binance.json· historyhistory.json· badge/badges/binance.svg· changes feed/feeds/tools/binance.xml - Markdown
/tools/binance.md· slim/tools/binance.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/binance.md·/fixes/binance.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool binance --md(the CLI) · over MCPget_tool {"slug": "binance"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT binance.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs 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
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/binance"><img src="https://www.anchorterminal.com/badges/binance.svg" alt="Binance API on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/binance)<a href="https://www.anchorterminal.com/tools/binance">Binance API on Anchor Terminal</a>It counts on a page on binance.com or one of its subdomains, or the README at the root of github.com/binance/binance-spot-api-docs.
-
Tell us where it is
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": "binance", "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.
Share this listing
For the vendorGet sharing assets for social media. Two images say Binance API is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/binance. The logo is the one on this listing. If it's wrong or out of date, send us the right one.