TensorFeed vs Not Human Search

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no key (static JSON feed endpoints)Free — no key for read endpoints (paid API-key plans offered)
Rate limit120 req/window · 119 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

TensorFeed vs Not Human Search: common questions

Which is more reliable, TensorFeed or Not Human Search?

On our scheduled checks, Not Human Search leads on measured uptime — TensorFeed at —% versus Not Human Search at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do TensorFeed and Not Human Search need an API key?

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

Can I call TensorFeed and Not Human Search from the browser?

Yes — both TensorFeed and Not Human Search 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 TensorFeed and Not Human Search free for commercial use?

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