cyberapi
API tool based on tauri, it is smaller and faster.
Runssource: GitHubRustApache-2.0commit 5b959b8f33d8
Rust, Apache-2.0 licensed. The project labels itself: api, api client, rest api and tauri.
cyberapi runs. An Argusic agent installed it in 38 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 cyberapi desktop app builds, all 198 workspace tests pass, and a fresh launch on the virtual display stays up with a live 'Cyber API' 1280x800 window while creating a valid 10-table cyberapi.db, after a one-line src/lib.rs fix that creates the data directory on first launch.
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 100 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.
- first launch showed startup-error window and wrote no DB: data dir parent absent and turso does not create it14 minutes
- disk filled (40G) by two full build+test passes; sqlx bridge test build failed with No space left on device8 minutes
- yeslogic-fontconfig-sys build failed: no fontconfig dev headers/.pc to compile bindings6 minutes
- linker: unable to find -lxkbcommon, -lxkbcommon-x11, -lxcb (runtime .so.0s present, no dev symlinks, no root for apt)4 minutes
- cargo test: this_build::tests::the_desktop_reads_files panicked on missing Downloads/XDG user dirs in container3 minutes
- Install time
- 38 minutes
- Cold machine to finish
- 67 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- RUST_FONTCONFIG_DLOPEN=1 RUSTFLAGS="-L /tmp/liblinks" cargo test --all exited 0 with 198 passed 0 failed 2 ignored; timeout 20 ./target/debug/cyberapi with CYBERAPI_DATA_DIR=/tmp/final-run stayed alive, xwininfo showed window 0x200001 'Cyber API' 1280x800, and sqlite3 decode of the created cyberapi.db listed 10 tables (api_collections, api_folders, api_settings, cookies, cyberapi_meta, prefs, responses, top_orders, variables, versions)
- Model tokens used
- 1,931,689
- Exact commit tested
- 5b959b8f33d8
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Built the workspace and ran the full test suite; diagnosed and worked around missing system dev l… - Found and fixed a first-launch bug (data dir was never created); after the one-line fix a brand-n… **Errors hit and fixes** - `yeslogic-fontconfig-sys` build failed (no `fontconfig.pc`/headers): used that crate's built-in `… - Link failed on `-lxkbcommon`, `-lxkbcommon-x11`, `-lxcb` (runtime `.so.0` present, no dev symlink… - One test (`the_desktop_reads_files`) panicked on `x.json` because no `~/.config/user-dirs.dirs` (… - First launch showed a startup-error window and wrote no database because the parent data dir was … - Disk filled (40G) from two full build/test passes: cleaned with `cargo clean` and re-ran everythi… **Final verification** - `RUST_FONTCONFIG_DLOPEN=1 RUSTFLAGS="-L /tmp/liblinks" cargo test --all` → `passed=198 failed=0 i… - Fresh launch `timeout 20 ./target/debug/cyberapi` with `CYBERAPI_DATA_DIR=/tmp/final-run` → proce… - Bridge (`cyberapi-bridge --help` works; connecting to PostgreSQL requires a DB server not present…
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.
- Recovered from all 5 errors 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 38 minutes to install, slower than the median of the 46 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 47 api projects Argusic has installed and timed, cyberapi was the 47th fastest to reach a running state, and 30 of 47 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.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cyberapi)Questions
- Does cyberapi run?
- Yes. cyberapi runs. Argusic installed and launched it on a clean machine in 38 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test cyberapi?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5b959b8f33d8. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test cyberapi?
- The run that produced this verdict cost $0.52: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cyberapi take to install?
- 38 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 cyberapi need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cyberapi?
- 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 cyberapi compare with the alternatives?
- Of the 47 api projects Argusic has installed and timed, cyberapi was the 47th fastest to reach a running state, and 30 of 47 reached one at all.
- Where is the evidence for cyberapi?
- 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.