scrapyrt
HTTP API for Scrapy spiders
Runssource: GitHubPythonBSD-3-Clausecommit 6d00a0ad55c3
Python, BSD-3-Clause licensed. The project labels itself: crawler, crawling, hacktoberfest, hacktoberfest2021, python, scraper, scrapy and twisted.
scrapyrt runs. An Argusic agent installed it in 23 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
ScrapyRT 0.18.1 installed in a venv, all 126 unit and integration tests pass, the HTTP server starts and responds to GET and POST crawl.json endpoints with real Scrapy spider output.
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.
- FileNotFoundError: 'flask' not found for mock test server subprocess3 minutes
- ModuleNotFoundError: No module named 'port_for'1 minute
- AssertionError: req.url 'http://localhost/' != 'http://localhost' in test_crawl_manager.py1 minute
- Install time
- 23 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest tests/ exited 0, 126 passed; scrapyrt server started on port 19097, GET crawl.json?spider_name=test&url=... returned 200 with status=ok and 1 item, POST to crawl.json returned 200 with 1 item
- Model tokens used
- 87,180
- Exact commit tested
- 6d00a0ad55c3
- 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.
Scrapyrt ready on attempt 0
Crawl status: 200
Status: ok
Items: 1
First item: {'name': ['Page 1']}
POST status: 200
POST items: 1
POST first item: {'name': ['Page 2']}
Everything is verified.
tokens used
87,180
Everything is verified.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 3 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 BSD-3-Clause, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 23 minutes to install, slower than the median of the 25 comparable projects Argusic has measured.
Of the 26 crawler projects Argusic has installed and timed, scrapyrt was the 22nd fastest to reach a running state, and 22 of 26 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)
crawlercrawlinghacktoberfesthacktoberfest2021pythonscraperscrapytwistedwebcrawlerwebcrawling
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/scrapyrt)Questions
- Does scrapyrt run?
- Yes. scrapyrt runs. Argusic installed and launched it on a clean machine in 23 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test scrapyrt?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6d00a0ad55c3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test scrapyrt?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does scrapyrt take to install?
- 23 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 scrapyrt need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing scrapyrt?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does scrapyrt compare with the alternatives?
- Of the 26 crawler projects Argusic has installed and timed, scrapyrt was the 22nd fastest to reach a running state, and 22 of 26 reached one at all.
- Where is the evidence for scrapyrt?
- 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.