shipapis
StarSubmit an APISubmit API

Telegram Bot vs xfetch

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

APITelegram BotDEAD0xfetchDEAD0
Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Telegram Bot vs xfetch: common questions

Which is more reliable, Telegram Bot or xfetch?

Both are neck-and-neck — Telegram Bot and xfetch each measure 0.0% 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.

Do Telegram Bot and xfetch need an API key?

Both ask you to authenticate — Telegram Bot uses an API key and xfetch uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Telegram Bot and xfetch from the browser?

Yes — both Telegram Bot and xfetch 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 Telegram Bot and xfetch free for commercial use?

Telegram Bot has unclear commercial terms, and xfetch 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.