Results at a glance
| Starting point | Details found | Readable exact pages | Median time | Time (P95) | API charge | API charge per 100 details found |
|---|---|---|---|---|---|---|
| Exact page URL · Jina Reader | 326/343 (95.0%) | 190/192 | 2.95 s | 8.04 s | $0.00 | $0.00 |
| Company homepage | Not measured | — | — | — | — | — |
| What we checked | Exact URL |
|---|---|
| Homepage titles | 76/82 |
| Product-page titles | 73/75 |
| Prices with billing units | 56/59 |
| Customer quotes | 121/127 |
The references were frozen on November 15. We repeated their 192 specified URLs and looked for the same 343 details in the returned Markdown. A price requires both the amount and billing unit.
Test 1: Reading a page you already have
Result. Of the 17 missed checks, 15 were on readable target pages whose Markdown lacked the reference text. The other 2 misses came from final URLs that differed from the supplied pages. All three price misses were on Tiptap. The Markdown included $49, $149 and $999 per month. The three other reference amounts, $59, $179 and $1,199 per month, were absent.
Setup. We sent one URL per request to Reader’s public endpoint without an API key and requested Markdown in a JSON response. We used the default engine and cache settings. We applied the original exact-URL matching rule to Reader’s reported final URL and scored the Markdown body. Metadata fields such as the title were outside the body score. Each request had a 90-second observation window.
| Exact page | Details found | End-to-end time | What Reader returned |
|---|---|---|---|
| Roboflow pricing | 9/9 | 0.69 s | The Markdown kept the monthly plan and the eight per-credit rates, including $3.90 and $3.56 per credit. |
| Merlin AI homepage | 0/1 | 3.64 s | The response’s metadata title matched the expected title. The first headline in the Markdown was “Deliver real estate in real time.” The body omitted the metadata title. |
| Blissway homepage | 0/1 | 1.62 s | Reader returned HTTP 200 and reported an SVG as the final URL. The result did not qualify as a read of the supplied homepage. |
Cloud Humans likewise returned a different final URL, routing the homepage request to /en/. Check the final URL before you attach the Markdown to a company record. Check the title in metadata when your schema allows that field. For a pricing table, verify both the amount and billing unit before treating the result as a plan rate. Individual runs
Test 2: Starting from the company homepage
Coverage. This review measured the known-URL Reader endpoint. For homepage discovery, one candidate workflow would select links from the homepage and use Reader to fetch them. Reader offers a link summary for a supplied page. Reader options
When to use Jina Reader for this task
Use Reader when the relevant URLs are already known and Markdown is the input your workflow needs. Check that the response came from the expected page, then validate the fields you plan to store. Budget for throughput separately from per-request latency. We paced the public endpoint below its published limit of 20 requests per minute, so this batch took about 10.1 minutes. Per-request times exclude the wait to dispatch the next request. Jina’s public rate limits
Data and scoring
All 192 exact-URL runs · Original comparison and scoring method. The zero API charge applies to this batch on the public route. Content and latency reflect Reader’s configuration and the pages returned on November 17.