domain: bridgeinteractive.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register at bridgedataoutput.com and submit a use-case application; Zillow Group data access requires approval and acceptance of the Zillow Data Terms of Use
Obtain your API key and dataset token after approval; each dataset (e.g., a specific MLS board) has its own token
Issue GET requests to the Bridge Web API endpoint with your API key and dataset token as query parameters, using OData-style $filter for field-level queries
Use the replication endpoint or the _filter parameter with a ModificationTimestamp filter for incremental updates
Default rate limit is 1,000 requests per day on standard access; request higher limits through the Bridge team for production workloads
Contact api@bridgeinteractive.com to request Zillow Group data sets or expanded MLS coverage beyond what is self-serve in the dashboard
Known gotchas
Storage of Zillow-sourced data is prohibited under the Zillow Data Terms of Use — design your architecture for on-demand querying, not local replication, when handling Zillow datasets
MLS access approval is separate for each dataset and depends on your relationship with that MLS board; approval is not guaranteed
The 1,000 requests/day default limit makes Bridge unsuitable for high-frequency replication without a negotiated higher-tier agreement
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?