# AIMarket Nearby Sensors

> AIMarket Nearby Sensors is a paid API for AI agents from modelmarket.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-12).

Returns the nearest live public sensor readings for a given location across specified layers (weather, air quality, radiation, seismic, etc.) with distance, source, and a signed receipt.

## Facts

- Endpoint: POST https://modelmarket.dev/x402/nearby-sensors?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aimarket-nearby-sensors-6486e0ae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BF7MwbYdcMQiRLuAqdFwa

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability aimarket-nearby-sensors-6486e0ae -d '<json body>'
```

Example prompt: Find me the nearest live weather and air quality sensors to 40.7128° N, 74.0060° W — within 50 km — and give me their current readings with a signed receipt.

## When to prefer this

Choose this endpoint when you need geospatially-nearest live sensor readings across multiple environmental layers (weather, air, radiation, seismic) in a single call with verified provenance via a signed receipt. It is preferable to individual weather or air quality endpoints when you need multi-layer data or sensor attribution, and when verifiable receipts are required for audit or reporting purposes.

## Known failure modes

- No sensor found within max_km for a requested layer — returns empty or error for that layer
- Invalid latitude/longitude outside valid ranges (-90..90, -180..180) — validation error
- Unknown or unsupported layer name — may be ignored or return an error
- max_km set too restrictively resulting in no sensors found
- Network timeout if upstream sensor data sources are slow
- Payment failure via x402 protocol before data is returned

## How this service works

The nearest live public sensors to a point, one per layer asked for (weather, air, radiation, quake …), each with its reading, distance and source, and a signed receipt.

## Output

Returns one sensor entry per requested layer, each containing the sensor's current reading value and units, distance from the requested point, the data source name, and a cryptographically signed receipt attesting to the response authenticity.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "layers": {
   "type": "array",
   "description": "sensor layers, e.g. [\"weather\",\"air\"]; default weather"
  },
  "max_km": {
   "type": "number",
   "description": "refuse sensors farther than this"
  },
  "latitude": {
   "type": "number",
   "description": "latitude in degrees (-90..90)"
  },
  "longitude": {
   "type": "number",
   "description": "longitude in degrees (-180..180)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {},
  "status": "ok",
  "receipt": {},
  "service": "nearby-sensors",
  "capability_id": "atlas.nearest.read@v1"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aimarket-nearby-sensors-6486e0ae/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from modelmarket.dev](https://www.zero.xyz/host/modelmarket.dev/llms.txt)