Trestle Rate Limits
Trestle publishes concrete baseline quotas and returns live quota headers on every response — including on anonymous 401s. Quotas are calculated per product / feed-type pair, not per account: one technology provider with an IDX - WebAPI connection to one MLS and an IDX Plus - WebAPI connection to another gets a separate quota for each connection, and a connection's quota grows as more MLSs are added to it. Media (public MediaURL) requests are metered against a separate, larger quota than API queries.
Trestle Rate Limits is the machine-readable rate-limit profile for Trestle on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests_per_hour and requests_per_minute.
The profile also includes response codes documented for throttled.
Tagged areas include Rate Limiting, Real Estate, and MLS.
Limits
Sources
- https://trestle-documentation.corelogic.com/webapi.html
- https://trestle-documentation.corelogic.com/webapi-at-scale.html
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/trestle-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.