TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-30 · finished 2026-10-30 13:00 UTC
Listed
32,435

locus traffic crash context derived

api.locus.reportInferencederived

POST https://api.locus.report/api/locus-traffic-crash-context

passlisted in Coinbase#22 by calls of 82 on this host

0.01 USDC

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

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-10-13 14:08 UTC · method · pinnable

Validation state
pass
as of 2026-10-30 12:46 UTC · method · pinnable · sweep daily-2026-10-30
Uptime, 7 / 30 / 90 days
75% / 74% / 67%
as of 2026-10-30 12:46 UTC · method · pinnable · 3 of 4 in 7d, 17 of 23 in 30d, 24 of 36 in 90d
Calls, trailing 30 days
3
as of 2026-10-13 14:08 UTC · method · pinnable
Unique payers, trailing 30 days
1
as of 2026-10-13 14:08 UTC · method · pinnable
Last called
2026-10-05 18:01 UTC
as of 2026-10-13 14:08 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.01 USDC
as of 2026-10-13 14:08 UTC · method · pinnable · on eip155:8453
Networks
2
as of 2026-10-13 14:08 UTC · method · pinnable

Counters

122 observations, 4 of them a change

How has the volume on this endpoint moved?

1234310 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 Oct
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

api.locus.report lists 82 endpoints; locus traffic crash context is tied 22nd by calls with 28 others.

locus traffic crash context takes a json body with the fields address, radiiMeters and lookbackYears.

A response from locus traffic crash context, as declared, includes ok, caveats, sources, coverage, verifyNext, radiiMeters and 2 others.

One payer accounts for all 3 calls to locus traffic crash context over 30 days.

The last call to locus traffic crash context came 8 days before the snapshot, 2026-10-05.

On Base, locus traffic crash context asks 0.01 USDC per call.

locus traffic crash context takes 1% of the calls counted across api.locus.report.

For locus traffic crash context the listing declares 2 accepts on Base and Solana, to 2 different wallets.

At api.locus.report, locus traffic crash context takes POST requests, is listed in the Coinbase registry, and falls under inference by TOLL's rules.

locus traffic crash context answered the sweep of 2026-10-30 with a valid 402, passing 24 of 36 sweeps since 2026-09-11.

Closest in price to locus traffic crash context within inference: llm at agent402.tools and council at council.cyberwarex.com.

locus traffic crash context is priced above 14% of comparable listings in inference.

Within inference, 84% of endpoints with counters have fewer calls.

The wallet paid by locus traffic crash context is the payee of 101 endpoints across 3 hosts.

Exactly this price appears on 6,800 other listings in inference.

Payment options as declared

the payment options, as of 2026-10-13 14:08 UTC · method · pinnable

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

Preflight checks at the last sweep

