Real estate AEO · 11 min read
How to Build Your Own IDX Website and MLS Dashboard With AI
By Justin Ratowsky
You can build an agent website with live home search, individual property pages, a sold portfolio and a neighborhood market dashboard using Claude Code, ChatGPT Codex, Cursor or Grok Build. Start with your MLS and broker. Get the right permission for each feature, then use AI to build and test the software. This guide starts with CRMLS in California and shows you how to find the right route anywhere in the United States.
Find your MLS and choose your route
Use the AutoAuthority MLS directory to browse researched licensing paths and contacts. Use the [national RESO MLS roster](https://www.reso.org/mls-list/) to find additional boards by name or office location. Look at the MLS name on your account or invoice and confirm it with your broker. A city can have multiple MLSs, and an MLS headquartered in another state may serve you. For example, Bright serves Delaware and DC and PrimeMLS serves Vermont. A listing data share can expand inventory without giving you a separate membership or license.
- MLS link or hosted embed. Start here if you want a search bar, results or a quick listing gallery. Some MLSs offer a free option. Check where the detail pages open and who handles lead capture, attribution, and updates.
- Managed IDX vendor. The vendor handles the listing display and usually helps with paperwork. Confirm coverage, sold history, URL structure, agent filters, lead export and what happens when you cancel.
- Licensed developer API. Choose this for native URLs, custom design, neighborhood boundaries and more control. Your broker or approved vendor requests the data through the MLS's designated platform. You build and maintain the experience.
- Broker direct or brokerage-approved developer. Some MLSs let a broker license a feed and designate an outside consultant. Ask who signs, who controls the display, and who can operate the feed.
- Separate data products. Request the right permission for VOW, your own broker listings, back-office use, analytics or broader commercial data. Record-specific use, storage, AI processing and downstream distribution each deserve a clear answer.
California worked example with CRMLS and Cotality Trestle
- Confirm your CRMLS membership, office and agent identifiers, public domain, brokerage branding and authorized broker signer. California has multiple MLSs. This is the CRMLS route, and Silicon Valley's MLSListings, for example, publishes its own intake.
- For your own vendor connection, open the Trestle wizard and choose Technology Provider. Use the business name, email and authorized signatory for the company operating the software. An agent using a managed vendor can have the vendor initiate the request. A broker direct arrangement may also be available.
- Create your product in Trestle. In Connections, add CRMLS, review the available feed types and request RESO Web API delivery for public IDX if it is offered for your product. Use CRMLS Data Licensing to describe the specific site and each planned use.
- Enter the authorized display URL and broker or agent signers requested. Preview the license and check setup fees, recurring fees, data limits and who pays. Ask whether future approved sites can be added under one connection with separate contracts.
- Get written approval for the site and approved uses before connecting real data. Obtain company-controlled credentials and store them in the server's secret manager. Build and demonstrate the product with fictional data while you wait.
What DIY IDX costs
Published prices checked November 9, 2026.
Cotality's published small technology-provider tier is $100 per RESO connection per month for up to 50 contracts across Trestle. The published rate becomes $105 in January 2027. CRMLS lists $7 per website URL per month after the first two URLs and separately lists an $85 Trestle transport figure. Use Cotality's newer rate for budgeting and confirm the applicable amount and billing structure in the offer.
One approved connection serving one or two domains would budget at $100 monthly today, or $105 in January 2027, under those assumptions. Five approved domains at one URL per site would budget at $121 today or $126 in January if CRMLS permits them on the same connection. These are planning estimates, not quotes. A separate analytics or VOW license could change the total.
Across the country, compare the one-time application or setup fee, MLS license, transport, per-domain and per-contract charges, hosting and storage, and your maintenance time. CRMLS documents free frameable search. FBS Spark publishes $50 per month per approved MLS for developer API access, with MLS approval still required. MLS Grid collects applicable MLS fees. Ask each vendor for a written quote for the actual market, number of sites, and features. Compare the vendor’s MLS listing coverage against the features it will let you build. MLS Grid and Bridge can be available for the same MLS, as Stellar documents. SimplyRETS provides a developer API on top of a feed you already have permission to use. RealScout can embed a search and listing galleries, with individual detail pages hosted by RealScout. For a CRMLS-only alternative, HomesIDX advertises a $49/month listing API, subject to broker authorization. Confirm its current vendor approval directly with CRMLS and separately verify dashboard rights.
What goes in your licensing request
Describe public search, native listing detail URLs, filtered neighborhood pages, and agent or team production galleries. Ask which listing and buyer-side identifiers you may display. Specify where the software runs, where data and photos will be stored or cached, how quickly changes and removals propagate, and whether previews may use live data. Ask about indexing, status and media restrictions, attribution and seller opt-outs. CRMLS has published a primary-photo-only IDX policy for closed or leased, expired and cancelled listings. Ask about the current rollout and which photos your license permits.
Describe the dashboard separately. Ask whether you can compute public neighborhood inventory, median sold price, median days on market, price per square foot and sale-to-list ratio. Explain whether you will show the individual transactions behind the charts, calculate historical series, store the results or send records to any AI or analytics service. CRMLS Rule 12.11 contemplates specified statistical uses, while §19.2.9 limits IDX listing use to display under its rules. Ask which license covers your implementation and keep the written answer. If you only need a shareable chart, CRMLS documents InfoSparks embeds.
Build the website and dashboard with Claude Code
- Put the project in a private GitHub repository. Start with synthetic active, pending and sold listings. Add a simple local instruction file such as CLAUDE.md or AGENTS.md that names the allowed use, requires human approval before deployment and prohibits printing secrets or sending MLS records to AI services.
- Build the public experience with one fictional neighborhood first. Add a search results page, filters, a map if useful, a property detail route, and a neighborhood page. Keep the feed adapter separate from the UI. That lets you swap the data source without rebuilding the website.
- After approval, connect the server to the provider's documented API. Inspect the allowed metadata and fields. Fetch a small authorized sample. Allowlist public fields and filter by status, opt-out flags and domain rights. Keep credentials, raw provider responses and unauthorized fields out of client bundles and logs.
- If the license permits replication, follow the provider's pagination and incremental sync guidance. Reconcile deletes, seller opt-outs, photo changes and status transitions. Keep the last successful update, avoid serving data past the allowed window, and alert on failed jobs. Use separate test and production credentials where offered.
- Build dashboard calculations from the approved data. Group by neighborhood, property type and time window, with sample counts. Use one defined geography and property-type filter per comparison. Clearly label your dates, data source and methodology. Display an insufficient-data state for tiny samples and explain any suppression threshold.
- Test a withdrawn listing, missing photos, a withheld address, a property that changes status, a duplicate, an expired key, and a feed outage. Compare a real sample against the approved source after authorization. Let your broker inspect the pages before publishing. After launch, run a scheduled health check and a recurring manual licensing and attribution review.
Try this in your coding assistant
Read this repository and propose a small IDX implementation plan. Use synthetic fixtures only. Build one public search page, a native property detail route and one neighborhood dashboard with sample counts and source labels. Keep data access server-side behind a replaceable adapter. Write down the MLS permissions and fields you need before we connect a live feed. Test seller opt-outs, a withheld address, removed listings, missing photos, duplicates and feed failure. Show me the changed files and test results. Stop before requesting credentials, connecting a live MLS or deploying.Learn a workflow you can use in the rest of your business
Start with a useful task you can repeat. Give the coding assistant a real goal, an example, and a short checklist for what a good result looks like. Connect GitHub for review and diffs. Use a separate staging environment for experiments. For scheduled tasks, start with a feed health check or a draft-only market summary made from approved numbers. Review before any client message or public post goes out.
A good next project is a 30-second vertical market update. Start with your own footage and a reviewed script. Use the official HyperFrames or Remotion skills for captions, lower thirds and motion graphics. Use FFmpeg for trimming, audio normalization and exports where helpful. Review names, numbers, caption timing, brokerage attribution, music and media rights before posting. Then turn the workflow into a reusable instruction file so you can run the same process next month.
Sources
- AutoAuthority U.S. MLS licensing directory
- RESO national MLS roster
- RESO Web API
- RESO organization identifiers and lookup API
- NAR MLS policy
- CRMLS IDX resources and fees
- CRMLS licensing request
- CRMLS rules and policies
- CRMLS IDX versus VOW
- CRMLS InfoSparks
- Cotality Technology Provider signup
- Cotality Trestle pricing
- MLS Grid license and developer guides
- Bridge API example from RESO
- FBS Spark API access and pricing
- Bright MLS geographic coverage
- PrimeMLS service area
- Claude Code project instructions and skills
- OpenAI Codex documentation
- Cursor project rules
- xAI Grok Build
- HyperFrames plugins
- Remotion plugins
- FFmpeg documentation
- Stellar MLS developer API options
- SimplyRETS feed requirements
- RealScout integrations and API limits
- HomesIDX advertised plans
- CRMLS contracted vendor list
- CRMLS final-status IDX photos
Frequently asked questions
Can I get an IDX API key directly from RESO?
RESO publishes the standard and a directory of organizations. Get the license and credentials through your MLS and its designated provider.
Does using Claude Code or Codex change the approval process?
The MLS licenses the data use and the broker authorizes the display where required. The coding assistant helps you implement and test it.
Can I show every sold home or count every sale as my own?
Show only sold data approved for the domain and use. Attribute representation accurately and confirm which broker and agent IDs the licensed feed provides.
Can I use my IDX key across clients or states?
Use the approvals and contracts for each broker, domain and dataset. Confirm whether the MLS and transport provider allow several separately authorized contracts to share a technical connection.
Can I launch without a paid API?
Yes. Publish original neighborhood pages and property stories using material you have permission to publish, and use an MLS-approved search link or embed while you evaluate developer access.