shipapis
StarSubmit an APISubmit API

Free Jobs API vs IPGEO

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

APIFree Jobs APIHEALTHY86IPGEOHEALTHY76
Uptime · 30d
Uptime · 90d98.0%99.02%
Uptime · 30d98.3%98.3%
P50 · ms833266
P95 · ms47632083
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Free Jobs API vs IPGEO: common questions

Which is more reliable, Free Jobs API or IPGEO?

On our scheduled checks, IPGEO leads on measured uptime — Free Jobs API at 98.0% versus IPGEO 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, Free Jobs API or IPGEO?

IPGEO has the lower median latency in our checks — Free Jobs API responds in 833 ms versus IPGEO at 266 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 Free Jobs API and IPGEO need an API key?

Neither needs a paid key — Free Jobs API is callable with no signup, and IPGEO is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Free Jobs API and IPGEO from the browser?

Only IPGEO is browser-friendly — it returns CORS headers over HTTPS. Free Jobs API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Free Jobs API and IPGEO free for commercial use?

Free Jobs API has unclear commercial terms, and IPGEO 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.