# Locus: Traffic Crash Context

> Locus: Traffic Crash Context is a paid API for AI agents from api.locus.report, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Retrieves traffic crash records near a given address or coordinates across configurable radii and lookback periods to inform property due diligence.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-traffic-crash-context
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/locus-traffic-crash-context-d3bd07d6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EOu-J9uOSzNcZamihdpGs

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 locus-traffic-crash-context-d3bd07d6 -d '<json body>'
```

Example prompt: Can you pull the Locus traffic crash context for 742 Evergreen Terrace, Springfield — check within 200, 500, and 1000 meters, looking back 5 years?

## When to prefer this

Choose this endpoint when you need geospatially bounded, radius-configurable traffic crash history around a specific address or coordinate pair as part of property research or location risk assessment. It is specifically designed for pre-decision due diligence workflows and surfaces coverage gaps explicitly, making it more useful than generic public-record scrapers when you need to know not just what data exists but what remains unverified.

## Known failure modes

- Address not parseable or too short — validation error returned
- Coordinates out of valid range (-90 to 90 lat, -180 to 180 lon) — schema rejection
- No crash records found for location — empty records array with caveats
- Payment not completed (x402 flow not resolved) — 402 response blocking data return
- Radii values outside 200–1000m range or more than 3 items — input validation failure
- Lookback years outside 1–10 range — validation error

## How this service works

Aggregate traffic-crash context near an address. Perfect for: 'traffic crashes near this property', 'pedestrian or bicycle crash counts nearby', 'fatal crash context around an address'. Returns small-cell-suppressed official aggregates with explicit severity classes: local sources where wired plus nationwide FARS fatal-only fallback. Not route exposure, a forecast, score, or place verdict. Charge-free unless at least one count survives small-cell suppression.

## Output

Returns a JSON object with a record ID, a list of local traffic crash records near the queried location, caveats about data coverage and completeness, and a timestamp indicating when the report was generated. Open questions and gaps in public-record coverage are flagged for follow-up.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "maxLength": 200,
   "minLength": 5
  },
  "latitude": {
   "type": "number",
   "maximum": 90,
   "minimum": -90
  },
  "longitude": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  },
  "radiiMeters": {
   "type": "array",
   "items": {
    "type": "integer",
    "maximum": 1000,
    "minimum": 200
   },
   "default": [
    200,
    500,
    1000
   ],
   "maxItems": 3,
   "minItems": 1
  },
  "lookbackYears": {
   "type": "integer",
   "default": 3,
   "maximum": 10,
   "minimum": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "locus_example",
  "caveats": [
   "Example artifact; not live data."
  ],
  "records": [],
  "generatedAt": "2026-01-01T00:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/locus-traffic-crash-context-d3bd07d6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.locus.report](https://www.zero.xyz/host/api.locus.report/llms.txt)