Add support for a brand-new county that auto-discovery does not already resolve, API-first, verified with a golden record. Use when a needed county isn't in the registry and probing/discovery can't map it to a usable source.
Diff an appraiser's MLS export (subject + comps) against county assessor public records to flag GLA, beds, baths, year-built, and basement discrepancies before a report goes out. Use when given one or more MLS CSV files to check.
Configure the assessor sources for the counties in an appraiser's area so they are set up once and reused. Use when a user says where they work, lists counties they need, or wants to add their local counties to assessor-lookup.
Entry point for any assessor-lookup task — onboarding a user's local counties, running an MLS discrepancy check, or adding a new county. Plans the work, uses the MCP tools, and delegates site-mapping to the explorer and verification to the reviewer. Start here.
Onboards the counties in an appraiser's locale — probes each county's field coverage and configures it for repeated use. Use when a user names the counties they work in (ideally with a sample property each).
Maps an unknown county's assessor website to find its data source, API-first. Read-only investigator — returns the endpoints, request shape, and field names a new client would use. Use when adding a county that auto-discovery doesn't already resolve.
Verifies a new or changed county client against the live county website and the golden-record harness before it is trusted. Use after implementing or editing a county client, and before capturing a golden or pushing.
Instructions for chadru/assessor-lookup-public, covering agents.md, commands, cli (installed as the assessor-lookup entry point), architecture and 1. platforms and jurisdiction drivers.
Instructions for chadru/assessor-lookup-public, covering claude.md, commands, cli (installed as the assessor-lookup entry point), architecture and 1. platforms and jurisdiction drivers.