# HALOWERK Land Compare – Built-Up Share (Two Locations)

> HALOWERK Land Compare – Built-Up Share (Two Locations) 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 the built-up land share at exactly two European coordinates and returns the signed difference and winner between them.

## Facts

- Endpoint: POST https://landvergleich.halowerk.com/v1/compare-two-built-up-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-built-up-share-two-locations-9bf823ef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Q-Bz7-KYiQzB-fPGofiid

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-built-up-share-two-locations-9bf823ef -d '<json body>'
```

Example prompt: Compare the built-up land share between central Paris at 48.8566, 2.3522 and central Amsterdam at 52.3676, 4.9041 — tell me which one is more urbanized and by how much.

## When to prefer this

Use this endpoint when you need a precise, method-consistent pairwise comparison of built-up land share between exactly two European locations. It is purpose-built for two-point comparisons and returns a direct signed difference and winner, making it ideal for site selection, urban analysis, or development assessment workflows where a head-to-head answer is needed. For ranking more than two sites, use the sibling multi-site ranking endpoint instead.

## Known failure modes

- Coordinates outside the European coverage bounding box (lat 34–72.5, lon -31.5–40.5) will be rejected
- Providing fewer or more than exactly two location objects returns a validation error
- Invalid or non-numeric latitude/longitude values cause a bad request error
- Locations that are identical or nearly identical may produce a near-zero difference with no clear winner
- Payment failure or insufficient USDC balance prevents the call from completing

## How this service works

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

## Output

Returns the built-up land share percentage for each of the two input coordinates, the signed numerical difference between them, and an indication of which location has the higher built-up share (the 'winner'), based on a consistent remote-sensing method applied across European coverage.

## 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-built-up-share-two-locations-9bf823ef/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)