Phonepe API vs Satellite Passes

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

Uptime · 30d
Uptime · 90d99.44%99.44%
Uptime · 30d98.3%100%
P50 · ms496752
P95 · ms10852659
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Phonepe API vs Satellite Passes: common questions

Which is more reliable, Phonepe API or Satellite Passes?

Both are neck-and-neck — Phonepe API and Satellite Passes each measure 99.44% 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, Phonepe API or Satellite Passes?

Phonepe API has the lower median latency in our checks — Phonepe API responds in 496 ms versus Satellite Passes at 752 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 Phonepe API and Satellite Passes need an API key?

Satellite Passes needs no key, while Phonepe API requires a free API key. If you want to start calling without signup, reach for Satellite Passes first.

Can I call Phonepe API and Satellite Passes from the browser?

Yes — both Phonepe API and Satellite Passes 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 Phonepe API and Satellite Passes free for commercial use?

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