# SitePulse Satellite Change Detection

> SitePulse Satellite Change Detection is a paid API for AI agents from sitepulse.waltsoft.net, paid per call via x402, $1.5/call, status unknown (last checked 2026-10-16).

Detects construction, clearing, or revegetation at any lat/lon coordinate over the past 12 months using Sentinel-2 NDVI/NDBI change analysis

## Facts

- Endpoint: GET https://sitepulse.waltsoft.net/v1/site?utm_source=zero.xyz
- Price: $1.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sitepulse-satellite-change-detection-3e39e500
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G-u878CMnLI_n6ECaRIF4

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 sitepulse-satellite-change-detection-3e39e500
```

Example prompt: Can you check if the site at 37.7749° N, 122.4194° W has been built on or cleared in the last 12 months — I need the change direction and confidence level from satellite data.

## When to prefer this

Use SitePulse when you need a fast, per-coordinate answer about whether a specific site has undergone physical land-use change (construction, clearing, or revegetation) in the past year, backed by Sentinel-2 satellite evidence and confidence scoring. Prefer this over manual GIS workflows or generic satellite APIs when you need a structured, decision-ready output including change direction and scene evidence without needing to process raw imagery yourself.

## Known failure modes

- Coordinate outside Sentinel-2 coverage area — limited or no scenes available
- Persistent cloud cover over the location reducing scene count and confidence
- Insufficient scenes over the 12-month window resulting in 'inconclusive' change direction
- Invalid or missing lat/lon parameter causing request error
- Low confidence result when spectral change is marginal or ambiguous

## How this service works

Has this place been built on or cleared in the last 12 months? Sentinel-2 satellite change detection for any lat/lon: NDVI/NDBI deltas, change direction, confidence and the scene-by-scene evidence.

## Output

Returns a JSON object with: whether change was detected (boolean), the direction of change (built-up, revegetated, none, or inconclusive), a confidence rating (high/medium/low), number of Sentinel-2 scenes used, recent and baseline NDVI/NDBI index snapshots, and an array of scene-by-scene evidence items supporting the determination.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "site": {
   "type": "object",
   "description": "Echo of the requested coordinate"
  },
  "recent": {
   "type": "object"
  },
  "baseline": {
   "type": "object"
  },
  "evidence": {
   "type": "array",
   "items": {
    "type": "object"
   }
  },
  "confidence": {
   "enum": [
    "high",
    "medium",
    "low"
   ],
   "type": "string"
  },
  "scenes_used": {
   "type": "integer"
  },
  "change_detected": {
   "type": "boolean"
  },
  "change_direction": {
   "enum": [
    "built-up",
    "revegetated",
    "none",
    "inconclusive"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sitepulse-satellite-change-detection-3e39e500/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sitepulse.waltsoft.net](https://www.zero.xyz/host/sitepulse.waltsoft.net/llms.txt)