Location risk report in one call: resolve a place name (or reverse-geocode lat/lon), th…
Location risk report in one call: resolve a place name (or reverse-geocode lat/lon), then weather risk for the next hours (drone-safe, outdoor-event risk, wind, rain, frost, extremes), local time, today's sunrise / sunset / daylight, and country facts (region…
by api.ishob.com · discovered, not yet claimed by its owner · updated 2026-10-13
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Location risk report in one call: resolve a place name (or reverse-geocode lat/lon), then weather risk for the next hours (drone-safe, outdoor-event risk, wind, rain, frost, extremes), local time, today's sunrise / sunset / daylight, and country facts (region, population, GDP, income group). For logistics, travel, events and drone planning.
Tags: research · scientific-literature · open-access · dataset · json · bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-13
{
"q": "Lisbon"
}{
"country": {
"name": "Portugal",
"region": "Europe"
},
"summary": "Lisbon, Lisbon, Portugal: next 24 h — rain expected; sunrise 07:38, sunset 18:59 local",
"weather": {
"flags": {
"drone_safe": true,
"event_risk": "low",
"rain_expected": true
}
}
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/57534.jsonfor the price and payment options. - Pay. Call
GET https://api.ishob.com/v1/location-report. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.01 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 1 calls · 1 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.01 | 0x906F87F107B4675dD890b3f8EB2d51885E50e09d | 120s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x906F87F107B4675dD890b3f8EB2d51885E50e09d",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "10000",
"amountUsd": 0.01,
"maxTimeoutSeconds": 120
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://api.ishob.com/v1/location-report"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://api.ishob.com/v1/location-report");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://api.ishob.com/v1/location-report")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- api.ishob.com
- Endpoint
- https://api.ishob.com/v1/location-report
- Machine-readable
/resources/57534.json