shipapis
StarSubmit an APISubmit API

24 Pull Requests vs VerifyEd

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

API24 Pull RequestsHEALTHY90VerifyEdHEALTHY76
Uptime · 30d
Uptime · 90d100%97.1%
Uptime · 30d100%95.0%
P50 · ms6781933
P95 · ms27853606
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublished100 req/window · 99 remaining · resets 1783522020
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs VerifyEd: common questions

Which is more reliable, 24 Pull Requests or VerifyEd?

On our scheduled checks, 24 Pull Requests leads on measured uptime — 24 Pull Requests at 100% versus VerifyEd at 97.1% 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 VerifyEd?

24 Pull Requests has the lower median latency in our checks — 24 Pull Requests responds in 678 ms versus VerifyEd at 1933 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 VerifyEd need an API key?

24 Pull Requests needs no key, while VerifyEd 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 VerifyEd from the browser?

Neither sends browser-friendly CORS headers reliably, so call 24 Pull Requests and VerifyEd 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 VerifyEd free for commercial use?

24 Pull Requests has unclear commercial terms, and VerifyEd 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.