tekore

Spotify Web API client for Python 3

Runs with mockssource: GitHubhomepagePythonMITcommit 2438a90a5fb2

Python, MIT licensed. The project labels itself: api client, python and spotify.

tekore runs, with stand-ins for the services it depends on. An Argusic agent installed it in 11 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Tekore 6.2.0 installed editable in the container venv; its offline pytest suite passes (252 passed, 174 skipped) and sync+async client/token/album/search/player flows were verified end-to-end against a schema-correct local mock of the Spotify Web API.

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

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.17 (measured)
recorded runs
1
last tested
stars
214
forks
18
open issues
6
watchers
6
size
2 MB
created
last push

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.

Time lost to each failure while testing tekore, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • mock server reaped between tool calls (connection refused)3 minutes
  • mock rejected Basic auth: 400 invalid_client1 minute
  • mock returned incomplete FullAlbum schema (6 pydantic validation errors)1 minute
  • UnknownModelAttributeWarning on album tracks (SimpleTrack rejects album/external_ids/popularity)1 minute
  • 404 for playback_currently_playing (path /v1/me/player/currently-playing)1 minute
  • ConversionError: playback_start_tracks rejected 'spotify:track:t1'1 minute
Install time
11 minutes
Cold machine to finish
14 minutes
Errors hit and fixed
7 hit, 7 fixed with no human help
How the result was proved
cd /work/repo && /tmp/venv/bin/python -m pytest -p no:cacheprovider -q returned '252 passed, 174 skipped in 1.48s', exit 0; plus E2E against local mock printed version 6.2.0, album/top-tracks/search/player/play-async results and E2E_OK
Model tokens used
781,152
Exact commit tested
2438a90a5fb2
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.

**Errors hit (mine, all fixed)**
- Mock server reaped between tool calls → combined mock+E2E into one invocation.
- `BadRequest 400 invalid_client` → mock's Basic-auth check was too strict; made it accept `mock_id…
- Mock base64 was for the wrong credentials → corrected.
- Broken mock file from overzealous edit → rewrote cleanly.
- `FullAlbum` schema missing `copyrights`/`external_ids`/`genres`/`label`/`popularity`/`tracks` → a…
- `SimpleTrack` blocks unknown `album`/`external_ids`/`popularity` (via `UnknownModelAttributeWarni…
- `404` on `/v1/me/player/currently-playing` (tekore's `playback_currently_playing()` calls that pa…
- `ConversionError: Invalid id: 'spotify:track:t1'` → my script misused `playback_start_tracks`; fi…
- `TypeError` on `request_client_token(asynchronous=True)` → async tokens go through `Credentials(.…
**Final state**
- Repo is untouched (only `/tmp` scaffolding outside it); tekore 6.2.0 installed editable in `/tmp/…

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

  • Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

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.
  • Took 11 minutes to install, slower than the median of the 39 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 40 api-client projects Argusic has installed and timed, tekore was the 30th fastest to reach a running state, and 25 of 40 reached one at all.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.17

Topics (from GitHub)

api-clientpythonspotify

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/tekore.svg)](https://argusic.com/subject/tekore)

Questions

Does tekore run?
tekore runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 11 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test tekore?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2438a90a5fb2. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test tekore?
The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does tekore take to install?
11 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 tekore need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing tekore?
7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does tekore compare with the alternatives?
Of the 40 api-client projects Argusic has installed and timed, tekore was the 30th fastest to reach a running state, and 25 of 40 reached one at all.
Where is the evidence for tekore?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion