24 Pull Requests vs Scrapfly

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms6781015
P95 · ms27854809
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs Scrapfly: common questions

Which is more reliable, 24 Pull Requests or Scrapfly?

On our scheduled checks, 24 Pull Requests leads on measured uptime — 24 Pull Requests at 100% versus Scrapfly at 99.02% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, 24 Pull Requests or Scrapfly?

24 Pull Requests has the lower median latency in our checks — 24 Pull Requests responds in 678 ms versus Scrapfly at 1015 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do 24 Pull Requests and Scrapfly need an API key?

24 Pull Requests needs no key, while Scrapfly requires a free API key. If you want to start calling without signup, reach for 24 Pull Requests first.

Can I call 24 Pull Requests and Scrapfly from the browser?

Neither sends browser-friendly CORS headers reliably, so call 24 Pull Requests and Scrapfly from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are 24 Pull Requests and Scrapfly free for commercial use?

24 Pull Requests has unclear commercial terms, and Scrapfly has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.