Straight answers, including the paperwork.

An IDX service: it puts MLS listings on your real-estate website, captures buyer leads, and enforces the MLS display rules. It is built to be installed by AI coding agents through a WordPress plugin, an HTTP API or a remote MCP server.

Yes, as long as the site can run code on a server: a WordPress install, a Next.js or Astro app, or any server stack. Listing pages are rendered on the server so search engines see them, and the secret key has to stay on the server.

If your site is static files only, add a server route or an edge function first. Your agent can tell you whether your host supports one.

Accounts are opened by request while GalaxyIDX is in early access. Email support+galaxyidx@bryanos.ai with your site's domain, your MLS and how the site is built.

Your AI agent can do the install. Two things need a person: your broker signs the MLS authorization, and you paste your secret key where it belongs, so it never passes through a chat.

MLS listing data is licensed, so each site needs an authorization from your brokerage. The steps:

1. Request an account (email us), then add your site with every domain it uses.
2. Your broker of record signs your MLS's IDX authorization for the site.
3. Request the MLS authorization in the dashboard: choose the MLS, enter your office id, and add a reference to the signed authorization.
4. It is filed with the MLS, and the MLS reviews it.
5. Once the MLS approves, listings appear on your site.

A pre-filled form with e-signature is planned, but it isn't built yet. Until then, if you don't have your MLS's form, email us before you start.

No. The MLS needs the broker of record of your brokerage, who is the MLS participant. An agent alone can't authorize IDX for a site, and neither can an AI agent.

We are starting with Georgia MLS. Other MLSs are added as brokers in those MLSs authorize their sites and each MLS approves it.

If your MLS isn't Georgia MLS, email us before you install, and we'll tell you where it stands.

That is up to the MLS, and it varies. You can install and test everything while the site is pending; the listing calls simply return no listings until approval.

By default a site shows your own office's listings. Showing every broker's listings for an area needs the MLS to approve that exact domain for it, and it is switched on per MLS.

They are built to be indexed: server-rendered HTML on your domain, listing schema, breadcrumbs, and a sitemap of the pages you may index. One listing gets one indexed page, on the site it belongs to. Nobody can promise rankings, and we don't.

It comes down. Its page answers with a short "no longer available" page and HTTP 410, linking to the area, instead of a stale listing.

The MLS rules allow resizing only: no cropping, nothing drawn over a photo. Photos are contained on a neutral background, which also means nobody's kitchen loses half its counter.

No. Automated value estimates and comments beside listings are not allowed under the display rules, so the product doesn't offer them.

Newest first. There is no paid or featured placement, and search filters are objective only (location, price, type), in line with Fair Housing.

If there has been no good sync for 12 hours, listings are hidden rather than shown out of date.

To your email. One route can cover every site, or each site can have its own. Delivery to a CRM (Lofty today) or a signed webhook needs a stored credential, so for now we set it up with you: email us. Every lead carries the site, the listing, the action (tour, question, alert) and the page it came from.

No. Text messaging is off, and lead forms never show a text-message consent box.

No. It starts unchecked; a visitor opts in only by ticking it.

Leads are delivered to you and kept in your account. You handle them under your own privacy policy. To delete a person's lead data on request, contact support.

$10/month per site for the software, plus whatever your MLS charges for its data feed, passed through at cost as its own line.

It is the MLS's charge, not ours. Showing it on its own line, at cost, lets you see exactly what the MLS takes.

At /llms.txt. It lists the rules and links to every doc, the Agent Skill and the OpenAPI spec. See For AI agents.

Yes, a remote one at https://mcp.galaxyidx.com/mcp. It authenticates with your secret key as a bearer token, and every tool works only inside your account.

No. Put it in your host's environment as IDX_SECRET_KEY, and have the agent reference the variable. It should never print, log or commit the key.