# HALOWERK Land Compare – Dominant Land-Cover Class (Two-Point)

> HALOWERK Land Compare – Dominant Land-Cover Class (Two-Point) is a paid API for AI agents from landvergleich.halowerk.com, paid per call via x402, $0.006/call, status unknown (last checked 2026-09-13).

Compares the dominant land-cover class at exactly two European coordinates and returns the signed difference and which location wins.

## Facts

- Endpoint: POST https://landvergleich.halowerk.com/v1/compare-two-landcover-class
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-land-compare-dominant-land-cover-class-two-point-91a599c9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tx4I3bcxVTWPuoJK03O42

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 halowerk-land-compare-dominant-land-cover-class-two-point-91a599c9 -d '<json body>'
```

Example prompt: Compare the dominant land-cover class between Paris (48.8566, 2.3522) and Munich (48.1351, 11.5820) — which one has a different primary land-cover type and what's the difference?

## When to prefer this

Use this endpoint when you need a direct pairwise comparison of dominant land-cover classification between exactly two European locations. Prefer it over single-point lookup services when the user explicitly wants to know which of two sites differs in land-cover type or needs a signed difference. Choose sibling endpoints for built-up share, water/wetland, terrain ruggedness, or soil properties; use this one specifically for dominant land-cover class.

## Known failure modes

- Coordinates outside European coverage bounds (latitude 34–72.5, longitude -31.5–40.5) return validation error
- Fewer or more than exactly two locations provided causes schema rejection
- Invalid WGS84 coordinate format returns parsing error
- Ambiguous or tied dominant class may result in no clear winner being reported
- Network timeout or service unavailability returns HTTP 5xx

## How this service works

Measures dominant land-cover class for exactly two European coordinates with one method and reports the signed difference and winner where meaningful.

## Output

Returns the dominant land-cover class for each of the two input European coordinates, the signed difference between the two values, and an indication of which location 'wins' (has the higher or more significant class value) where meaningful.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "locations": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "longitude",
     "latitude"
    ],
    "properties": {
     "name": {
      "type": "string",
      "maxLength": 60,
      "minLength": 1
     },
     "latitude": {
      "type": "number",
      "maximum": 72.5,
      "minimum": 34,
      "description": "WGS84 latitude inside the published European coverage."
     },
     "longitude": {
      "type": "number",
      "maximum": 40.5,
      "minimum": -31.5,
      "description": "WGS84 longitude inside the published European coverage."
     }
    },
    "additionalProperties": false
   },
   "maxItems": 2,
   "minItems": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-land-compare-dominant-land-cover-class-two-point-91a599c9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from landvergleich.halowerk.com](https://www.zero.xyz/host/landvergleich.halowerk.com/llms.txt)
