Real-estate deal watchlist.Real-estate deal watchlist.Real-estate deal watchlist.Real-estate deal watchlist.

Every real-estate investor has the same starting point: five saved searches across three platforms, plus a Gmail label full of wholesaler blasts. Nobody has time to read them all. This is the watchlist that reads them for you.

One inbox on Inbin, 4 newsletter or alert subscriptions pointed at it. Every email that lands gets parsed against your schema.

One PUT to /v1/schemas. Inbin extracts these fields from every future email. Hallucination guard drops anything the model invented.

{
  "extract": {
    "listings": {
      "type": "array",
      "items": {
        "address":       { "type": "string", "required": true },
        "city":          { "type": "string", "required": true },
        "state":         { "type": "string", "pattern": "^[A-Z]{2}$", "required": true },
        "zip":           { "type": "string", "pattern": "^\\d{5}$" },
        "list_price_usd":{ "type": "number", "required": true },
        "beds":          { "type": "number", "nullable": true },
        "baths":         { "type": "number", "nullable": true },
        "sqft":          { "type": "number", "nullable": true },
        "source":        { "type": "string" }
      }
    }
  }
}

1. 01
   Create the inbox

   POST /v1/inboxes returns a permanent forwarding address like abc123@in.inbin.dev. Use it everywhere you subscribe.
2. 02
   Point the sources at it

   Enter that address directly in each source’s notification settings or signup form (Redfin, MLS forwards, etc.). If a source sends a verification email, Inbin detects it and shows you the link or code to confirm. For mail that only goes to your own mailbox, a Gmail forwarding filter works as the fallback.
3. 03
   Declare the schema

   Paste the JSON above. Inbin creates version 1 and tracks every future version; any event can be re-extracted against the new shape with one call.
4. 04
   Consume the events

   Every parsed email hits your webhook as HMAC-signed JSON. Or read them via GET /v1/events. Or query them from an agent via MCP.

vs. PropStream: $99+ / mo.

Every product listed above exists because the underlying data was hard to get. Newsletters give you that data for free. Inbin structures it.

Also worth building