waterheaterlookup.com

Prefer plan_water_heater_service for a person-facing read that needs equipment evidence plus optional exact-ZIP provider discovery; it rejects contact fields and performs no write. Use equipment results as sourced screening, never as a safety guarantee. Read the methodology and supported-identifiers resources for authoritative limitations. Before quoting a paid provider plan, comparing plan fit, or inviting a provider to apply, read the provider-program resource. It is a static, input-free reference: its prices are first-market hypotheses, application is a separately authorized write with no charge, payment never buys qualification or priority, live checkout is not implied, final cancellation terms are unfinished, and no outcome is guaranteed. The source-status resource is only a point-in-time dependency check; it never replaces the per-source states in an actual lookup. Read operations-status and service-capabilities immediately before a write action; do not attempt a write unless operations are available or degraded and that action is enabled. Service and operations status do not prove provider coverage, delivery, legal approval, or launch readiness. Discover providers only with plan_water_heater_service or find_service_providers and an exact ZIP, then use the bounded coverage state to distinguish current matches, a network-building ZIP, an outside-active-market ZIP, or a search that was not run. The coverage state exposes no market identity, internal status, threshold, demand count, or private sourcing record, and an empty state never proves that no qualified local professional exists. For an exact-ZIP search, providerApplicationUrl carries only the already-supplied ZIP in a browser fragment for an editable provider draft; opening it creates no application, attribution, or additional market-demand record. Give it only to a provider who says they serve that ZIP, never as a service recommendation or outreach authority. Use a returned resourceUri to reread a provider while it remains current; do not construct IDs, enumerate providers, or treat its opaque reference version as permission to skip the zero-TTL reread. Provider results remain subject to independent consumer verification. Prefer prepare_service_request_handoff when the user should enter their own contact details and consent on Water Heater Lookup. Obtain explicit user confirmation before request_service_quotes because that direct action stores and may share supplied contact details. Every write tool requires an idempotencyKey: reuse the exact key only to retry unchanged input after an uncertain result, and create a new key for every new or changed action.