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 coastal overlays derived

api.locus.reportInferencederived

POST https://api.locus.report/api/locus-coastal-overlays

passlisted in Coinbase#64 by calls of 82 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-10-13 14:08 UTC · method · pinnable

Validation state
pass
as of 2026-10-30 07:16 UTC · method · pinnable · sweep daily-2026-10-30
Uptime, 7 / 30 / 90 days
83% / 79% / 85%
as of 2026-10-30 07:16 UTC · method · pinnable · 5 of 6 in 7d, 23 of 29 in 30d, 39 of 46 in 90d
Calls, trailing 30 days
1
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-07 15:39 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.05 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, 3 of them a change

How has the volume on this endpoint moved?

12110 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

Of api.locus.report's 82 listings, locus coastal overlays ranks tied 64th by calls with 18 others.

Requests carry a json body with the field address.

A response from locus coastal overlays, as declared, includes ok, note, point, county, layers, caveats and 2 others.

locus coastal overlays drew a single call from a single payer in the trailing 30 days.

The last call to locus coastal overlays came 6 days before the snapshot, 2026-10-07.

The declared price is 0.05 USDC on Base.

locus coastal overlays accepts payment on Base and Solana, 2 options in all, to 2 different wallets.

TOLL files locus coastal overlays under inference: a POST endpoint on api.locus.report, listed in the Coinbase registry.

locus coastal overlays answered the sweep of 2026-10-30 with a valid 402, passing 39 of 46 sweeps since 2026-09-11.

Closest in price to locus coastal overlays within inference: proofread file at api.aiskills402.com and agent at aeonos.basechainlabs.com.

locus coastal overlays is near the top of prices in inference; 95% of comparable listings are cheaper.

The wallet paid by locus coastal overlays is the payee of 101 endpoints across 3 hosts.

The price of locus coastal overlays is declared by 126 other listings in inference too.

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.05 USDCexact0xF121fb…64431b
Coinbasesolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpUSDC0.05 USDCexactFBVHMG5P…DpQdwV

Preflight checks at the last sweep

