Data.gov vs Neotimo DGFiP Mirror
Same instrument, two spec sheets — measured, not claimed.
Data.gov vs Neotimo DGFiP Mirror: common questions
Which is more reliable, Data.gov or Neotimo DGFiP Mirror?
Both are neck-and-neck — Data.gov and Neotimo DGFiP Mirror each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.
Which is faster, Data.gov or Neotimo DGFiP Mirror?
Neotimo DGFiP Mirror has the lower median latency in our checks — Data.gov responds in 931 ms versus Neotimo DGFiP Mirror at 524 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 Data.gov and Neotimo DGFiP Mirror need an API key?
Neither needs a paid key — Data.gov is callable with no signup, and Neotimo DGFiP Mirror is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Data.gov and Neotimo DGFiP Mirror from the browser?
Only Neotimo DGFiP Mirror is browser-friendly — it returns CORS headers over HTTPS. Data.gov needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are Data.gov and Neotimo DGFiP Mirror free for commercial use?
Data.gov has unclear commercial terms, and Neotimo DGFiP Mirror 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.