Bootprint vs TensorFeed

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms66302
P95 · ms291752
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key (static JSON feed endpoints)
Rate limitUnpublished120 req/window · 119 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bootprint vs TensorFeed: common questions

Which is more reliable, Bootprint or TensorFeed?

Both are neck-and-neck — Bootprint and TensorFeed 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, Bootprint or TensorFeed?

Bootprint has the lower median latency in our checks — Bootprint responds in 66 ms versus TensorFeed at 302 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 Bootprint and TensorFeed need an API key?

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

Can I call Bootprint and TensorFeed from the browser?

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

Are Bootprint and TensorFeed free for commercial use?

Bootprint has unclear commercial terms, and TensorFeed 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.