Curb Insights — what buyers asked the talking yard sign
Sign in with a staff account to view Curb Insights.
The Curb Insights pack isn’t applied yet — apply db/2026-07-29_1402_curb-insights-staged.sql, then reload.
Collection is dark. config.curb_insights is {"enabled": false}, so no events are being recorded and the weekly digest is a no-op. The houses still answer buyers exactly as they do today — flip the switch to start counting.
The curb rail itself is dark. config.curb is off, so no house is answering and nothing new can be recorded.
—
What buyers asked about
One question can touch several topics — each topic it mentions gets a vote, but the question itself counts once under Questions.
What the seller would receive
Composed from the same seven-day numbers mcp_curb_insights_digest() uses, so this preview and the real Monday email cannot disagree. Nothing is sent from this page.
PURE · to the seller
—
—
Queued as one pure_comms_log row and brand-carded by the pure-comms drainer · one send per listing per week.
Aggregate topics only. pure_curb_events holds five columns — id, slug, kind, topic, ts. No name, contact, IP, or question text is recorded anywhere on this rail, so no report can ever leak one. A buyer who books a showing reaches the agent through the consented lead rail, exactly as before.
Pure MLS Tech · Acquisto Real Estate · Curb Insights over mcp_curb_insights / mcp_curb_insights_list · weekly composer mcp_curb_insights_digest (dark until flipped) ·