Is Binance Agent Skills open source?

No. Binance Agent Skills is closed source as of 2026-10-24.

Which chains does Binance Agent Skills support?

Binance Agent Skills lists support for BNB Chain as of 2026-10-24.

Is Binance Agent Skills still maintained?

Sato Hub tracks no commit or release for Binance Agent Skills; it cannot say whether it is maintained.

How do I install or run Binance Agent Skills?

Sato Hub has no deploy spec for Binance Agent Skills; follow the project's own documentation.

Is Binance Agent Skills verified on Sato Hub?

No independent verification is on record for Binance Agent Skills; its verification status is "Self-Reported" and its Sato Score is 31 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.

Trading Tool

Binance Agent Skills

Name: Binance Agent Skills
Author: Binance

A set of MCP-style Agent Skills that let AI agents access Binance spot, derivatives, margin, Alpha market data, and asset management via standardized APIs.

Sato Score31
ChainsBNB Chain

ActiveSelf-Reported

Binance Agent Skills is a closed-source trading tool by Binance on BNB Chain, with no code activity tracked. Sato Score 31/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-24. How the score works →

Check what an install would ask of your keys, before you run it →

No code activity tracked

Listed from binance.com on 2026-06-08. Install: not attempted — no install path on record. Evidence →

Website ↗X / Twitter ↗

Next step

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp

Ask Sato Hub what is on record about Binance Agent Skills before I use it.

Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Binance rolled out a suite of AI Agent Skills (reported as roughly 13-20 modules across announcements in March-April 2026) covering spot trading, USD-margined derivatives, cross/isolated margin, Binance Alpha market data, asset management, and onchain pay. Additional skills target onchain analysis (address/token info, market rank, trading signals, token audit). These are centralized-exchange capabilities exposed to agents through a standardized API rather than a standalone onchain agent.

Sato Score

31/100· Low

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness: 20/35
Code transparency: 0/20
Interface verifiability: 0/10
Docs & demo: 0/10
Listing transparency & provenance: 8/15
Independent verification: 3/10

View verification & embed badge →History →How the Sato Score works

Evidence — listed vs checked · what the words mean

Listed from binance.com on 2026-06-08. Install: not attempted — no install path on record.

Claim	Value	Evidence	Source	Checked
Chains supported	BNB Chain	self-reported	binance.com	as of 2026-10-24
Verification status	Self-Reported — not independently reviewed	self-reported	binance.com	as of 2026-10-24
Website answers	answered (HTTP 202)	observed	binance.com	2026-10-24
Daily check record	90 of 90 daily checks since 2026-07-26 succeededa success rate of our checks, not uptime; the source is this listing's own history	observed	—	2026-10-23
Built by	Binanceconfidence 0.95	self-reported	binance.com	as of 2026-07-01
Creator profile	https://www.binance.comconfidence 0.90	self-reported	binance.com	as of 2026-07-01
Sato Score	31/100 (Low)how open, active and verifiable — not a safety or quality grade	computed	satohub.ai	2026-10-24

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Observed record — 91 daily checks since 2026-07-26

100%of 91 checks since 2026-07-26 succeeded

Currently responding for 91 days

Succeeded: 91
Failed: 0
Their error: 0
Unattributed: 0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 37 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-24, one point per UTC day

Share of OUR checks that succeeded

100%

7-day rolling; unattributable days are gaps · 30/30 days

Tools listed

fewer than 2 points—

from the server's own tools/list · 0/30 days

Sato Score

as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.