# locus.report EPA NEI Emissions Nearby

> locus.report EPA NEI Emissions Nearby is a paid API for AI agents from locus.report, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-13).

Returns EPA National Emissions Inventory facility rows and per-pollutant tonnage estimates near a given address, ranked by distance.

## Facts

- Endpoint: POST https://locus.report/api/locus-nei-emissions-nearby?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/locus-report-epa-nei-emissions-nearby-b24a52e9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_22XLJFipOQJjRNuwTGRZI

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-report-epa-nei-emissions-nearby-b24a52e9 -d '<json body>'
```

Example prompt: Can you pull the EPA National Emissions Inventory data for facilities within 3,000 meters of 1600 Pennsylvania Ave NW, Washington DC — give me the full facility-pollutant matrix so I can see per-pollutant tonnage for each nearby emitter?

## When to prefer this

Use this endpoint when you need distance-ranked, per-pollutant emissions tonnage from the EPA National Emissions Inventory for facilities near a specific US address or coordinate. It is the right choice for environmental due diligence, site screening, and industrial context research. Prefer it over ambient air quality or monitoring endpoints when you need regulatory inventory data rather than real-time sensor readings, health risk scores, or exposure estimates. The full detailLevel option is valuable when you need a complete facility-pollutant matrix for a given area.

## Known failure modes

- No facilities found within the specified radius — returns empty result set with no charge
- Address geocoding fails — returns error if address cannot be resolved to coordinates
- Radius out of bounds (below 500m or above 25,000m) — validation error
- Invalid or missing required address/coordinate input — schema validation error
- reportingYear must be 2023 (const constraint) — other years rejected
- Service unavailable or upstream EPA data issue — HTTP 5xx error

## How this service works

EPA National Emissions Inventory facility and pollutant rows near an address for agents reviewing distance-ranked tonnage. Bounded summary or detailLevel=full facility-pollutant matrix. Periodic inventory estimates, not monitoring, exposure, or a burden score. Charge-free when no facility rows resolve.

## Output

A distance-ranked list of EPA NEI facility rows near the input address, each with facility name, pollutant name, reported tonnage, and distance. At summary detailLevel, the response is bounded; at full detailLevel, the complete facility-pollutant matrix is returned. Includes only periodic inventory estimates (not real-time monitoring or ambient concentration data). No charge is applied if no facility rows resolve.

## 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
  },
  "detailLevel": {
   "enum": [
    "summary",
    "full"
   ],
   "type": "string",
   "default": "summary"
  },
  "radiusMeters": {
   "type": "integer",
   "maximum": 25000,
   "minimum": 500
  },
  "reportingYear": {
   "type": "number",
   "const": 2023
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/locus-report-epa-nei-emissions-nearby-b24a52e9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from locus.report](https://www.zero.xyz/host/locus.report/llms.txt)