solana-dex-cli

Agent-first CLI for trading on Solana, 18 DEX adapters, 12 SWQoS TX landing processors. Buy, sell, lp, snipe, create pool, launch coin, and stream real-time onchain events from your terminal.

Runssource: GitHubTypeScriptMITcommit 1851d27b71a2

TypeScript, MIT licensed. The project labels itself: algo trading, command line tool, decentralized exchange, developer tools, grpc, high frequency trading, meteora and orca.

solana-dex-cli runs. An Argusic agent installed it in 1.2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Project installed from source, built to dist/, all 47 tests (43 unit + 4 registry) pass, CLI responds with version 2.0.0-alpha.16 and lists all 18 DEX adapters with correct capabilities.

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 90 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
90 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
584
forks
193
open issues
17
watchers
8
size
34 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.

Install time
1 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
npm run test:unit exited 0, 43/43 passed; npm run test:registry exited 0, 4/4 passed; node dist/cli.js --version returned 2.0.0-alpha.16; node dist/cli.js list-dex showed all 18 adapters with correct capabilities
Model tokens used
24,315
Exact commit tested
1851d27b71a2
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.

- `npm run build` compiled TypeScript with zero errors
- Unit tests: 43 passed, 0 failed
- Registry tests: 4 passed, 0 failed
- CLI version and help commands respond correctly
tokens used
24,315
All tasks succeeded:
- `npm install` completed with 1000 packages (engine warnings for node v18 instead of v20, but inst…
- `npm run build` compiled TypeScript with zero errors
- Unit tests: 43 passed, 0 failed
- Registry tests: 4 passed, 0 failed
- CLI version and help commands respond correctly

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.
  • Installed in 1.2 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 1.2 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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 Runner2/3Runs100.000.02
Argusic Runner1/3Unverified80.000.01

Topics (from GitHub)

algo-tradingcommand-line-tooldecentralized-exchangedeveloper-toolsgrpchigh-frequency-tradingmeteoraorcaraydiumsolanatradingbot

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/solana-dex-cli.svg)](https://argusic.com/subject/solana-dex-cli)

Questions

Does solana-dex-cli run?
Yes. solana-dex-cli runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test solana-dex-cli?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1851d27b71a2. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test solana-dex-cli?
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 solana-dex-cli take to install?
1.2 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 solana-dex-cli need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing solana-dex-cli?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for solana-dex-cli?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion