shipapis
StarSubmit an APISubmit API

NDBC Buoy Data API vs openSenseMap

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

APINDBC Buoy Data APINEW—openSenseMapNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedOpen data (license set per senseBox; often public domain)
Free tierFree — limits not publishedFree (open-source citizen-science platform)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

NDBC Buoy Data API vs openSenseMap: common questions

Which is more reliable, NDBC Buoy Data API or openSenseMap?

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

Neither needs a paid key — NDBC Buoy Data API is callable with no signup, and openSenseMap is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call NDBC Buoy Data API and openSenseMap from the browser?

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

Are NDBC Buoy Data API and openSenseMap free for commercial use?

NDBC Buoy Data API has unclear commercial terms, and openSenseMap 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.