TinyFish Task Review: Collecting Company Data from Websites

TinyFish Fetch matched 279 of 343 expected details from exact URLs. The recorded API charge for the batch was $0. It recovered 105 of 127 quotes. Pricing varied sharply: it found all nine expected rates on Firecrawl's pricing page and none of the six on Tiptap's.

192 exact page URLs

Results at a glance

Starting point Details found Runs with readable content Median time Time (P95) API charge API charge per 100 details found
Exact page URL 279/343 190/192 1.64 s 9.2 s $0 $0.00
Company homepage Not measured — — — — —
What we checked Exact URL Company homepage
Homepage titles 64/82 —
Product-page titles 64/75 —
Prices with billing units 46/59 —
Customer quotes 105/127 —

The checks cover 343 known details from 82 companies. A hit means the expected detail appeared in the returned text. The charge per 100 details uses each batch's total API charge and the number of matches. Scorecard

Test 1: Reading a page you already have

Result. TinyFish returned readable content for 190 of 192 URLs and matched all expected checks on 151 pages.

Setup. We gave TinyFish Fetch the official URLs and scored the expected details found in the returned text. AgentRouter recorded $0 for these calls in this run. That is the observed charge in this test, not a general pricing claim.

What four Fetch responses looked like

Input Result in the raw records Matched details Time
Firecrawl pricing The response included the $399 monthly rate and $333/month billed annually, along with the other expected rates. 9/9 prices 10.35 s
Tiptap pricing The response included a Plans & Pricing heading and plan-limit FAQs. The six expected monthly rates were missing. 0/6 prices 2.10 s
Warmly pricing The request timed out. 0/3 prices 31.13 s
Serif Health product page The request completed and included text from the redirected health-systems page. The scorer counted no readable result for the original URL. 0/1 product title 7.86 s

TinyFish had 64 missed checks overall. In 60 of those checks the reference page was counted as readable. A timeout tells you which request to retry. The Tiptap result shows why you also need a check for whether a readable response contains the required pricing fields. Runs page-060, page-110, page-133, and page-054

Homepage discovery

Coverage. TinyFish Fetch did not run in the 100-homepage cohort. This study does not show how a TinyFish workflow chooses product, pricing or customer pages from a domain, and it contains no TinyFish multi-step latency or cost measurement.

When to use TinyFish for this task

Use Fetch when you already have the URL and can validate the requested fields. Give a timeout a bounded retry. If a pricing page comes back readable without amounts or billing units, send the row to another verified source or mark the price unconfirmed. When evaluating bulk use, compare both latency and the share of fully usable pages. In this run the median was 1.64 seconds, yet only 151 of 192 pages matched every expected detail.

Data and scoring

Individual runs · Full comparison and methodology. The main retrieval tests ran through AgentRouter on November 15, 2026. Charges describe the observed calls. A text match and a verified citation are scored separately.

Related review

TinyFish API Review

Seven TinyFish features tested through APIs: official company-page lookup, sourced pricing tables, page extraction, browser workflows, research and scheduled monitoring. A dated API pilot with public inputs, results and scoring.