shipapis
StarSubmit an APISubmit API

24 Pull Requests vs Audexum

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

API24 Pull RequestsHEALTHY90AudexumHEALTHY93
Uptime · 30d
Uptime · 90d100%97.1%
Uptime · 30d100%95.0%
P50 · ms678417
P95 · ms27851103
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs Audexum: common questions

Which is more reliable, 24 Pull Requests or Audexum?

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

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

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

Only Audexum is browser-friendly — it returns CORS headers over HTTPS. 24 Pull Requests needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are 24 Pull Requests and Audexum free for commercial use?

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