peddler

Amazon Selling Partner API (SP-API) in Ruby

Runs with mockssource: GitHubhomepageRubyMITcommit 8fe69f6c3227

Ruby, MIT licensed. The project labels itself: amazon, ecommerce, ruby, selling partner api and sp api.

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

Ruby 3.3.6 is installed at /home/runner/.local/bin/ruby, all 77 gem dependencies installed via bundle, and the full test suite passes cleanly: 460 runs, 874 assertions, 0 failures, 0 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

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
318
forks
130
open issues
1
watchers
26
size
16 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 peddler, 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.

  • Ruby not found in container4 minutes
  • zlib extension not compiled into Ruby (needed by rubygems)1 minute
  • psych (YAML) extension not compiled into Ruby (needed by rubygems)1 minute
  • Generator tests failed: missing selling-partner-api-models checkout1 minute
Install time
7 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
bundle exec rake test returned '460 runs, 874 assertions, 0 failures, 0 errors, 0 skips' and exit code 0
Model tokens used
218,654
Exact commit tested
8fe69f6c3227
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.

- **Ruby not installed** — installed Ruby 3.3.6 from source (no package manager root access)
- **zlib extension missing** — built zlib library from source and compiled the Ruby extension
- **psych (YAML) extension missing** — built libyaml from source and compiled the psych extension
- **Generator tests failing over missing SP-API models** — cloned `selling-partner-api-models` at t…
tokens used
218,654
All systems working. Let me compile the final report.
**Errors encountered and fixed:**
- **Ruby not installed** — installed Ruby 3.3.6 from source (no package manager root access)
- **zlib extension missing** — built zlib library from source and compiled the Ruby extension
- **psych (YAML) extension missing** — built libyaml from source and compiled the psych extension
- **Generator tests failing over missing SP-API models** — cloned `selling-partner-api-models` at t…

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 7 minutes.
  • 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.
  • 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.03

Topics (from GitHub)

amazonecommercerubyselling-partner-apisp-api

Embed the badge

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

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

Questions

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