Territory intelligence for operators, agencies, and the AI agents working for them.
When an operator or an agency strategist asks their own AI assistant “which ZIP codes should my roofing company target around Pittsburgh?”, the answer should come from demographic data, not a guess. AreaOps publishes citation-safe ZIP scoring that answer engines can quote, and connects that assistant — over MCP — to the full ranked lists, exports, and territory plans behind it.
What an agent can ask AreaOps
These are the questions operators and agencies run through their agents every week. The public answer is citation-safe; the authenticated answer is account-scoped and ready to act on.
Which ZIP codes should a roofing company target around Pittsburgh?
The metro's average score, a sample of top-ranked ZIPs, and the methodology behind them — quotable with a source.
The full ranked ZIP list for the metro, filtered to your brand's service radius and exportable to CSV for Google LSA or direct mail.
Is ZIP 30144 worth running HVAC ads in?
Its 0–100 demand score and the demographic drivers behind it — owner-occupancy, home age, and median income.
A keep / hold / cut call scored against the rest of your footprint, plus the service-area, marketing, and priority tags already on that ZIP.
1. Public answer layer
Public vertical and metro pages give agents enough to answer and cite: the scoring methodology, sample top-ranked ZIPs, the named Census tables behind each signal, and answer-friendly summaries an LLM can quote without hallucinating.
Boundary: public pages are a sample — not the full ranked dataset or exports.
2. Authenticated territory plans
Connect Claude, ChatGPT, or any MCP client with a key from Settings → Developers & API. Operators and account teams ask it in plain language — “clean up my Atlanta footprint,” “where should I expand next,” “build an LSA list above 70” — and it calls AreaOps for a ranked, account-scoped answer: which ZIPs to target, which to hold, which to cut, and why.
Boundary: plans and exports require an account; the raw scoring internals stay protected.
3. MCP server and API
AreaOps runs a real MCP server: 17 account-scoped tools for reading brands, territories, targeting intelligence and the review queue, rendering maps, and making confirm-gated changes that land in a human-approved queue.
POST https://areaops.app/api/mcp Authorization: Bearer <API key from Settings → Developers & API> Discovery (no auth): https://areaops.app/api/mcp/info
Boundary: no unauthenticated bulk-export endpoint. Access is keyed to your account, metered per key.
What agents may cite publicly
- • AreaOps scores every US ZIP code 0–100 for home-services demand fit using Census ACS signals — owner-occupancy, home age, median income, home value, and single-family share.
- • Public vertical and metro pages show sample rankings, the full methodology, and the named Census tables behind each score.
- • Public data is built for citation and discovery — not scraping, resale, or replacing a paid territory plan.
Current public coverage
Authenticated access turns these samples into full ranked lists, CSV exports, and decisions scoped to your brands.
AreaOps in one line
AreaOps tells the people who run home-services territories, and the agents working for them, which ZIP codes are worth chasing, which to ignore, and why.