Listing

Account stage — register a new beycome user (POST /auth/register). Use when the owner has no account yet. beycome is passwordless: registering automatically emails the user a 6-digit sign-in code, so the next step is `beycome_signin_verify` with that code — do NOT call `beycome_signin_start` after signup, the code is already on its way. If the email is already registered, this still just send

Account stage — send a one-time sign-in code (POST /auth/check-email). beycome is passwordless — never ask the user for a password. This emails the user a 6-digit code (a second, different code also goes out by SMS; either one works). Ask the user for the code they received, then exchange it for the access_token with `beycome_signin_verify`. Read the response body, not the HTTP status — th

Account stage — exchange the one-time code for the access_token (POST /auth/validate-code). The gateway to the listing flow. Call after `beycome_signin_start` or `beycome_signup` (both send the code) with the 6-digit code the user received. On success the Bearer token is at ``data.data.access_token`` (``expires_in`` gives its lifetime in seconds — tokens are long-lived, so mid-session expiry

Discovery stage — is this state served by beycome MLS? (GET /mls/is-covered). No account or prop_id needed. Use before listing to confirm beycome operates in the property's state; ``is_active: true`` means covered. If not covered, the listing flow does not apply.

Discovery stage — estimate a property's SALE value (beycome CMA + Zillow Zestimate). No account or prop_id needed. Returns both estimates plus suggested pricing strategies (fast / balanced / max). Use during discovery to set a list price; pair with `beycome_comps`. For rental inquiries, use `beycome_rental_estimate` instead.

Discovery stage — estimate a property's monthly RENT (POST /gemini-estimate). No account or prop_id needed. Pairs with `beycome_estimate`, but this tool is SPECIFICALLY for rental estimates: use it ONLY for rental inquiries or for properties that have a unit number. For sale-price estimates, use `beycome_estimate`. Returns ``rentEstimate`` (e.g. "$2,600"), ``rentEstimateRange`` (e.g. "$2,400 -

Discovery stage — sold comparable listings near a location (GET /comps). No account or prop_id needed. Supports price / beds / baths / area / lot / type filters. Use during discovery to support pricing alongside `beycome_estimate`. Slow endpoint: a cold query can take up to ~1 minute to respond — this is normal, you can always retry the call if it times out. Photo URL and listing-link fields

Questionnaire stage — mint a pre-authorized link to the MLS questionnaire form (POST /api/mls/questionnaire-link). Requires a PAID listing (premium active, Flat/Yes) — whether the user just paid on the submit-property page (`beycome_submit_property_link`) or already had a paid listing with the questionnaire still pending. Returns a pre-authorized link (expires in 7 days) — this tool only ha

Listing-creation stage — mint a pre-authorized link to the submit-property page (POST /api/mls/submit-property-link). Call AFTER signing in (`beycome_signin_verify`). User-scoped — no prop_id exists yet. Returns a pre-authorized link (expires in 7 days) — this tool only hands back the URL; the listing is created in the browser, with no login step. Present the URL and tell the user that on t

Recovery stage — the signed-in user's properties (GET /properties). Token-scoped RESO list endpoint on the normal api base. Two main uses: - After the user finishes the submit-property page (`beycome_submit_property_link`): find the newly created listing (typically the newest entry), CONFIRM the address with the user, then use its id as ``prop_id`` for `beycome_questionnaire_link`

Post-publish stage — offers received on the owner's listings (GET /offers). Used once a listing is live. Requires ``access_token``. Returns a paginated list (20 per page; pass ``page`` to advance) of every offer across all of the signed-in user's listings — each entry is the full offer record (buyer, price, contingencies, dates, status). Read-only. There is no server-side ``prop_id`` filter;

Post-publish stage — calendar of showings, open houses, and offer deadlines (GET /calendar/events). Used once a listing is live. The API requires the date range, so it defaults to today → +90 days when omitted (``from_date`` / ``to_date`` are ``YYYY-MM-DD``, with ``to_date`` on or after ``from_date``). ``prop_id`` filters to one listing; omit it for every listing the user owns. The response

Post-publish stage — read the owner's buyer/inquiry messages (GET /messages). Read-only. Requires ``access_token``. Two modes: - Omit ``thread`` → lists the ~20 most recent conversations, newest first, one row per thread (the latest message in each). Useful fields per row: ``address``, ``prop_id``, ``prop_status``, ``msg`` (latest text), ``subject``, ``requested_by`` / ``email``

Post-publish stage — reply to a buyer/inquiry message (POST /messages/reply). Sends a real message and queues a real email notification to the recipient, so the text you send is final — treat this as a live send, not a draft. ALWAYS improve the user's drafted reply before sending: fix grammar, spelling, punctuation, capitalization, and formatting, and tighten wording for a clear, professiona