DocForge vs Nationalize.io

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

Uptime · 30d
Uptime · 90d100%97.1%
Uptime · 30d100%100%
P50 · ms1583448
P95 · ms2485985
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedKeyless 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

DocForge vs Nationalize.io: common questions

Which is more reliable, DocForge or Nationalize.io?

On our scheduled checks, DocForge leads on measured uptime — DocForge at 100% versus Nationalize.io at 97.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, DocForge or Nationalize.io?

Nationalize.io has the lower median latency in our checks — DocForge responds in 1583 ms versus Nationalize.io at 448 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 DocForge and Nationalize.io need an API key?

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

Can I call DocForge and Nationalize.io from the browser?

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

Are DocForge and Nationalize.io free for commercial use?

DocForge has unclear commercial terms, and Nationalize.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.