Archive.org vs Invokely

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

Uptime · 30d
Uptime · 90d98.3%100%
Uptime · 30d100%100%
P50 · ms630227
P95 · ms3068245
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (rights vary per item)
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-07-052026-10-12
operationalpartialdownno data

Archive.org vs Invokely: common questions

Which is more reliable, Archive.org or Invokely?

On our scheduled checks, Invokely leads on measured uptime — Archive.org at 98.3% versus Invokely at 100% 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, Archive.org or Invokely?

Invokely has the lower median latency in our checks — Archive.org responds in 630 ms versus Invokely at 227 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 Archive.org and Invokely need an API key?

Archive.org needs no key, while Invokely requires a free API key. If you want to start calling without signup, reach for Archive.org first.

Can I call Archive.org and Invokely from the browser?

Yes — both Archive.org and Invokely send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Archive.org and Invokely free for commercial use?

Archive.org has unclear commercial terms, and Invokely 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.