shipapis
StarSubmit an APISubmit API

httpSMS vs Rendex

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

APIhttpSMSDEAD0RendexDEAD0
Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

httpSMS vs Rendex: common questions

Which is more reliable, httpSMS or Rendex?

Both are neck-and-neck — httpSMS and Rendex each measure 0.0% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Do httpSMS and Rendex need an API key?

Both ask you to authenticate — httpSMS uses an API key and Rendex uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call httpSMS and Rendex from the browser?

Yes — both httpSMS and Rendex 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 httpSMS and Rendex free for commercial use?

httpSMS has unclear commercial terms, and Rendex 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.