Evaluation intake

Request a new buyer brief.

Paste a listing URL or address, add any buyer notes, and submit it into the public evaluation queue. Today this uses GitHub Issues; direct no-GitHub-submit support is scaffolded for the next backend step.

Submit A House

Public note: this flow creates a GitHub issue in a public repository. Do not include private financing limits, personal identity details, or negotiation strategy unless you want them public.

Redfin, Zillow, Realtor, MLS link, or another public listing URL.
Use the full address if you have it.
Optional, but useful if the listing site is stale or gated.

Request Ready

Open the GitHub issue link below, review the text, and submit it. That issue becomes the public queue item for evaluation and publishing.

Open GitHub issue

Check request status

How A Request Becomes A Page

  1. The form creates a public GitHub issue with the listing URL, address, and notes.
  2. The issue is acknowledged and labeled by the repository workflow.
  3. The home-evaluation skill is run against the request, using current listing, market, school, safety, tax, permit, and title sources where available.
  4. The generated brief is added as an HTML page under `homes/` and listed in `data/homes.json`.
  5. GitHub Pages republishes the site automatically from the `main` branch.

Why GitHub Still Asks You To Submit

GitHub Pages is a static host. It cannot safely keep a private GitHub token in the browser, so the current public-safe flow sends you to GitHub to confirm the issue. The repo now includes a small backend scaffold that can remove that extra step once an endpoint with a private token is deployed.