Read first-party assistant blockers or quote progress for a homeowners or umbrella intake.

Returns a line-aware follow-up payload for a consumer-prefill homeowners or umbrella intake uid. Authenticate with Authorization: Bearer <intake_access_token> from the latest consumer-prefill follow-up response. Before submission, this exposes the one-time review checkpoint and any remaining missing or estimated values, and the agent should say explicitly that the application is not submitted yet before asking for anything else. Present gathered details, review facts, and remaining items as short labeled bullets or sections rather than a prose paragraph. If any shown value is estimated, mark each estimated bullet label or value with *, include the short note * = estimated once above and once below the list, and do not prefix every estimated line with [Estimated]. For homeowners, treat those missing fields as a behind-the-scenes enrichment backlog rather than a first-turn questionnaire, and keep recovering context-backed answers until the payload is ready for one review card. After submission, homeowners issue payloads can stay in pending_quotes or waiting_on_carrier for up to 48 hours; keep polling and use the returned notification-channel details to keep the registered customer email on file. When the homeowners carrier or chat thread needs another answer, Coverage Cat returns conversation.messages, conversation.reply_pending, and conversation.reply_to_message_id so the assistant can answer the follow-up in chat with the patch route instead of breaking out to delegated tools. Homeowners quoted offers include selection_token, the select step can return a purchase_preview plus preview_token, and any carrier payment or signing link will go directly to the customer's email on file rather than a first-party payment endpoint. For umbrella, Coverage Cat may keep status: needs_more_info while still returning a staged review preview plus a bundled next_question for the final shopper-owned review turn, so the assistant can collect details such as full name, email, phone, full address, birthday, marital status, driver's license state, driver's license number, net worth, and any corrections in one message rather than one field at a time. Once quotes are ready, selection_guidance.same_reply_requirements can preview small carrier-specific bind questions for a chosen offer so the shopper can answer those in the same selection reply instead of opening a second turn. If the staged review shows a wrong estimated umbrella count from context, patch the canonical umbrella_details.* count field before you show the final review. Coverage Cat will not resume or expose a prior consumer umbrella draft based on email alone. Continue an existing consumer draft only through the issued uid plus the current hidden MCP session or latest intake_access_token handoff. If the shopper gives a birthday in MM-DD-YYYY form, normalize it to YYYY-MM-DD before the patch call. After submission, umbrella issue payloads expose quote progress, structured umbrella offers with selection_token, detailed post-choose umbrella states, payment_setup details once secure Stripe collection is prepared, and a refreshed intake_access_token for the next direct follow-up call. For Monoline and Markel, once declarations uploads are on file, documents_pending_review usually advances to payment_needed with a secure payment_url within about 5-10 minutes while declarations verification continues in parallel.