Skip to content

Chrome Extension — Relive Overlay

Retired

This extension and its dedicated backend were retired and are no longer deployed against anything live. This page documents them for historical/reference purposes only. See History & Migrations for migration context. Nothing on this page is a live recommendation to install or run this extension in production.

What it did

The Relive Overlay was a Chrome extension that injected UI onto a partner's ("Relive") property-search web app, overlaying this project's own building intelligence side-by-side with the partner's data, live, in-page.

Behavior

List view. The extension drew badges on each result row:

  • A solid pill showing an extracted commission figure, when known.
  • An outlined badge showing the building's lead tier, when the building was in the universe but commission wasn't known yet.
  • A "not matched" badge otherwise.

A floating panel summarized coverage: the partner's building count versus this project's, coverage share, buildings only this project had, and fill rates for commission, email, and phone.

Detail view. A two-level panel:

  • A building overview — headline average rent, unit/floorplan counts, a commission comparison line, a deduplicated photo gallery, lead tier/PM, amenity chips, and a floorplan list.
  • Drilling into a floorplan — photo, beds/baths/sqft, rent range, availability, and scraped unit rows.

Images were always hotlinked from their original hosts, never re-hosted.

Coverage was limited to three metros — Chicago, Atlanta, and Denver. Other markets showed "no coverage yet."

Architecture

A content script rendered the badges and panel on the partner's page. A background service worker acted as a fetch proxy, because the partner's page set a Content-Security-Policy that blocked the extension's content script from calling an external API directly (a background service worker isn't subject to the page's CSP).

The backend matched the partner's property records to this project's buildings by normalized address (ZIP + house number + street-token similarity), falling back to a normalized building-name match.

Backend

A dedicated Vercel project — part of the now-retired extension-api/ — served the production/hosted API for installed extensions, authenticated by a per-client API key header, reading comparison tables in the warehouse (see Warehouse Schema).

A companion local script could run the same API locally on a developer machine for testing, backed directly by local data files.

For how this fit into the platform's broader system boundaries before retirement, see Architecture Overview.

Why it was retired

Needs verification

The specific reason for retirement isn't captured in the material this page was generated from. If this context matters — for example, when deciding whether to revive a similar integration later — confirm with the team rather than assuming.