Rejection Reason Generator vs Agify

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
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

Rejection Reason Generator vs Agify: common questions

Which is more reliable, Rejection Reason Generator or Agify?

Only Agify is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Rejection Reason Generator and Agify need an API key?

Neither needs a paid key — Rejection Reason Generator 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 Rejection Reason Generator and Agify from the browser?

Yes — both Rejection Reason Generator and Agify 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 Rejection Reason Generator and Agify free for commercial use?

Rejection Reason Generator 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.