shipapis
StarSubmit an APISubmit API

Affirmations.dev vs Agify

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

APIAffirmations.devHEALTHY92AgifyHEALTHY89
Uptime · 30d
Uptime · 90d100%93.1%
Uptime · 30d100%91.7%
P50 · ms590545
P95 · ms10811337
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedProprietary
Free tierFree — limits not published100 names/day, no signup
Rate limitUnpublished100/day per IP
In directory since2026-07-052026-05-02
operationalpartialdownno data

Affirmations.dev vs Agify: common questions

Which is more reliable, Affirmations.dev or Agify?

On our scheduled checks, Affirmations.dev leads on measured uptime — Affirmations.dev at 100% versus Agify at 93.1% 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, Affirmations.dev or Agify?

Agify has the lower median latency in our checks — Affirmations.dev responds in 590 ms versus Agify at 545 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 Affirmations.dev and Agify need an API key?

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

Can I call Affirmations.dev and Agify from the browser?

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

Are Affirmations.dev and Agify free for commercial use?

Affirmations.dev has unclear commercial terms, and Agify allows commercial use on its free tier. 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.