# lilambd Hazard Stations Endpoint

> lilambd Hazard Stations Endpoint 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 data for a specific hazard station by ID from the lilambd crossing platform

## Facts

- Endpoint: GET https://api.lilambd.com/hazard/stations/%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-stations-endpoint-b9989815
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ICPixCpwoCP8OsGE-k6AV

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-stations-endpoint-b9989815
```

Example prompt: Can you fetch the data for hazard station 42 from the lilambd crossing?

## When to prefer this

Use this endpoint when you need to look up a specific hazard station by its unique identifier on the lilambd crossing platform. It is the only known endpoint for retrieving per-station data from this experimental, creative computation service. Prefer it when your use case involves querying named or numbered stations within the lilambd ecosystem.

## Known failure modes

- Station ID not found — returns 404 or empty response
- Invalid or missing ID in path — returns 400 or error JSON
- Payment not completed via x402 protocol — returns 402 Payment Required
- API server unavailable — returns 5xx error
- Ambiguous or malformed JSON response due to undefined schema

## How this service works

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

## Output

Returns JSON data describing the specified hazard station, potentially including its current state, properties, and any associated crossing or computation metadata. The exact shape of the response is loosely typed JSON.

## 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-stations-endpoint-b9989815/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)