SPACEXPLORATION

Returns the full attribute registry — every searchable and filterable field, its type, allowed values, and display label. Read this first to understand the schema before calling search_listings with attribute filters.

Takes no parameters.

Search commercial real estate listings. Returns paginated hits with facet counts; every hit carries the public `url` to cite and its `listed_at` / `updated_at` stamps. For AI-driven search, call interpret_search first to convert a natural-language query into structured filters, then pass those filters — and its bounds, when present — here.

Retrieve the full details of a single listing by its hashid. Returns the complete ListingResource projection including parcel data, all attribute details, and attachments: photos, plus the public documents the broker attached (brochures, offering memoranda, site plans) with their filename and a direct download URL. Broker contact is included only when the requesting user is authorised to manage the listing; such a user also gets every lease suite with its id and status, the rows update_listing takes back.

Translate a natural-language property-search sentence into a structured filter payload compatible with search_listings. Use this as a transparent intermediate step: pass the user's raw query here, then forward the returned filters — and the returned bounds, when present (they carry the "near <place>" intent) — to search_listings.

Look up any US building by its street address and get the public data SPACEXPLORATION keeps on it, whether or not it is for sale or lease: the FEMA flood zone and natural hazard risk, EPA records nearby (including leaking underground storage tanks), Census demographics around it, access and nearby amenities, and, for a building that has been listed on SPACEXPLORATION, the county public record (owner, assessed and market values, taxes, tax lots, recorded sales) with a numbered source for each figure. Also returns the building page URL to share and any live listings in it (pass a listing hashid to get_listing). The first lookup of a building gathers its data in the background, which takes a minute or two: while status.gathering or status.researching_county_record is true, check on it with get_parcel and the returned hashid instead of repeating the lookup. Requires a signed-in account.

Read a building SPACEXPLORATION already has, by the hashid that look_up_parcel returns or that a building page URL (/parcel/{hashid}/...) contains. Returns the same data as look_up_parcel: the address and building page URL, the FEMA flood zone and natural hazard risk, EPA records nearby, Census demographics, access and nearby amenities, the county public record with numbered sources where research has found it, and any live listings in it. It looks nothing up and starts nothing, so use it to check on a building whose status.gathering or status.researching_county_record was true.

Save the current search as a named alert. The user will receive email digests when new matching listings appear. Requires authentication.

List the authenticated user's saved searches, including their filters and alert schedule. Requires authentication.

Takes no parameters.

Delete a saved search by its ID. Only the owner may delete their own searches. Requires authentication.

List all listings owned or brokered by the authenticated user. Optionally filter by status. Requires authentication.

Geocode a free-form US address into coordinates and structured components (street_address, city, county, state, postal_code) plus a formatted address and place_id — exactly the identity fields create_listing requires. Use this first, then pass the result straight into create_listing instead of supplying your own coordinates.

Create a new draft listing. Returns the full created listing exactly as stored, including its hashid and status. Pass an idempotency_key (any client-generated string, e.g. a UUID) to make the call safe to retry — re-sending the same key returns the original listing instead of creating a duplicate.

Update a listing's parcel, pricing, or marketing data, or a lease's suites. Pass at least one group (parcel, pricing, marketing, spaces); send each group whole, not just the changed field. A live listing must stay publishable: an update that leaves it without what publishing required is refused whole, so switch a live listing between sale and lease in one call that carries the new side's price (sale_price, or spaces). Returns the full updated listing exactly as stored.

Set broker-authored attributes on a listing you own. Pass `attributes` as a map of registry field name to value (the field names get_registry returns, e.g. {"attr_parking_spaces": 40, "attr_office_class": "Class A"}). Only fields get_registry marks "writable":true can be set; publish-time computed fields and hot columns (use update_listing for those) are rejected with guidance. Enum fields take the allowed value (or an array for multiselect); send null to clear a field (a live listing refuses to clear one publishing requires). Returns the full updated listing.

Attach a photo to a listing you own directly from its public URL — one call, no separate sign/upload/confirm. The server fetches the image and ingests it with auto-generated thumbnail/hero/full variants. Only https image URLs whose host is publicly routable are accepted. The photo is content-moderated (must be real-estate related and safe) before it can appear publicly — the returned snapshot includes the moderation_status (approved / rejected / escalated) and moderation_reason. A rejected or escalated photo will not be publicly visible and will block publishing until removed or replaced.

Begin an out-of-band file upload. Returns a presigned R2 PUT URL and the headers to use; the file bytes are uploaded directly to storage, never through this channel. After PUTting the file, call confirm_attachment_upload with the returned attachment_id. Supports listings (photos, documents), users (avatar), and pages (cover, photos). Avatars pass an automated content check before they appear publicly.

Finalize an out-of-band upload after the file bytes have been PUT to the presigned URL. Verifies the stored object matches what was signed (size and content-type) and marks the attachment ready. Returns the attachment snapshot with its public variant URLs. Idempotent: confirming an already-confirmed upload returns the same snapshot.

Delete an attachment you own by its ULID. Soft-deletes the row so it no longer appears on the listing. Use this to clean up an abandoned upload (one you signed but never finished) or a photo you no longer want. Idempotent: deleting an already-deleted attachment succeeds. A live listing keeps at least one approved photo: to replace its last one, attach the new photo first, then delete the old.

Kick off the publish pipeline for a draft listing. Enriches with AI, gathers market data, then transitions the listing to Active. Returns the pipeline ID to track progress, plus `suggestions` — non-blocking fixes (a flyer as the cover photo, a placeholder address, an unusual cap rate) to pass on to the user. Fails with the unmet readiness checklist if the listing is not ready. When photos hold it back, `photos_to_review` lists each one with its reason, and `owner_can_keep` marks a photo held only for an MLS or listings-site watermark: ask the user whether they own or have the rights to it, and if so send them to `editor_url` to confirm it there, since only they can.

Get the status of your listing publishes. Pass a listing hashid for the detailed status of that listing's latest publish run — overall state (pending/running/completed/failed), current phase, per-step progress, and any failure reason. Omit the hashid to list your recent publish runs across all your listings. Use this to track a publish_listing call to completion.

Withdraw a listing, removing it from public search. This is a terminal status — the listing cannot be re-activated; create a new listing instead.

Answers to the questions people ask about SPACEXPLORATION itself: what it costs, listing a property, where leads go, finding property, AI assistants (including the built-in one), where the building data comes from, and accounts. Call this before answering any question about how SPACEXPLORATION works or what it costs, answer from what it returns, and link the entry's `url` (or its `see` page when it has no url). Pass `topic` to read one group; leave it out for all of them.

File feedback or a support ticket with the SPACEXPLORATION team: a bug report, feature request, or question about the app or this MCP server. Works anonymously — include a contact email if you want a reply.