JoyCode2Api

JoyCode API 代理, 协议翻译成 Anthropic/OpenAI 兼容格式,让 Claude Code 直接调用 JoyCode支持的模型,比如GLM 5.1等

Runs with mockssource: GitHubGoApache-2.0commit 176ca9d4d7f9

Go, Apache-2.0 licensed. The project labels itself: anthropic api, api gateway, claude code, fastapi, llm, openai api, proxy and python.

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

Binary builds, server starts, health endpoint returns 200, Dashboard serves HTML, and all 11 Go test packages pass

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.13 (measured)
recorded runs
1
last tested
stars
218
forks
48
open issues
10
watchers
2
size
5 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 JoyCode2Api, 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.

  • TestOpenAPIEndpoints/v1_models returned 500 (no upstream mock)4 minutes
  • Go 1.25+ not found in container2 minutes
Install time
8 minutes
Cold machine to finish
17 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
go test ./... exited 0, 11 packages passed; curl http://127.0.0.1:34891/health returned HTTP 200 with JSON; curl http://127.0.0.1:34891/ returned HTTP 200 with Dashboard HTML; ./JoyCode2Api version printed 'JoyCode Proxy 0.6.1'
Model tokens used
680,254
Exact commit tested
176ca9d4d7f9
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.

4. **Test fix**: `TestOpenAPIEndpoints/v1_models` was failing (500) because the subprocess server t…
5. **Full test suite**: all 11 Go packages pass.
tokens used
680,254
All tests pass. The server binary builds and runs. Let me compile the final report.
Here's the summary:
**What was done:**
1. **Go install**: Go was not in the container. Installed Go 1.27.3 from tarball. Set `GOROOT`, `GO…
2. **Build**: `CGO_ENABLED=0 go build -o JoyCode2Api ./cmd/JoyCode2Api/` succeeded on first try. No…
3. **Server launch**: `serve --skip-validation --tls=false` starts on port 34891, Dashboard serves …
4. **Test fix**: `TestOpenAPIEndpoints/v1_models` was failing (500) because the subprocess server t…
5. **Full test suite**: all 11 Go packages pass.

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 8 minutes.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, 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.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.13

Topics (from GitHub)

anthropic-apiapi-gatewayclaude-codefastapillmopenai-apiproxypythonsse

Embed the badge

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

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

Questions

Does JoyCode2Api run?
JoyCode2Api runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test JoyCode2Api?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 176ca9d4d7f9. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test JoyCode2Api?
The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does JoyCode2Api take to install?
8 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 JoyCode2Api need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing JoyCode2Api?
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 JoyCode2Api?
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