# Coin Railz Satellite Flood Detection

> Coin Railz Satellite Flood Detection is a paid API for AI agents from coinrailz.com, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Monitors surface water extent and flood conditions using Sentinel-1 SAR satellite imagery

## Facts

- Endpoint: GET https://coinrailz.com/api/satellite/flood-detection
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/coin-railz-satellite-flood-detection-1405611b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yWGKVTyWsfEsriUEMDjbq

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 coin-railz-satellite-flood-detection-1405611b
```

Example prompt: Can you run a flood detection check using the Coin Railz satellite service for my agent ID 'agent-007'? I want to see current surface water extent and whether any flooding is detected.

## When to prefer this

Choose this endpoint when you need satellite-based flood or surface water detection using SAR (Synthetic Aperture Radar) data from Sentinel-1, which can detect water through clouds and at night. Prefer over optical satellite services when cloud cover is a concern.

## Known failure modes

- Missing agentId returns validation error
- Invalid or unrecognized agentId may return unauthorized error
- Payment of 0.1 USDC not provided results in 402 Payment Required
- Network connectivity issues may return timeout or 503 error
- Unsupported network values in the networks array may be ignored or cause errors

## How this service works

Surface water extent and flood monitoring from Sentinel-1 SAR

## Output

Returns a JSON object with success status, service name ('flood-detection'), a result message, and a UTC timestamp indicating when the analysis was performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "west",
  "south",
  "east",
  "north"
 ],
 "properties": {
  "east": {
   "type": "number",
   "description": "Eastern longitude boundary (-180 to 180)"
  },
  "west": {
   "type": "number",
   "description": "Western longitude boundary (-180 to 180)"
  },
  "north": {
   "type": "number",
   "description": "Northern latitude boundary (-90 to 90)"
  },
  "south": {
   "type": "number",
   "description": "Southern latitude boundary (-90 to 90)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "application/json",
 "format": "json",
 "example": {
  "result": "Service executed successfully",
  "service": "flood-detection",
  "success": true,
  "timestamp": "2026-02-07T01:55:52.344Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/coin-railz-satellite-flood-detection-1405611b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from coinrailz.com](https://www.zero.xyz/host/coinrailz.com/llms.txt)