shipapis
StarSubmit an APISubmit API

DocForge vs Fake JSON API

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

APIDocForgeHEALTHY80Fake JSON APIHEALTHY88
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms1583865
P95 · ms24852006
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DocForge vs Fake JSON API: common questions

Which is more reliable, DocForge or Fake JSON API?

On our scheduled checks, DocForge leads on measured uptime — DocForge at 100% versus Fake JSON API at 99.02% 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 Fake JSON API?

Fake JSON API has the lower median latency in our checks — DocForge responds in 1583 ms versus Fake JSON API at 865 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 Fake JSON API need an API key?

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

Can I call DocForge and Fake JSON API from the browser?

Only Fake JSON API 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 Fake JSON API free for commercial use?

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