TOLL

What software pays for, recorded every six hours.

Snapshot
2026-11-01 21:59 UTC
Sweep
daily-2026-10-30 · finished 2026-10-30 13:00 UTC
Listed
52,265

locus drinking water violations derived

api.locus.reportInferencederived

POST https://api.locus.report/api/locus-drinking-water-violations

passlisted in Coinbase#27 by calls of 59 on this host

0.05 USDC

per call, as the listing declares it on eip155:8453

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-11-01 21:59 UTC · method · pinnable

Validation state
pass
as of 2026-10-30 10:38 UTC · method · pinnable · sweep daily-2026-10-30
Uptime, 7 / 30 / 90 days
80% / 79% / 88%
as of 2026-10-30 10:38 UTC · method · pinnable · 4 of 5 in 7d, 19 of 24 in 30d, 36 of 41 in 90d
Calls, trailing 30 days
1
as of 2026-11-01 21:59 UTC · method · pinnable
Unique payers, trailing 30 days
1
as of 2026-11-01 21:59 UTC · method · pinnable
Last called
2026-10-07 15:44 UTC
as of 2026-11-01 21:59 UTC · method · pinnable
First observed by TOLLderived
2026-09-10
as of 2026-09-10 19:08 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.05 USDC
as of 2026-11-01 21:59 UTC · method · pinnable · on eip155:8453
Networks
2
as of 2026-11-01 21:59 UTC · method · pinnable

Counters

125 observations, 5 of them a change

How has the volume on this endpoint moved?

123110 Sep11 Sep12 Sep13 Sep14 Sep15 Sep16 Sep17 Sep18 Sep19 Sep20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep26 Sep27 Sep28 Sep29 Sep30 Sep1 Oct2 Oct3 Oct4 Oct5 Oct6 Oct7 Oct8 Oct9 Oct10 Oct11 Oct12 Oct13 Oct1 Nov
Calls counted in the trailing 30 days on this endpoint, at every snapshot since 2026-09-10. Each point is a trailing-30-day sum as the registry published it, not a daily rate. The axis is truncated to the range of the data with a break at its foot.

In words

locus drinking water violations is one of 59 listed endpoints on api.locus.report, tied 27th by calls with 32 others among them.

locus drinking water violations takes a json body with the field address.

A response from locus drinking water violations, as declared, includes ok, note, place, point, query, caveats and 2 others.

locus drinking water violations drew a single call from a single payer in the trailing 30 days.

The last call to locus drinking water violations came 25 days before the snapshot, 2026-10-07.

The declared price is 0.05 USDC on Base.

For locus drinking water violations the listing declares 2 accepts on Base and Solana, to 2 different wallets.

TOLL files locus drinking water violations under inference: a POST endpoint on api.locus.report, listed in the Coinbase registry.

locus drinking water violations answered the sweep of 2026-10-30 with a valid 402, passing 36 of 41 sweeps since 2026-09-11.

Closest in price to locus drinking water violations within inference: claude opus 5 at api.glianalabs.com and midas ops premium at midax402.com.

locus drinking water violations is near the top of prices in inference; 97% of comparable listings are cheaper.

The wallet paid by locus drinking water violations is the payee of 104 endpoints across 3 hosts.

The price of locus drinking water violations is declared by 207 other listings in inference too.

Payment options as declared

the payment options, as of 2026-11-01 21:59 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.05 USDCexact0xF121fb…64431b
Coinbasesolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpUSDC0.05 USDCexactFBVHMG5P…DpQdwV

Preflight checks at the last sweep

