binance
Node.js & JavaScript SDK for Binance REST APIs & WebSockets, with TypeScript & browser support, integration tests, beautification & more.
Runssource: GitHubhomepageTypeScriptMITcommit 12bd77bf5e28
TypeScript, MIT licensed. The project labels itself: api, api client, api wrapper, binance, binance api, binance api node, binance exchange and binance node.
binance runs. An Argusic agent installed it in 0.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The SDK installs, builds via tsc with no errors, and 74 tests pass including all unit tests and public Binance API endpoint tests (getServerTime, getSystemStatus, getExchangeInfo, testConnectivity, market data) plus TLS certificate pinning verification against the live server
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- 9 test suites fail: require real Binance API credentials (HMAC/RSA/ED25519 keys) not available in this container2 minutes
- Install time
- under a minute
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npx jest --no-coverage reported 74 passed, 49 failed (all credential-dependent); public tests against real api.binance.com returned valid data: getServerTime returned number, getSystemStatus returned {msg:'normal',status:0}, getExchangeInfo returned full exchange metadata, testConnectivity returned {}
- Model tokens used
- 38,618
- Exact commit tested
- 12bd77bf5e28
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
echo "Ran tests: npx jest (74 passed, 49 failed - all failures are missing API credentials)" echo "Public API verified: serverTime, systemStatus, exchangeInfo, testConnectivity all return real… echo "TLS cert pinning verified: network.test.ts passes against real Binance server"' in /work/repo succeeded in 0ms: Install: npm install + npm run build Ran tests: npx jest (74 passed, 49 failed - all failures are missing API credentials) Public API verified: serverTime, systemStatus, exchangeInfo, testConnectivity all return real data … TLS cert pinning verified: network.test.ts passes against real Binance server Now I have all the information needed. tokens used 38,618 Now I have all the information needed.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.5 minutes, faster than the median of the 61 comparable projects Argusic has measured.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 62 api projects Argusic has installed and timed, binance was the 9th fastest to reach a running state, and 39 of 62 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.04 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.03 |
Topics (from GitHub)
apiapi-clientapi-wrapperbinancebinance-apibinance-api-nodebinance-exchangebinance-nodebinance-node-apibitcoincryptocurrencycryptocurrency-exchangesexchangejavascriptnodejsresttradingtypescriptwebsocket
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/binance)Questions
- Does binance run?
- Yes. binance runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test binance?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 12bd77bf5e28. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test binance?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does binance take to install?
- 0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does binance need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing binance?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does binance compare with the alternatives?
- Of the 62 api projects Argusic has installed and timed, binance was the 9th fastest to reach a running state, and 39 of 62 reached one at all.
- Where is the evidence for binance?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.