Fruityvice vs Makeup

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms951791
P95 · ms39962529
Authnonenone
CORSnoyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fruityvice vs Makeup: common questions

Which is more reliable, Fruityvice or Makeup?

On our scheduled checks, Fruityvice leads on measured uptime — Fruityvice at 100% versus Makeup 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, Fruityvice or Makeup?

Makeup has the lower median latency in our checks — Fruityvice responds in 951 ms versus Makeup at 791 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 Fruityvice and Makeup need an API key?

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

Can I call Fruityvice and Makeup from the browser?

Neither sends browser-friendly CORS headers reliably, so call Fruityvice and Makeup from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Fruityvice and Makeup free for commercial use?

Fruityvice has unclear commercial terms, and Makeup 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.