Phonepe API vs Replicate

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesno
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

Phonepe API vs Replicate: common questions

Which is more reliable, Phonepe API or Replicate?

On our scheduled checks, Replicate leads on measured uptime — Phonepe API at —% versus Replicate 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 Phonepe API and Replicate need an API key?

Both ask you to authenticate — Phonepe API uses an API key and Replicate 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 Phonepe API and Replicate from the browser?

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

Are Phonepe API and Replicate free for commercial use?

Phonepe API has unclear commercial terms, and Replicate 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.