the checks, as of 2026-10-30 10:38 UTC · method · pinnableendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-30 10:38 UTCpass0daily-2026-10-30
2026-10-29 10:15 UTCpass0daily-2026-10-29
2026-10-28 10:37 UTCfail1daily-2026-10-28
2026-10-27 10:18 UTCpass0daily-2026-10-27
2026-10-26 16:39 UTCpass0daily-2026-10-26
2026-10-23 10:40 UTCfail1daily-2026-10-23
2026-10-21 19:58 UTCpass0daily-2026-10-21
2026-10-20 20:52 UTCpass0daily-2026-10-20
2026-10-19 10:27 UTCpass0daily-2026-10-19
2026-10-18 18:01 UTCpass0daily-2026-10-18
2026-10-16 08:19 UTCpass0daily-2026-10-16
2026-10-15 10:14 UTCpass0daily-2026-10-15
2026-10-14 08:06 UTCpass0daily-2026-10-14
2026-10-13 12:57 UTCpass0daily-2026-10-13
2026-10-12 10:20 UTCpass0daily-2026-10-12
2026-10-11 08:58 UTCpass0daily-2026-10-11
2026-10-10 17:12 UTCpass0daily-2026-10-10
2026-10-09 10:17 UTCpass0daily-2026-10-09
2026-10-08 11:49 UTCpass0daily-2026-10-08
2026-10-07 11:06 UTCpass0daily-2026-10-07
2026-10-06 11:47 UTCpass0daily-2026-10-06
2026-10-05 10:27 UTCfail1daily-2026-10-05
2026-10-04 13:23 UTCfail1daily-2026-10-04
2026-10-03 06:56 UTCfail1daily-2026-10-03
2026-10-02 16:06 UTCpass0daily-2026-10-02
2026-10-01 08:53 UTCpass0daily-2026-10-01
2026-09-30 08:17 UTCpass0daily-2026-09-30
2026-09-29 20:27 UTCpass0daily-2026-09-29
2026-09-28 17:35 UTCpass0daily-2026-09-28
2026-09-23 07:26 UTCpass0daily-2026-09-23
2026-09-22 07:40 UTCpass0daily-2026-09-22
2026-09-21 08:01 UTCpass0daily-2026-09-21
2026-09-19 06:01 UTCpass0daily-2026-09-19
2026-09-18 14:43 UTCpass0daily-2026-09-18
2026-09-17 05:53 UTCpass0daily-2026-09-17
2026-09-16 05:52 UTCpass0daily-2026-09-16
2026-09-15 06:09 UTCpass0daily-2026-09-15
2026-09-14 05:40 UTCpass0daily-2026-09-14
2026-09-13 05:33 UTCpass0daily-2026-09-13
2026-09-12 07:50 UTCpass0daily-2026-09-12
2026-09-11 11:43 UTCpass0daily-2026-09-11

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

  1. listed in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-10-07 15:44 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "address": "1 E Edenton St, Raleigh, NC 27601"
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "ok": true,
      "note": "Awareness/diagnostic only. Full briefs are x402-paid. Agents can discover live free tools at https://api.locus.report/tools/list and paid tools, prices, and manifests at https://api.locus.report/.well-known/ai-tool/index.json.",
      "place": {
        "county": "Wake County",
        "stateAbbr": "NC",
        "countyFips3": "183"
      },
      "point": {
        "latitude": 35.780418000003195,
        "longitude": -78.63910200000142
      },
      "query": {
        "pwsids": [
          "NC0392010"
        ]
      },
      "caveats": [
        "Point-in-polygon containment identifies a candidate utility or published provider boundary, not proof of an active account or connection. Confirm with the utility; a water bill names the actual provider."
      ],
      "provenance": {
        "source": "EPA SDWIS / ECHO Safe Drinking Water Act violation and enforcement records",
        "coverage": "United States public water systems where SDWIS publishes violation/enforcement rows",
        "serviceUrl": "https://data.epa.gov/efservice/SDW_VIOL_ENFORCEMENT",
        "sourcePage": "https://echo.epa.gov/tools/data-downloads/sdwa-download-summary"
      },
      "verifyNext": [
        {
          "url": "https://www.epa.gov/ground-water-and-drinking-water/public-water-system-service-areas",
          "step": "Confirm the serving utility directly (a water bill names it); service-area boundary containment does not prove an active account or connection."
        }
      ],
      "violations": [
        {
          "pwsid": "NC0392010",
          "systemName": "RALEIGH, CITY OF",
          "officialUrl": "https://echo.epa.gov/detailed-facility-report?fid=NC0392010",
          "violationId": "3285707",
          "violationCode": "24",
          "violationName": "Monitoring, Routine Minor (TCR)",
          "contaminantCode": "3100",
          "contaminantName": "Coliform (TCR)",
          "enforcementDate": "2010-09-01",
          "compliancePeriod": {
            "end": "2006-01-31",
            "begin": "2006-01-01"
          },
          "enforcementAction": "SOX",
          "violationCategory": "Monitoring and Reporting",
          "enforcementActionName": "St Compliance achieved"
        }
      ],
      "systemsBasis": "service_area_boundary",
      "systemsChecked": [
        {
          "pwsid": "NC0392010"
        }
      ],
      "systemsQueried": 1,
      "componentStatus": [
        {
          "status": "ok",
          "component": "sdwis_violation_enforcement"
        }
      ],
      "systemsRetrieved": 1,
      "serviceAreaMatched": true,
      "serviceAreaResolution": {
        "point": {
          "latitude": 35.780418000003195,
          "longitude": -78.63910200000142
        },
        "source": {
          "name": "EPA Community Water System Service Area Boundaries (EPA Office of Research and Development)",
          "layerUrl": "https://services.arcgis.com/cJ9YHowT8TU7DUyn/arcgis/rest/services/Water_System_Boundaries/FeatureServer/0",
          "fetchedAt": "2026-09-23T01:11:19.075Z",
          "sourcePage": "https://www.epa.gov/ground-water-and-drinking-water/public-water-system-service-areas"
        },
        "status": "matched",
        "caveats": [
          "Point-in-polygon containment identifies a candidate utility or published provider boundary, not proof of an active account or connection. Confirm with the utility; a water bill names the actual provider."
        ],
        "systems": [
          {
            "name": "RALEIGH, CITY OF",
            "pwsid": "NC0392010",
            "boundary": {
              "basis": "provider_supplied",
              "confidence": "high",
              "dataProvider": "NC Center for Geographic Information and Analysis",
              "verification": "verified",
              "confidenceNote": "Provider-supplied boundary marked Verified in the EPA layer.",
              "dataProviderType": "State Agency",
              "verificationStatus": "Verified"
            },
            "primacyAgency": "NC",
            "serviceAreaType": "Municipality",
            "populationServed": 640000,
            "serviceConnections": 200114
          }
        ],
        "multipleMatches": false
      }
    }
  }
}
Cite this page

The pinned URL below renders this page from the snapshot of 2026-11-01 21:59 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "locus drinking water violations on api.locus.report", snapshot of 2026-11-01 21:59 UTC. https://tollindex.com/e/api-locus-report-api-locus-drinking-water-violations-a9a218/at/2026-11-01T21-59Z. Accessed [access date].

BibTeX

@misc{toll-e-api-locus-report-api-locus-drinking-water-violations-a9a218-2026-11-01T21-59Z,
  author = {TOLL},
  title = {locus drinking water violations on api.locus.report},
  howpublished = {\url{https://tollindex.com/e/api-locus-report-api-locus-drinking-water-violations-a9a218/at/2026-11-01T21-59Z}},
  year = {2026},
  month = {11},
  note = {Pinned view of the snapshot of 2026-11-01 21:59 UTC. Accessed [access date].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about locus drinking water violations, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint a9a21891ba4e9a95cbc4b4b54b252ee047ad9d056c8324382dd5dc9bd99d144a from wallet 0xF121fbeceC43e1B616D47285851c20d5fC64431b

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.