shipapis
StarSubmit an APISubmit API

Bacon Ipsum vs Genderize.io

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

APIBacon IpsumNEW—Genderize.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key requiredKeyless usage limited (x-rate-limit-limit: 25 observed); 2,500 names/mo with a free key
Rate limitUnpublishedKeyless cap 25 per x-rate-limit-limit header; remaining/reset exposed in response headers
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bacon Ipsum vs Genderize.io: common questions

Which is more reliable, Bacon Ipsum or Genderize.io?

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

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

Can I call Bacon Ipsum and Genderize.io from the browser?

Yes — both Bacon Ipsum and Genderize.io 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 Bacon Ipsum and Genderize.io free for commercial use?

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