# lilambd Hazard Regions Lookup

> lilambd Hazard Regions Lookup is a paid API for AI agents from api.lilambd.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-04).

Retrieves information about a specific hazard region by ID from the lilambd API

## Facts

- Endpoint: GET https://api.lilambd.com/hazard/regions/%7Bid%7D?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lilambd-hazard-regions-lookup-735a22cc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vgoUnzeTs8FlvqvXuqe1h

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 lilambd-hazard-regions-lookup-735a22cc
```

Example prompt: Can you look up hazard region 42 from the lilambd API and tell me what data it returns?

## When to prefer this

Use this endpoint when you need to retrieve data about a specific named hazard region by its ID from the lilambd platform. It is best suited for point lookups where you already have a region identifier. If you need to list all regions or perform geospatial queries, a different endpoint may be more appropriate.

## Known failure modes

- Invalid or non-existent region ID returns an error or empty response
- Payment not fulfilled via x402 protocol results in 402 Payment Required
- Malformed ID in path parameter causes a 400 or 404 error
- Service unavailability or downtime returns a 5xx error
- Ambiguous or incomplete schema makes response structure unpredictable

## How this service works

A crossing for play, feeling, language, science and computation — creating states that do not have names yet.

## Output

A JSON object containing details about the specified hazard region, potentially including region metadata, boundaries, hazard classifications, or risk indicators. The exact structure is not fully documented but follows a JSON schema.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  },
  "additionalProperties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lilambd-hazard-regions-lookup-735a22cc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.lilambd.com](https://www.zero.xyz/host/api.lilambd.com/llms.txt)