Skip to main content
POST
Fetch cited geospatial facts with an x402 payment
Fetch cited public facts for one US coordinate or street address using an x402 v2 payment. Each successful call costs $0.001 USDC on Base (eip155:8453), regardless of the number of selected fields. No Mireye account, API key, prepaid balance, or subscription is required for this route. Authenticated POST /v1/fetch remains free. This separate route lets wallet-equipped agents pay directly without creating an API key.

Payment flow

  1. Send the Fetch request below. Without payment, the API returns 402 with a Payment-Required header. Decode its base64-encoded x402 v2 JSON to read the payment requirements and extensions.bazaar discovery metadata. The response body is empty JSON ({}).
  2. An x402 client checks the amount, Base network and recipient, signs a USDC payment authorization, and retries the same request with Payment-Signature.
  3. After verification and successful execution, the payment settles. The 200 response contains Fetch data and a Payment-Response settlement header.
This request only inspects the payment requirements; it does not pay:
Use an x402 v2 compatible client with a Base wallet funded with USDC to complete the paid retry. A Mireye API key does not replace the payment on this route.

Data and limits

The request schema, US coverage, field selectors, presets, response provenance, address handling and capacity limits match Fetch. Parcel identity, ownership, boundaries and licensed parcel-derived fields are excluded. Use the authenticated Enrich API for those. Read partial_failures and each field’s status: a successful Fetch response can contain absent or failed fields and still costs the fixed call price. HTTP error responses do not proceed to settlement. Failed settlement withholds the data response.

Errors and retries

The account-wallet Idempotency-Key, max_cost_usd and /v1/operations recovery flow do not apply here. Configure spending limits in your x402 client. If a response is lost after signing, inspect the payment outcome before authorizing a new payment; a new authorization can create a separate charge.

Body

application/json
address
string | null
Required string length: 1 - 256
fields
string[] | null
lat
number | null
lng
number | null
preset
enum<string> | null
Available options:
terrain,
flood_risk,
wildfire_underwrite,
land_cover,
site_selection,
building_lookup,
points_of_interest,
utilities,
boundaries,
solar_siting,
wind_siting,
storage_siting,
data_center_siting,
grid_interconnect,
natural_hazard

Response

Successful Response