# GNSS Degradation Estimator

> GNSS Degradation Estimator is a paid API for AI agents from natur.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-14).

Estimates the likelihood and magnitude of satellite navigation degradation from ionospheric delay errors and geomagnetic activity, distinguishing between single-frequency and dual-frequency receiver impacts.

## Facts

- Endpoint: POST https://natur.halowerk.com/v1/gnss-degradation
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gnss-degradation-estimator-23d0c37f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mR_YrUXmAF-GO9ELLwYlT

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 gnss-degradation-estimator-23d0c37f -d '<json body>'
```

Example prompt: What's the risk of GNSS position errors at my survey site in Munich right now — I'm using a single-frequency receiver and want to know how bad the ionospheric delay could be given current geomagnetic activity?

## When to prefer this

Choose this endpoint when you need to distinguish between ionospheric and geomagnetic causes of GNSS degradation rather than a single aggregate score, particularly when the application involves single-frequency receivers where silent positional drift is a safety or accuracy concern. It is especially valuable for pre-mission checks for surveying, drone operations, or autonomous navigation where undetected position errors are dangerous. Prefer it over generic space weather APIs when the output must be actionable for GNSS operators specifically.

## Known failure modes

- Missing or invalid coordinates return a 400 error
- Unknown or unsupported receiver type enum causes validation failure
- Geomagnetic data unavailable for requested time window returns partial result or 503
- Requests for future timestamps beyond forecast horizon return uncertainty-flagged estimates
- Rate limiting at high request volume returns 429

## How this service works

Estimates how likely satellite navigation is to be degraded, keeping two distinct mechanisms apart. Ionospheric delay error rises with geomagnetic activity, affects single-frequency receivers far more than dual-frequency ones, and shifts the computed position without any obvious sign that something is wrong.

## Output

Returns a structured estimate of GNSS degradation likelihood broken down by mechanism: ionospheric delay error (scaled by receiver type — significantly higher for single-frequency vs dual-frequency) and geomagnetic activity contribution. Includes a predicted positional offset magnitude, a risk level indicator, and flags whether degradation would be detectable or silent to the receiver.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "lat": {
   "type": "number",
   "maximum": 90,
   "minimum": -90,
   "description": "Latitude of operation. Decisive: the same activity means different things at 70 and at 40 degrees."
  },
  "lon": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  },
  "receiver": {
   "enum": [
    "single_frequency",
    "dual_frequency",
    "sbas_augmented",
    "rtk"
   ],
   "type": "string",
   "default": "single_frequency"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gnss-degradation-estimator-23d0c37f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from natur.halowerk.com](https://www.zero.xyz/host/natur.halowerk.com/llms.txt)