nba_api
An API Client package to access the APIs for NBA.com
Runs with mockssource: GitHubPythonMITcommit 52c0fb0b81c4
Python, MIT licensed. The project labels itself: analysis, api client, basketball stats, endpoint analysis, http client, jupyter notebooks, nba and nba api.
nba_api runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
nba_api 1.11.4 installs, all 522 unit tests pass, all 150 integration tests pass against VCR cassettes, static player and team data loads correctly, and all endpoint classes import successfully.
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.
- test_endpoint_uses_global_session fails when run after VCR integration tests in same pytest session (pre-existing test isolation bug)20 minutes
- VCR cassettes recorded with season 2025-26 fail to match when current date generates season 2026-27 (Nov 2026)15 minutes
- Install time
- under a minute
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- poetry run pytest tests/unit -v returned 522 passed 0 failed; poetry run pytest tests/integration -v returned 150 passed 17 skipped; poetry run python -c 'from nba_api.stats.static import players, teams; print(len(teams.get_teams()), len(players.get_players()))' returned '30 5205'
- Model tokens used
- 180,347
- Exact commit tested
- 52c0fb0b81c4
- 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.
Let me now compile the ARGUSIC_RESULT:
exec
/bin/sh -lc 'export PATH="$HOME/.local/bin:$PATH" && cd /work/repo && poetry run pytest tests/unit …
succeeded in 9711ms:
/work/repo/tests/integration/helpers/models.py:54: DeprecationWarning: ScoreboardV2 has known iss…
return self.endpoint_class(**{**resolved, **self.overrides})
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
================= 672 passed, 17 skipped, 6 warnings in 9.20s ==================
672 passed, 17 skipped. The only pre-existing issue is the `test_endpoint_uses_global_session` fail…
tokens used
180,347
672 passed, 17 skipped. The only pre-existing issue is the `test_endpoint_uses_global_session` fail…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 0.5 minutes.
- Recovered from all 2 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.
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.26 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.18 |
Topics (from GitHub)
analysisapi-clientbasketball-statsendpoint-analysishttp-clientjupyter-notebooksnbanba-apinba-statsnba-stats-apipythonpython3sports-statsstats
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/nba-api)Questions
- Does nba_api run?
- nba_api runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test nba_api?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 52c0fb0b81c4. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test nba_api?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does nba_api 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 nba_api need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing nba_api?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for nba_api?
- 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.