elevenlabs-js
The official JavaScript (Node) library for the ElevenLabs API.
Runs with mockssource: GitHubhomepageTypeScriptMITcommit b6deef08ed7c
TypeScript, MIT licensed. The project labels itself: artificial intelligence, conversational ai, javascript, node, text to speech and typescript.
elevenlabs-js runs, with stand-ins for the services it depends on. An Argusic agent installed it in 4 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The repository installs with npm, builds with tsc, and its full Jest suite (1094 tests, 179 suites) plus a 22-check SDK probe pass under Node 20 against a local schema-correct mock of the ElevenLabs API, with generated mp3 audio verified by ffmpeg decode and WebSocket realtime/speech-engine paths verified live.
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 92 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.
- 15 custom live-API tests in tests/custom/client.test.ts fail without an ElevenLabs API key45 minutes
- Initial mock's dummy mp3 bytes are not a decodable mp3; ffmpeg decode of generated audio failed8 minutes
- npm package entry index.js does not exist in the repo (produced only by prepack); probe originally imported ../../index.js and hit ERR_MODULE_NOT_FOUND6 minutes
- Node 18 lacks global File API (project requires Node 20+ per CONTRIBUTING), causing 3 fetcher unit tests to crash with 'File is not defined'5 minutes
- mpv is not installed in the container, so the stream() helper check could not exercise playback2 minutes
- Install time
- 4 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- ELEVENLABS_MOCK_BASE_URL=http://127.0.0.1:8790 npx -y node@20 ./node_modules/.bin/jest --config jest.config.mjs -> Test Suites: 179 passed, 179 total; Tests: 1094 passed, 1094 total. npx -y node@20 tests/custom/mock/probe.mjs -> SUMMARY: 22/22 checks passed, exit 0. curl -s -o /dev/null -w %{http_code} http://127.0.0.1:8790/v1/models (with xi-api-key header) returned 200.
- Model tokens used
- 1,566,824
- Exact commit tested
- b6deef08ed7c
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
M tests/custom/client.test.ts ?? tests/custom/mock/ tests/custom/client.test.ts | 40 +++++++++++++++++++++++++--------------- 1 file changed, 25 insertions(+), 15 deletions(-) ---files in mock--- mockServer.mjs probe.mjs real.mp3 All verification is complete. Final state: `npm install` succeeded, `npm run build` succeeded, and … tokens used 1,566,824 All verification is complete. Final state: `npm install` succeeded, `npm run build` succeeded, and …
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
- Installed in 4 minutes, faster than the median of the 5 comparable projects Argusic has measured.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Of the 6 artificial-intelligence projects Argusic has installed and timed, elevenlabs-js was the 3rd fastest to reach a running state, and 4 of 6 reached one at all.
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.32 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.79 |
Topics (from GitHub)
artificial-intelligenceconversational-aijavascriptnodetext-to-speechtypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/elevenlabs-js)Questions
- Does elevenlabs-js run?
- elevenlabs-js runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 4 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test elevenlabs-js?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b6deef08ed7c. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test elevenlabs-js?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does elevenlabs-js take to install?
- 4 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 elevenlabs-js need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing elevenlabs-js?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does elevenlabs-js compare with the alternatives?
- Of the 6 artificial-intelligence projects Argusic has installed and timed, elevenlabs-js was the 3rd fastest to reach a running state, and 4 of 6 reached one at all.
- Where is the evidence for elevenlabs-js?
- 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.