shipapis
StarSubmit an APISubmit API

Cartes.io vs Check e-mail or username for a data breach

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

APICartes.ioNEW—Check e-mail or username for a data breachNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source project; user-generated maps)Unverified
Free tierFree, no API key for public readFree — limits not published
Rate limit60 req/window · 59 remainingUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cartes.io vs Check e-mail or username for a data breach: common questions

Which is more reliable, Cartes.io or Check e-mail or username for a data breach?

On our scheduled checks, Check e-mail or username for a data breach leads on measured uptime — Cartes.io at —% versus Check e-mail or username for a data breach 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 Cartes.io and Check e-mail or username for a data breach need an API key?

Neither needs a paid key — Cartes.io is callable with no signup, and Check e-mail or username for a data breach is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Cartes.io and Check e-mail or username for a data breach from the browser?

Only Cartes.io is browser-friendly — it returns CORS headers over HTTPS. Check e-mail or username for a data breach needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Cartes.io and Check e-mail or username for a data breach free for commercial use?

Cartes.io has unclear commercial terms, and Check e-mail or username for a data breach 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.