Locus Agent Capabilities

Use this skill to connect an agent to Locus when a place-based workflow needs local-government context: taxes, parcels, zoning, flood, environmental records, development activity, transportation projects, local policy, source coverage, or recurring monitoring. The fuller client guide is docs/AGENT_CAPABILITIES.md.

Locus returns awareness and verification steps, not a verdict. Do not score, rank, predict, screen, value, or label a person, property, block, or neighborhood as safe/unsafe.

What to remember first

• 51 national free tools are available with no payment or local coverage check; all 51 work directly from a geocodable US address (locus_pfas_occurrence resolves an address to serving system(s) via EPA's community water system service-area boundary layer, with per-boundary provenance/confidence, and still accepts explicit PWSIDs from locus_water_systems). The live free catalog currently exposes 83 tools total. Use national lanes for rural addresses too, including flood, storm, wildfire, soil, groundwater-monitoring wells, cleanup, toxic-release, underground storage tank / leaking-tank, drought, water, PFAS occurrence and non-UCMR multimedia records, sewer-overflow/CSO context, NEI facility emissions, broadband, wetland, terrain, air-quality, governing-district, housing/economic, nearby-place, geotagged Wikipedia place/history context, safely licensed nearby Wikimedia Commons area media metadata, public-utility, county Medicare-spending, electricity/transmission, and aggregate traffic-crash context. Mirror-backed EPA lanes return explicit not_ingested, partial, or unavailable component states instead of treating missing data as a favorable result. Traffic crashes use a national FARS fatal-only fallback, with richer registry-derived coverage in Chicago, Virginia, and North Carolina; source classes and partial subsets stay explicit, counts below 3 are suppressed, and proximity never establishes route exposure or future probability.
• National free tools cover all 50 states for geocodable US addresses. Local lanes are wired jurisdiction by jurisdiction and are growing. Always expect national context. Treat local parcel, zoning, permit, tax, and development-case depth as coverage-dependent.
• Start with locus_place_facts when lane availability says it is available. It is the one-call address bundle for supported parcel areas: parcel facts, FEMA flood zone, governing districts, transportation context, and tax context where wired.
• Use locus_lane_availability before paid calls. It maps national, local, varies, not-covered, and degraded lanes, then gives per-paid-tool buy recommendations.
• Treat partial trend coverage as a check-first signal. supported_partial trend places appear in lanes.varies with low paid substance; buy locus-local-trend-brief only when buyRecommendations[].substanceHere is medium or better. Thin exact-radius results can return a charged:false data-sufficiency diagnostic instead of a paid brief.
• The live paid catalog has 73 endpoints: 23 native paid tools plus 50 promoted dual-rail routes over focused free tools. Most native single-call tools list at $0.05 to $0.10 USDC; surrounding-area analysis is $0.10, its report upgrade $0.15, local fiscal context is $0.05, locus-property-flyer is $0.49, and locus-place-report-batch is $0.25 per 3-50 address async job. Prefer free /tools/call for dual-rail lookups; prefer one composite over many micros (see product ladder). Call the live paid catalog or locus_lane_availability for current priceUsdc, then read the x402 challenge for exact price, chain, recipient, and schema before payment.

Quick connect

Install this skill: