# Service area

Last updated: 2026-03-31

## Source of truth for “open” Wisconsin counties

**Market configuration** decides which Wisconsin counties Zwivio treats as **open**. The public site reflects that through a **machine-readable coverage projection**. Agents that can call HTTP may use **`GET /public/coverage?state=WI`** to read the same county-level signal the product uses. It can change without a separate marketing or web copy update.

**Public `/locations/wi` pages** list counties that are open under that coverage **and** have supported public location pages (county/city naming, slugs, and ZIP context for homeowners). **Coverage from market configuration is the authority for which counties are open**, not geography copy alone.

## “Listed” vs depth and availability

- **Listed / open county:** The county is in live public coverage and has a supported public location presence so `/locations/wi/{county}` and related city routes can resolve where applicable.
- **Depth and timing:** Assignment still depends on contractor availability, routability, routing policy, after-hours handling, and operations. **Listing a county or city is not a promise of same-day or on-demand contractor depth.**

## Do not overclaim

- Do not claim broader Wisconsin coverage than **`GET /public/coverage`** (or the same list reflected on **`/locations/wi`** and **`/llm-info`**) for “open counties.”
- Do not equate “this county appears on the site” with “contractors are always available there on demand.”

## Where to look without an API

- **`/locations/wi`**: Wisconsin hub aligned with public coverage.
- **`/llm-info`**: Index with county and example city chips aligned with the public site.
- This file and **`/llm/urls.md`**: context and URL patterns.

If an agent cannot call APIs, rely on **`/locations/wi`**, **`/llm-info`**, and this file. Do not infer open counties from generic marketing copy alone.