Image to Link vs What The Commit

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms2811312
P95 · ms9374279
Authnonenone
CORSyesyes
HTTPSyesno
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

Image to Link vs What The Commit: common questions

Which is more reliable, Image to Link or What The Commit?

On our scheduled checks, Image to Link leads on measured uptime — Image to Link at 100% versus What The Commit 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, Image to Link or What The Commit?

Image to Link has the lower median latency in our checks — Image to Link responds in 281 ms versus What The Commit at 1312 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 Image to Link and What The Commit need an API key?

Neither needs a paid key — Image to Link is callable with no signup, and What The Commit is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Image to Link and What The Commit from the browser?

Only Image to Link is browser-friendly — it returns CORS headers over HTTPS. What The Commit needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Image to Link and What The Commit free for commercial use?

Image to Link has unclear commercial terms, and What The Commit 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.