# HALOWERK Land Compare – Grassland Share Two-Point Comparison

> HALOWERK Land Compare – Grassland Share Two-Point Comparison 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-15).

Measures and compares grassland share (as a fraction) at exactly two European coordinates, returning the signed difference and identifying which location has more grassland.

## Facts

- Endpoint: POST https://landvergleich.halowerk.com/v1/compare-two-grassland-share
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-land-compare-grassland-share-two-point-comparison-1c82b816
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UTxkg1uSp1pIttwULooQ9

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-grassland-share-two-point-comparison-1c82b816 -d '<json body>'
```

Example prompt: Compare the grassland share between these two locations in Europe: a site near Munich at latitude 48.15, longitude 11.58, and one near Paris at latitude 48.85, longitude 2.35 — which one has more grassland and by how much?

## When to prefer this

Use this endpoint when you need a direct pairwise comparison of grassland share between exactly two European locations and want both the raw values and the signed difference in a single call. Prefer it over a general land-cover endpoint when grassland specifically is the metric of interest, and over a multi-site ranking endpoint when exactly two points are being evaluated.

## Known failure modes

- Coordinates outside European coverage bounds (latitude 34–72.5°N, longitude -31.5–40.5°E) return a validation error
- Fewer or more than exactly two location objects cause a schema validation failure
- Invalid or non-numeric latitude/longitude values return a parsing error
- Payment not provided or insufficient USDC causes a 402 response
- Locations too close together may yield a near-zero difference with no clear winner

## How this service works

Measures grassland share for exactly two European coordinates with one method and reports the signed difference and winner where meaningful.

## Output

Returns the grassland share fraction for each of the two input coordinates, the signed numeric difference between them (location A minus location B), and an indication of which location 'wins' (has more grassland) where the difference is 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-grassland-share-two-point-comparison-1c82b816/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)