13trust / 100

Water Usgs

by Saylor Innovations Data Desk in Other

x402 APIFailing, checked 33 min ago

USGS river gauge reading - latest streamflow, gage height and water temperature for a USGS site number with 2-hour change

GET
https://saylorinnovations.com/api/water/usgs/:site
Price
$0.01
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
33 min ago, next in 28 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 33 min ago: Expected HTTP 402, got 404

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://saylorinnovations.com/api/water/usgs/:site

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

The listing has no example input.

GET https://saylorinnovations.com/api/water/usgs/:site

Example response

The provider's example. We can't check it without paying.

{
  "lat": 38.94977778,
  "lon": -77.12763889,
  "name": "POTOMAC RIVER NEAR WASH, DC LITTLE FALLS PUMP STA",
  "readings": {
    "discharge_cfs": {
      "change_over_window": 0,
      "observed_at": "2026-10-12T16:50:00.000-04:00",
      "value": 11500
    },
    "gage_height_ft": {
      "change_over_window": 0,
      "observed_at": "2026-10-12T16:50:00.000-04:00",
      "value": 4.13
    }
  },
  "site": "01646500",
  "source": "USGS National Water Information System",
  "window_note": "change_over_window compares the latest reading to the oldest in the last 2 hours"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://saylorinnovations.com/api/water/usgs/:site'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://saylorinnovations.com/api/water/usgs/:site' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsaylorinnovations.com%2Fapi%2Fwater%2Fusgs%2F%3Asite
const res = await pay("https://saylorinnovations.com/api/water/usgs/:site");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://saylorinnovations.com/api/water/usgs/:site")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
33 min agoExpected HTTP 402, got 404404361 ms-
6 h agoExpected HTTP 402, got 404404215 ms-
11 h agoExpected HTTP 402, got 404404191 ms-
17 h agoExpected HTTP 402, got 404404362 ms-
22 h agoExpected HTTP 402, got 404404396 ms-
Show 2 older checks
27 h agoExpected HTTP 402, got 404404450 ms-
31 h agoExpected HTTP 402, got 404404357 ms-