the checks, as of 2026-10-30 07:16 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 07:16 UTCpass0daily-2026-10-30
2026-10-29 06:57 UTCpass0daily-2026-10-29
2026-10-28 07:20 UTCpass0daily-2026-10-28
2026-10-27 07:10 UTCpass0daily-2026-10-27
2026-10-26 12:30 UTCfail1daily-2026-10-26
2026-10-24 21:52 UTCpass0daily-2026-10-24
2026-10-23 07:09 UTCpass0daily-2026-10-23
2026-10-22 05:24 UTCfail1daily-2026-10-22
2026-10-21 09:03 UTCpass0daily-2026-10-21
2026-10-20 09:15 UTCpass0daily-2026-10-20
2026-10-19 06:51 UTCpass0daily-2026-10-19
2026-10-18 09:01 UTCpass0daily-2026-10-18
2026-10-17 19:03 UTCfail1daily-2026-10-17
2026-10-16 05:14 UTCpass0daily-2026-10-16
2026-10-15 06:52 UTCpass0daily-2026-10-15
2026-10-14 05:09 UTCpass0daily-2026-10-14
2026-10-13 09:41 UTCpass0daily-2026-10-13
2026-10-12 07:05 UTCpass0daily-2026-10-12
2026-10-11 05:29 UTCpass0daily-2026-10-11
2026-10-10 13:47 UTCpass0daily-2026-10-10
2026-10-09 05:45 UTCpass0daily-2026-10-09
2026-10-08 07:28 UTCpass0daily-2026-10-08
2026-10-07 06:39 UTCpass0daily-2026-10-07
2026-10-06 07:31 UTCpass0daily-2026-10-06
2026-10-05 07:00 UTCfail1daily-2026-10-05
2026-10-04 09:44 UTCfail1daily-2026-10-04
2026-10-03 04:46 UTCfail1daily-2026-10-03
2026-10-02 14:00 UTCpass0daily-2026-10-02
2026-10-01 07:05 UTCpass0daily-2026-10-01
2026-09-30 06:22 UTCpass0daily-2026-09-30
2026-09-29 18:43 UTCpass0daily-2026-09-29
2026-09-28 04:34 UTCpass0daily-2026-09-28
2026-09-25 20:16 UTCfail1daily-2026-09-25
2026-09-23 05:56 UTCpass0daily-2026-09-23
2026-09-22 06:06 UTCpass0daily-2026-09-22
2026-09-21 06:29 UTCpass0daily-2026-09-21
2026-09-20 19:08 UTCpass0daily-2026-09-20
2026-09-19 04:29 UTCpass0daily-2026-09-19
2026-09-18 10:20 UTCpass0daily-2026-09-18
2026-09-17 04:27 UTCpass0daily-2026-09-17
2026-09-16 04:28 UTCpass0daily-2026-09-16
2026-09-15 04:26 UTCpass0daily-2026-09-15
2026-09-14 04:22 UTCpass0daily-2026-09-14
2026-09-13 04:21 UTCpass0daily-2026-09-13
2026-09-12 06:37 UTCpass0daily-2026-09-12
2026-09-11 10:07 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:39 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "address": "1 SE 3rd Ave, Miami, FL 33131"
    },
    "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.",
      "point": {
        "latitude": 25.773907,
        "longitude": -80.18856
      },
      "county": {
        "id": "miami-dade-fl",
        "fips": "12086",
        "name": "Miami-Dade County, FL",
        "state": "FL",
        "county": "Miami-Dade",
        "layers": [
          {
            "key": "parcel",
            "title": "Parcels @ PaParcel",
            "status": "queryable",
            "category": "parcel",
            "layerUrl": "https://gisweb.miamidade.gov/arcgis/rest/services/MD_LandInformation/MapServer/26",
            "sourceUrl": "https://gisweb.miamidade.gov/arcgis/rest/services/MD_LandInformation/MapServer",
            "sourceName": "Miami-Dade GIS - MD_LandInformation",
            "officialPage": "https://gisweb.miamidade.gov/emaps"
          },
          {
            "key": "zoning",
            "title": "Municipal Zoning @ MunicipalZone",
            "status": "queryable",
            "category": "zoning",
            "layerUrl": "https://gisweb.miamidade.gov/arcgis/rest/services/MD_LandInformation/MapServer/19",
            "sourceUrl": "https://gisweb.miamidade.gov/arcgis/rest/services/MD_LandInformation/MapServer",
            "sourceName": "Miami-Dade GIS - MD_LandInformation",
            "officialPage": "https://gisweb.miamidade.gov/emaps"
          }
        ],
        "caveats": [
          "County flood layer can lag FEMA map revisions; verify with FEMA NFHL.",
          "Not insurance/legal/appraisal/safe-unsafe."
        ],
        "coverage": "queryable",
        "verifyNext": [
          {
            "url": "https://gisweb.miamidade.gov/emaps",
            "step": "Verify parcel/zoning/flood in the county GIS viewer.",
            "source": "Miami-Dade GIS"
          }
        ],
        "description": "Official Miami-Dade County, FL coastal GIS overlays for parcel, zoning, flood."
      },
      "layers": [
        {
          "key": "parcel",
          "title": "Parcels @ PaParcel",
          "source": {
            "layerUrl": "https://gisweb.miamidade.gov/arcgis/rest/services/MD_LandInformation/MapServer/26",
            "fetchedAt": "2026-09-23T01:11:13.187Z",
            "sourceUrl": "https://gisweb.miamidade.gov/arcgis/rest/services/MD_LandInformation/MapServer",
            "sourceName": "Miami-Dade GIS - MD_LandInformation"
          },
          "status": "ok",
          "records": [
            {
              "PID": 483148,
              "FOLIO": "0101120003001",
              "DOR_DESC": "OFFICE BUILDING - MULTISTORY : OFFICE BUILDING",
              "LOT_SIZE": 46844,
              "DOR_CODE_CUR": "1813",
              "LAND_VAL_CUR": 28106400,
              "PRIMARY_ZONE": "6401",
              "TOTAL_VAL_CUR": 91300000,
              "TRUE_SITE_ADDR": "1 SE 3 AVE",
              "TRUE_SITE_CITY": "Miami",
              "BUILDING_VAL_CUR": 63193600,
              "TRUE_SITE_ZIP_CODE": "33131-0000"
            }
          ],
          "category": "parcel"
        },
        {
          "key": "zoning",
          "title": "Municipal Zoning @ MunicipalZone",
          "source": {
            "layerUrl": "https://gisweb.miamidade.gov/arcgis/rest/services/MD_LandInformation/MapServer/19",
            "fetchedAt": "2026-09-23T01:11:13.187Z",
            "sourceUrl": "https://gisweb.miamidade.gov/arcgis/rest/services/MD_LandInformation/MapServer",
            "sourceName": "Miami-Dade GIS - MD_LandInformation"
          },
          "status": "ok",
          "records": [
            {
              "ZONE": "T6-80-O",
              "ZONEDESC": "URBAN CORE ZONE",
              "MUNICNAME": "MIAMI",
              "GENRLLUTYPE": "RC"
            }
          ],
          "category": "zoning"
        }
      ],
      "caveats": [
        "County flood layer can lag FEMA map revisions; verify with FEMA NFHL.",
        "Not insurance/legal/appraisal/safe-unsafe."
      ],
      "matched": true,
      "overhangs": [],
      "verifyNext": [
        {
          "url": "https://gisweb.miamidade.gov/emaps",
          "step": "Verify parcel/zoning/flood in the county GIS viewer.",
          "source": "Miami-Dade GIS"
        }
      ],
      "resolvedCounty": {
        "stateAbbr": "FL",
        "stateFips": "12",
        "countyName": "Miami-Dade County",
        "countyFips3": "086",
        "countyFips5": "12086"
      },
      "officialReferences": [
        {
          "url": "https://www.fema.gov/flood-maps/national-flood-hazard-layer",
          "name": "FEMA National Flood Hazard Layer"
        },
        {
          "url": "https://www.floodsmart.gov/get-insured/eligibility",
          "name": "FloodSmart: flood insurance eligibility"
        }
      ]
    }
  }
}
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 coastal overlays on api.locus.report", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-locus-report-api-locus-coastal-overlays-370a4c/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-api-locus-report-api-locus-coastal-overlays-370a4c-2026-10-13T14-08Z,
  author = {TOLL},
  title = {locus coastal overlays on api.locus.report},
  howpublished = {\url{https://tollindex.com/e/api-locus-report-api-locus-coastal-overlays-370a4c/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 coastal overlays, 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 370a4ca09f4262ae335a0dd77ffc9455b298574776a638d00386593033024dc4 from wallet 0xF121fbeceC43e1B616D47285851c20d5fC64431b

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

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