shipapis
StarSubmit an APISubmit API

Cutt.ly vs IPinfo

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

APICutt.lyNEW—IPinfoNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredKeyless /json works with limits; free token recommended (IPinfo Lite offers higher/unlimited access with a token)
Rate limitUnpublishedKeyless/unauthenticated access is rate-limited; numeric caps not stated on the developers page
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cutt.ly vs IPinfo: common questions

Which is more reliable, Cutt.ly or IPinfo?

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

Do Cutt.ly and IPinfo need an API key?

IPinfo needs no key, while Cutt.ly requires a free API key. If you want to start calling without signup, reach for IPinfo first.

Can I call Cutt.ly and IPinfo from the browser?

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

Are Cutt.ly and IPinfo free for commercial use?

Cutt.ly has unclear commercial terms, and IPinfo 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.