USGS APIs

US Geological Survey collection of public APIs covering earthquake data, water resources, national map services, and geological data — each as a separate endpoint collection.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Other usgs government earthquakes water geology geospatial maps public-data
⚙ Agent Friendliness
47
/ 100
Can an agent use this?
🔒 Security
52
/ 100
Is it safe for agents?
⚡ Reliability
60
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
--
Documentation
72
Error Messages
58
Auth Simplicity
95
Rate Limits
38

🔒 Security

TLS Enforcement
100
Auth Strength
40
Scope Granularity
10
Dep. Hygiene
55
Secret Handling
60

HTTPS enforced. No authentication means no security model to evaluate. Public data only. Government infrastructure with no published security certifications. No secret handling concerns because there are no secrets.

⚡ Reliability

Uptime/SLA
38
Version Stability
75
Breaking Changes
78
Error Recovery
48
AF Security Reliability

Best When

Accessing authoritative US government geological, hydrological, or earthquake data for research, monitoring, or mapping applications.

Avoid When

You need a single unified API, commercial SLAs, or non-US data. The fragmented nature of USGS APIs requires significant integration effort.

Use Cases

  • Earthquake monitoring and seismic activity feeds
  • Streamflow and water level monitoring
  • Geological hazard assessment and mapping
  • National map tile and elevation data retrieval
  • Environmental research and citizen science integrations

Not For

  • Non-US geographic data
  • Real-time commercial SLA requirements
  • Unified data access (each USGS service has a separate API)

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: none
OAuth: No Scopes: No

No authentication required. All USGS APIs are fully public. No API keys, no rate limit registration.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Completely free government APIs. No pricing structure. Fair use expected; aggressive scraping may be rate-limited.

Agent Metadata

Pagination
offset
Idempotent
True
Retry Guidance
Not documented

Known Gotchas

  • Not a single API — USGS has 10+ separate service families with different schemas and endpoints
  • Earthquake API uses FDSN standards; Water Services uses its own schema — agents must handle both
  • Some services return GeoJSON, others return WaterML, others return CSV — response format varies
  • No centralized documentation — each service has its own doc site
  • Informal rate limits not documented; aggressive use may result in IP blocking with no clear feedback
  • Data latency varies: earthquake data near-realtime, some water data delayed hours or days
  • Map tile services use OGC WMS/WMTS standards requiring specialized clients

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for USGS APIs.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6411
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered