Crawl4AI Cloud Task Review: Collecting Company Data from Websites

Crawl4AI Cloud matched 314 of 343 expected details across 192 exact page URLs. Two small homepage trials ended without readable pages within 90 seconds, so homepage discovery has no cohort score.

192 exact page URLsVia treg

Results at a glance

Starting point Details found Runs with readable content Median time Time (P95) Confirmed API charge Charge per 100 details found
Exact page URL · Scrape 314/343 191/192 4.2 s 10.1 s $0.048 $0.01529
Company homepage Pilot only — — — — —
What we checked Exact page URL Company homepage
Homepage titles 74/82 —
Product-page titles 68/75 —
Prices with billing units 49/59 —
Customer quotes 123/127 —

We matched returned text against 343 expected details from 82 companies. A run counted as readable when the scorer found nonempty text on an eligible page. Navigation can qualify as readable text even when a page's main content is missing. The charge per 100 details uses confirmed charges divided by matches.

Test 1: Reading a page you already have

Result. On Momentic, the archived Markdown matched all seven expected prices in 3.4 seconds for $0.00025. On Tiptap, the response was readable and none of the six expected prices matched. It contained annual amounts such as $2,988. That case took 5.1 seconds for $0.00025. Momentic pricing · Tiptap pricing.

One of 29 misses came from a page that returned no readable text. The other 28 came from readable pages where the expected details did not match.

Setup. We sent one known page URL to crawl4ai.web.scrape through treg. We requested Markdown with the proxy disabled and set an 83-second endpoint timeout inside the 90-second test window. Crawl4AI Cloud reported archive responses for 12 of the 192 URLs, including Momentic. The responses omitted their final URLs, so we scored them under the requested URLs. The archived responses matched 22 of 22 checks. The other 180 inputs matched 292 of 321.

Test 2: Starting from the company homepage

Pilot. We tried Crawl from the Momentic and Dili homepages. The Momentic job was still pending at the 90-second cutoff. The Dili request timed out before it returned a job ID. Neither trial delivered readable pages within the test window, and we did not run the full 100-homepage test.

When to use Crawl4AI Cloud for this task

Use Scrape when you have a list of official URLs and per-page cost matters. Validate the amount and billing unit together on pricing pages where multiple plans or billing periods appear.

Data and scoring

The November 17 tests through treg reuse the frozen November 15 URLs and reference checks. A hit is a normalized text match on an eligible URL. The pricing checks require the amount and billing unit. The November 15 Firecrawl and Context.dev tests ran through AgentRouter. The timings and charges here describe the November 17 workflows through treg, including their cache settings, concurrency, and retry handling.

Individual runs and scorecard lists inputs, returned URLs, checks, timings, and fees. Filter for provider crawl4ai. Original comparison and methodology explains the shared dataset and scoring.