shipapis
StarSubmit an APISubmit API

Lookup.im API vs RSS2JSON

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

APILookup.im APIHEALTHY84RSS2JSONHEALTHY96
Uptime · 30d
Uptime · 90d99.02%96.1%
Uptime · 30d100%96.7%
P50 · ms1158178
P95 · ms35811882
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lookup.im API vs RSS2JSON: common questions

Which is more reliable, Lookup.im API or RSS2JSON?

On our scheduled checks, Lookup.im API leads on measured uptime — Lookup.im API at 99.02% versus RSS2JSON at 96.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, Lookup.im API or RSS2JSON?

RSS2JSON has the lower median latency in our checks — Lookup.im API responds in 1158 ms versus RSS2JSON at 178 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 Lookup.im API and RSS2JSON need an API key?

RSS2JSON needs no key, while Lookup.im API requires a free API key. If you want to start calling without signup, reach for RSS2JSON first.

Can I call Lookup.im API and RSS2JSON from the browser?

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

Are Lookup.im API and RSS2JSON free for commercial use?

Lookup.im API has unclear commercial terms, and RSS2JSON 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.