piazza-api
Unofficial Client for Piazza's Internal API
Runs with mockssource: GitHubhomepagePythonMITcommit 39681fe60324
Python, MIT licensed. The project labels itself: api client, piazza, piazza api and python.
piazza-api runs, with stand-ins for the services it depends on. An Argusic agent installed it in 25 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
After installing in a fresh venv, the unmodified piazza-api 0.16.0 client imports and, pointed at the local mock via a requests session redirect, completes login and all verified API calls end to end, with the mock log showing only 200/302 responses and zero errors.
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.
- No tests or CLI in repo; the only way to exercise is via the library calls20 minutes
- Mock HTTP keep-alive acted unstably through the container proxy3 minutes
- Piazza() without login raises AttributeError instead of NotAuthenticatedError (library quirk)
- Install time
- 25 minutes
- Cold machine to finish
- 26 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- .venv/bin/python .argus/verify.py exited 0 with ALL_OK (22 checks: version, nonce, login cookie, user_profile, user_status, classes, network, get_post, get_feed, iter_all_posts, create_post, get_all_users, get_users, add/remove, filtered feed, search, stats, demo_login, raw content_get)
- Model tokens used
- 3,035,596
- Exact commit tested
- 39681fe60324
- 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.
104 .argus/verify.py 143 .argus/mock_piazza.py 247 total elapsed check: started ~17:05, now 17:30 Everything is verified. Final state confirmed; the error-fix log is below. exec /bin/sh -lc 'cd /work/repo && (setsid .venv/bin/python .argus/mock_piazza.py > .argus/mock.log 2>&1… succeeded in 1040ms: exit 0 ALL_OK tokens used 3,035,596
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 3 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 25 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, piazza-api was the 37th fastest to reach a running state, and 25 of 40 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.62 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/piazza-api)Questions
- Does piazza-api run?
- piazza-api runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 25 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test piazza-api?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 39681fe60324. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test piazza-api?
- The run that produced this verdict cost $0.62: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does piazza-api take to install?
- 25 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 piazza-api need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing piazza-api?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does piazza-api compare with the alternatives?
- Of the 40 api-client projects Argusic has installed and timed, piazza-api was the 37th fastest to reach a running state, and 25 of 40 reached one at all.
- Where is the evidence for piazza-api?
- 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.