Integration
Connect USGS Earthquake Hazards Program to CleanURI
When something happens in USGS Earthquake Hazards Program, your agent does the next thing in CleanURI. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want USGS Earthquake Hazards Program and CleanURI to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with USGS Earthquake Hazards Program and CleanURI
Triggers and actions 1 trigger ยท 3 actions
Trigger
New earthquakePolling trigger over the real-time GeoJSON feed (e.g. https://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/{significant|4.5|2.5|1.0|all}_hour.geojson, configurable magnitude threshold/window) or the FDSN query endpoint ordered by time-desc. Fires once per new event id (dedup on feature.id), delivering magnitude, place, time, coordinates, depth.
- Find earthquakes by magnitude
Search earthquake events via GET https://earthquake.usgs.gov/fdsnws/event/1/query?format=geojson with filters (starttime, endtime, minmagnitude, maxmagnitude, mindepth, maxdepth, latitude, longitude, maxradiuskm, alertlevel, eventtype, orderby, limit). Returns a GeoJSON FeatureCollection of matching events.
- Get earthquake
Fetch a single earthquake event's detail via GET https://earthquake.usgs.gov/fdsnws/event/1/query?format=geojson&eventid={eventid}. Returns the full GeoJSON Feature including magnitude, place, time, coordinates and depth.
Action
Shorten URLgiven a long URL (form param 'url', URL-encoded, no spaces), returns {result_url} short link, or {error} on failure. Rate limit 2 req/sec per IP.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.