@sonordev/re-site-kit

Real estate listings for Sonor-powered Next.js sites: search and filters, a page for every listing, the MLS attribution IDX rules ask for, condo buildings, trending homes, and MCP tools a buyer's AI assistant can use. Sonor pulls the MLS feed and your site reads it with the same SONOR_API_KEY it already uses, so the site never holds an MLS credential.

Full docs live at sonor.dev/re-site-kit.

Built on site-kit

re-site-kit is an industry layer on top of @sonordev/site-kit, not a second stack. site-kit already owns the data plane, analytics, visitor identity and forms, and this kit adds real estate rendering and meaning on top of them:

If you find yourself adding transport, credentials or a provider to a real estate site, check site-kit first. It almost certainly has it.

What's in it

• Search: searchListings with filters, sort and paging, a zero-JavaScript ListingFilters form and crawlable ListingPagination. Search and filters
• Listing pages: getListing, getListingParams, listingMetadata, ListingDetail, ListingGallery and schema.org JSON-LD. Listing pages
• Cards and grids that credit the listing brokerage by default. Cards and grids
• Hot properties ranked from your own listing views. Hot properties
• Buildings: listings matched to your condo building pages, plus a market snapshot for any set of listings. Buildings, Market snapshot
• Leads and compliance: an inquiry form that carries the listing into the CRM, and IDX attribution. Inquiry forms, IDX compliance
• MCP tools so a buyer's AI assistant can search your listings and ask for a showing. MCP tools

Requirements

• @sonordev/site-kit 4.3.0 or later, installed and mounted with SiteKitLayout (or your site's deferred analytics sibling). The MCP tools need site-kit 6.4.0 or later.
• Next.js App Router and React, at the versions your site-kit release supports.
• A Sonor project with the Real Estate module and a listing feed.
• SONOR_API_KEY in the environment. It's the only env var, and it stays server-side.

Install

pnpm add @sonordev/re-site-kit

Quickstart

A listings page with search, filters and paging, all server-rendered:

// app/listings/page.tsx
import { searchListings } from '@sonordev/re-site-kit/server'
import { ListingFilters, ListingGrid, ListingPagination } from '@sonordev/re-site-kit'

type SearchParams = Promise<Record<string, string | string[] | undefined>>

export default async function ListingsPage({ searchParams }: { searchParams: SearchParams }) {
  // One value per parameter (a repeated ?city=…&city=… keeps the first).
  const params = Object.fromEntries(
    Object.entries(await searchParams).map(([key, v]) => [key, Array.isArray(v) ? v[0] : v]),
  )
  const { listings, pagination } = await searchListings({
    city: params.city,
    minPrice: params.min_price ? Number(params.min_price) : undefined,
    maxPrice: params.max_price ? Number(params.max_price) : undefined,
    page: params.page ? Number(params.page) : 1,
  })

  return (
    <main>
      <h1>Homes for sale</h1>
      <ListingFilters basePath="/listings" values={{ city: params.city }} />
      <ListingGrid listings={listings} hrefFor={(l) => (l.slug ? `/listings/${l.slug}` : null)} />
      <ListingPagination
        pagination={pagination}
        listingCount={listings.length}
        basePath="/listings"
        searchParams={params}
      />
    </main>
  )
}

ListingFilters is a plain GET form whose field names are the API's query parameters, so the page's searchParams flow straight back into searchListings, even with JavaScript off. The Quickstart adds the listing detail page, the inquiry form and view tracking.

Subpaths

Every export is listed in the Subpath map.

Docs

• Quickstart
• Search and filters
• Listing pages
• Cards and grids
• Hot properties
• Buildings and the registry
• Market snapshot
• Inquiry forms
• IDX compliance
• MCP tools
• Formatting and JSON-LD
• Types
• Subpath map
• Styling and performance
• Changelog