shipapis
StarSubmit an APISubmit API

Genderize.io vs IFTTT

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

APIGenderize.ioNEW—IFTTTNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierKeyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free keyFree — limits not published
Rate limitKeyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headersUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Genderize.io vs IFTTT: common questions

Which is more reliable, Genderize.io or IFTTT?

On our scheduled checks, IFTTT leads on measured uptime — Genderize.io at —% versus IFTTT 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 Genderize.io and IFTTT need an API key?

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

Can I call Genderize.io and IFTTT from the browser?

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

Are Genderize.io and IFTTT free for commercial use?

Genderize.io has unclear commercial terms, and IFTTT 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.