the checks, as of 2026-10-30 12:46 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 12:46 UTCpass0daily-2026-10-30
2026-10-29 12:27 UTCfail1daily-2026-10-29
2026-10-28 12:53 UTCpass0daily-2026-10-28
2026-10-27 12:31 UTCpass0daily-2026-10-27
2026-10-23 13:05 UTCpass0daily-2026-10-23
2026-10-21 22:20 UTCfail1daily-2026-10-21
2026-10-19 12:44 UTCpass0daily-2026-10-19
2026-10-16 10:26 UTCpass0daily-2026-10-16
2026-10-15 12:26 UTCfail1daily-2026-10-15
2026-10-14 10:18 UTCpass0daily-2026-10-14
2026-10-13 15:37 UTCpass0daily-2026-10-13
2026-10-12 12:43 UTCpass0daily-2026-10-12
2026-10-11 11:18 UTCpass0daily-2026-10-11
2026-10-10 19:26 UTCpass0daily-2026-10-10
2026-10-09 13:06 UTCpass0daily-2026-10-09
2026-10-08 15:01 UTCpass0daily-2026-10-08
2026-10-07 14:16 UTCpass0daily-2026-10-07
2026-10-06 14:43 UTCpass0daily-2026-10-06
2026-10-05 12:49 UTCfail1daily-2026-10-05
2026-10-04 15:16 UTCfail1daily-2026-10-04
2026-10-03 08:20 UTCfail1daily-2026-10-03
2026-10-02 17:26 UTCpass0daily-2026-10-02
2026-10-01 10:04 UTCpass0daily-2026-10-01
2026-09-30 09:30 UTCpass0daily-2026-09-30
2026-09-29 21:36 UTCfail1daily-2026-09-29
2026-09-23 08:28 UTCfail1daily-2026-09-23
2026-09-22 08:41 UTCpass0daily-2026-09-22
2026-09-21 09:02 UTCpass0daily-2026-09-21
2026-09-19 06:59 UTCfail1daily-2026-09-19
2026-09-17 06:51 UTCfail1daily-2026-09-17
2026-09-16 06:48 UTCfail1daily-2026-09-16
2026-09-15 07:04 UTCfail1daily-2026-09-15
2026-09-14 06:30 UTCpass0daily-2026-09-14
2026-09-13 06:20 UTCpass0daily-2026-09-13
2026-09-12 10:29 UTCpass0daily-2026-09-12
2026-09-11 14:49 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-05 18:01 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "address": "1 E Edenton St, Raleigh, NC 27601",
      "radiiMeters": [
        200,
        500,
        1000
      ],
      "lookbackYears": 3
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "ok": true,
      "caveats": [
        "Police reports do not include every crash, and reporting thresholds and classification practices differ across jurisdictions."
      ],
      "sources": [
        {
          "status": "ok",
          "caveats": [
            "This is a pedestrian/bicycle subset only and must not be described as all reported North Carolina crashes."
          ],
          "sourceId": "nc-ncdot-nonmotorist-crashes",
          "geography": "North Carolina",
          "updateLag": "Verified through 2025; publication can lag the current year",
          "aggregates": [
            {
              "modes": [
                {
                  "count": null,
                  "normalized": "bicycle",
                  "suppressed": true,
                  "displayCount": "<3",
                  "officialLabel": "Bicyclist"
                }
              ],
              "total": null,
              "severity": [
                {
                  "count": null,
                  "normalized": "serious_injury",
                  "suppressed": true,
                  "displayCount": "<3",
                  "officialLabel": "A: Suspected Serious Injury"
                }
              ],
              "radiusMeters": 200,
              "totalSuppressed": true
            }
          ],
          "provenance": {
            "sourceId": "nc-ncdot-nonmotorist-crashes",
            "authority": "North Carolina Department of Transportation",
            "checkedAt": "2026-09-23T01:11:51.303Z",
            "fetchedAt": "2026-09-23T01:11:51.847Z",
            "sourceName": "NCDOT Non-Motorist Crashes",
            "queryLocator": "https://services.arcgis.com/NuWFvHYDMVmmxMeM/arcgis/rest/services/NCDOT_NonMotoristCrashes/FeatureServer/0/query",
            "sourceIdentifier": "NCDOT_NonMotoristCrashes/FeatureServer/0",
            "officialSourceUrl": "https://services.arcgis.com/NuWFvHYDMVmmxMeM/arcgis/rest/services/NCDOT_NonMotoristCrashes/FeatureServer/0",
            "recordIdentifiers": [],
            "recordIdentifierNote": "Source-side aggregate query; individual crash identifiers are intentionally not fetched or returned."
          },
          "severityClass": "nonmotorist_only",
          "updateCadence": "Periodic statewide release",
          "availableYears": {
            "from": 2007,
            "through": 2025
          }
        }
      ],
      "coverage": "localized_plus_fatal_companion",
      "verifyNext": [
        {
          "step": "Review the named source's severity class, available years, and update lag before comparing counts."
        }
      ],
      "radiiMeters": [
        200
      ],
      "localCoverage": {
        "combinationNote": "North Carolina subset totals are not combined because K+A and non-motorist records can overlap; neither source is all-report coverage.",
        "severityClasses": [
          "nonmotorist_only"
        ],
        "combinedSourceTotal": null,
        "allReportedAvailable": false
      },
      "requestedWindow": {
        "from": "2023-09-23",
        "through": "2026-09-23",
        "lookbackYears": 3
      },
      "registryCoverage": {
        "label": "Chicago all-reported; Virginia reportable-threshold; North Carolina partial subsets (K+A and nonmotorist); Pikes Peak region reportable-threshold; nationwide FARS fatal-only companion",
        "supportedLocalGeographies": [
          "Chicago"
        ]
      }
    }
  }
}
Cite this page

The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 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 traffic crash context on api.locus.report", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-locus-report-api-locus-traffic-crash-context-f7a080/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-api-locus-report-api-locus-traffic-crash-context-f7a080-2026-10-13T14-08Z,
  author = {TOLL},
  title = {locus traffic crash context on api.locus.report},
  howpublished = {\url{https://tollindex.com/e/api-locus-report-api-locus-traffic-crash-context-f7a080/at/2026-10-13T14-08Z}},
  year = {2026},
  month = {10},
  note = {Pinned view of the snapshot of 2026-10-13 14:08 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 traffic crash context, 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 f7a080cc6f9dc732d797de0e1608267ffa9b253a8ae7cfa158fd6d117c15b12b from wallet 0xF121fbeceC43e1B616D47285851c20d5fC64431b

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

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