deepseek-php-client
⚡️ A community driven PHP client for DeepSeek AI, designed to bring clean API access, fluent developer experience, and framework-friendly integration to PHP applications.
Runs with mockssource: GitHubPHPMITcommit b02cafe3b413
PHP, MIT licensed. The project labels itself: ai, api client, deepseek, deepseek api, deepseek chat, deepseek coder, deepseek integration and deepseek learning.
deepseek-php-client runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The library installs with composer install, passes its full dev gate (Pest 15 passed, PHPStan no errors, 100% type coverage), and its Guzzle and Symfony clients each returned 200/401 chat responses, 200 models list, and 200 stream responses against a local schema-correct mock DeepSeek 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
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.
- php and composer missing in container (no root)5 minutes
- Symfony client sent empty Authorization bearer token; mock's initial lenient auth check returned 200 instead of 4013 minutes
- e2e run failed with cURL error 7 connection refused because the backgrounded mock server had died when its exec session ended2 minutes
- composer test appeared to fail with '/bin/sh: 1: Bad substitution'1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- composer install exited 0; ./vendor/bin/pest exited 0 with 'Tests: 15 passed (56 assertions)'; composer test exited 0; composer test:types exited 0 with '[OK] No errors'; php /tmp/e2e_verify.php (real client vs mock at 127.0.0.1:8321) exited 0 printing chat status=200, invalid-key status=401, models status=200 ids=deepseek-v4-pro,deepseek-v4-flash, stream status=200 for both guzzle and symfony
- Model tokens used
- 154,519
- Exact commit tested
- b02cafe3b413
- 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.
- Container had no `php` or `composer` and no root. As a brand-new user, I downloaded the static PH… - Ran the project's test suite: `./vendor/bin/pest` → `Tests: 15 passed (56 assertions)`. - Ran the full dev gate `composer test` (pint lint, PHPStan, 100% type-coverage, Pest) → exit 0; PH… - Since tests only use Mockery mocks and live API keys aren't available, I stood up a schema-correc… - Error encountered: running the e2e script while the background mock process had been killed betwe… **Result** exec /bin/sh -lc "cat <<'EOF' EOF" in /work/repo succeeded in 0ms: tokens used 154,519
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 4 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 12 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 237 ai projects Argusic has installed and timed, deepseek-php-client was the 180th fastest to reach a running state, and 168 of 237 reached one at all.
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 | 1/3 | Runs with mocks | 92.00 | 0.02 |
Topics (from GitHub)
aiapi-clientdeepseekdeepseek-apideepseek-chatdeepseek-coderdeepseek-integrationdeepseek-learningdeepseek-php-clientdeepseek-php-librarydeepseek-r1deepseek-sdkdeepseek-symfonydeepseek-v3deepseek-v4-flashnlpphp-deepseekphp-openai-alternativetext-generation
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/deepseek-php-client)Questions
- Does deepseek-php-client run?
- deepseek-php-client runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test deepseek-php-client?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b02cafe3b413. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test deepseek-php-client?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does deepseek-php-client take to install?
- 12 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 deepseek-php-client need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing deepseek-php-client?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does deepseek-php-client compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, deepseek-php-client was the 180th fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for deepseek-php-client?
- 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.