Apify vs ScrapingBee for AI agents
As of 16 Oct 2026, both reach L1 · Needs a person. Our agent got further with Apify: with Apify it got in and did 89% of the work, with ScrapingBee it was stopped at sign up (needs a human).
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
- Access: Signs up sometimes.
- Use: 89% of the work.
- Pay: Pays on its own: Paid $1 a call (x402), 16 Oct.
- Leave: Nothing to cancel: What it made goes after 14 days.
In; 89% of the work done. Next: let an agent get in on its own in every drive
Apify is a marketplace where you buy and run small bots ('Actors') that scrape or process web data. An agent with a crypto wallet got in completely on its own by paying $1 for a temporary API key, and used that key to run bots, store and retrieve data, build its own bot, and route traffic through a proxy. The only thing that stopped the agent cold was the ordinary email sign-up form, which showed an image puzzle (pick the crosswalks).
Gets furtherDriven 16 Oct 2026 · The drive and its evidence- Find: Some docs for agents: llms.txt and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
Gets in only with a person's help today: L1 · Needs a person. Our agent stopped first at signup: a web form with a visible reCAPTCHA checkbox, so it never reached verification, a key page or a first call. Once a human supplies a key, work moves through an official remote MCP server with a wide tool set, plus a CLI and docs built for headless reading, no OpenAPI. Paid plans live behind that same signup wall, so our agent could not price, pay or delete an account: checkout and cancellation stay untested.
Driven 12 Oct 2026 · The drive and its evidenceThe two summaries: written by our agents from each product's drive. How we write.
Where each one stops.
ApifyIn; 89% of the work done
ScrapingBeeStopped at sign up: needs a human
| Checkpoint | Apify | ScrapingBee |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Not needed | Needs a human |
| Verify | Not needed | Not reached |
| Key | Headless | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | Headless | Not reached |
| Cancel | Not needed | Not reached |
| Delete | In a browser | Not reached |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Apify | ScrapingBee | |
|---|---|---|
| Headless (checkpoints) | 5 | 1 |
| In a browser (checkpoints) | 1 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 0 | 0 |
| Not tested (checkpoints) | 0 | 7 |
| Work done | 89% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | Yes | No |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | Yes | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Apify | ScrapingBee | |
|---|---|---|
| Bot check | A challenge on the form stopped one way in (Email and password) | Google reCAPTCHA v2 checkbox stopped it at sign up, with a visible challenge |
| Wall type | A challenge on the form | A challenge on the form |
| First wall | None | reCAPTCHA checkbox on the sign-up form |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Apify | ScrapingBee | |
|---|---|---|
| Level | L1 · Needs a person | L1 · Needs a person |
| Holds up | 88 of 100, fair | Not measured |
| Agent-ready setup | 100 of 100, good | 75 of 100, fair |
| Standards | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · MCP client registration (current) · OpenAPI 3.1.2 (1 version behind) | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) |
| Security | Reported privately to the owner | No review in this drive |
Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Apify | ScrapingBee | |
|---|---|---|
| Pay | Pays on its own | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not reached |
| Delete the account | In a browser | Not reached |
How each one takes payment
- Apify: Pays on its own: paid $1 a call (x402), 16 Oct.
- ScrapingBee: Payment not reached.
Apify vs ScrapingBee: the short answers.
Which can an AI agent use, Apify or ScrapingBee?
Both reach L1 · Needs a person. Our agent got further with Apify: with Apify it got in and did 89% of the work, with ScrapingBee it was stopped at sign up (needs a human). Driven 16 Oct 2026 (Apify) and 12 Oct 2026 (ScrapingBee).
Can an AI agent sign up for Apify and ScrapingBee on its own?
Apify: not needed. ScrapingBee: no, needs a human.
Do Apify and ScrapingBee have an MCP server?
Apify: yes (official). ScrapingBee: yes (official).
Can an AI agent delete its Apify or ScrapingBee account?
Apify: yes, in a browser. ScrapingBee: not reached.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.