# Locus: PFAS Occurrence Scan

> Locus: PFAS Occurrence Scan 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).

Scans public records for PFAS (per- and polyfluoroalkyl substances) occurrence data associated with a property address, coordinates, or public water system IDs.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-pfas-occurrence
- 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-pfas-occurrence-scan-fb417589
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6_tkAQ_xvTTiwsrSp0kAo

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-pfas-occurrence-scan-fb417589 -d '<json body>'
```

Example prompt: Can you run a PFAS occurrence scan on 742 Evergreen Terrace, Springfield, IL to check what public water records exist, what's been answered, and what still needs verification before I make an offer on the property?

## When to prefer this

Use this endpoint when you need a fast, low-cost PFAS-specific public records scan for a property or water system — particularly during real estate due diligence, environmental site assessments, or when advising on drinking water safety. It is optimized for PFAS occurrence data specifically, unlike broader property or environmental report endpoints. At $0.01 per call it is suitable for bulk screening across multiple addresses.

## Known failure modes

- Invalid or unrecognized address returns empty records array with coverage caveats
- PWSID not found in public databases returns empty records with explanation
- Missing all location inputs (no address, coordinates, or pwsids) causes validation error
- Coordinates out of supported geographic range return no records
- Public record data may be stale or incomplete, indicated via caveats field

## How this service works

EPA UCMR 5 PFAS results for an address or explicit PWSIDs. Perfect for: 'PFAS results for this address', 'was this utility tested for PFAS'. Addresses resolve via EPA service-area boundaries (point-in-polygon) with per-boundary provenance and confidence (provider vs machine-modeled); containment is evidence, not proof. Detection and non-detect counts stay distinct; lithium excluded. Entry-point samples, not a tap; no safe/unsafe verdict. Charge-free when out of coverage or unresolved.

## Output

Returns a JSON artifact with a scan ID, timestamp, list of PFAS occurrence records pulled from public sources, any caveats about data coverage or reliability, and guidance on which questions remain open and what to verify next.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "pwsids": {
   "type": "array",
   "items": {
    "type": "string",
    "pattern": "^[A-Z0-9]{4,24}$"
   },
   "maxItems": 10,
   "minItems": 1
  },
  "address": {
   "type": "string",
   "maxLength": 200,
   "minLength": 5
  },
  "latitude": {
   "type": "number",
   "maximum": 90,
   "minimum": -90
  },
  "longitude": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  }
 }
}
```

## 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-pfas-occurrence-scan-fb417589/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)