Register for MLS Grid access at mlsgrid.com and obtain OAuth 2.0 client credentials; access requires an agreement with the participating MLS boards whose data you intend to replicate
Use the replication endpoint with ModificationTimestamp as your incremental key: issue GET /Property?$filter=ModificationTimestamp gt <last_sync_timestamp>&$orderby=ModificationTimestamp asc
Set a conservative page size (e.g., $top=500) and follow @odata.nextLink until exhausted; store the highest ModificationTimestamp seen as your checkpoint
Respect the HTTP 429 response: back off exponentially and resume from your last checkpoint — do not replay from the beginning after a rate-limit suspension
Set your User-Agent header to your OAuth 2.0 access token value as required by MLS Grid (mandatory from June 2026 for media requests)
For media/photos, fetch URLs from the Media resource after syncing property records; media access uses the same credentials but counts toward separate usage limits
Known gotchas
MLS Grid will suspend your access token if activity is flagged as excessive — monitor your usage dashboard and throttle proactively rather than reacting to suspensions
Data is replicated, not real-time; MLS Grid targets eventual consistency, so do not promise sub-minute freshness to downstream consumers
Broker-only access plans restrict data to listings where the credentialed broker is the listing or selling agent — confirm your access tier before building a full-market feed
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp