# Trestle

**Canonical:** https://apis.io/providers/trestle/  
**Website:** https://www.cotality.com/products/trestle  
**APIs profiled:** 4

Trestle is the real estate data distribution platform operated by CoreLogic (rebranded Cotality in 2025), sitting between roughly 500 US Multiple Listing Services and the technology providers, brokers and aggregators that consume their listing data. Its home market is the United States. Trestle occupies the licensing-and-transport layer of the residential real estate value chain: it maps each participating MLS into the RESO Data Dictionary and republishes it through a RESO Web API 2.0 / OData 4.0 endpoint and a legacy RETS 1.8 endpoint, plus a bidirectional Direct Web API into the Matrix MLS CRM and a Participant Reporting API used to prove broker relationships back to the MLSs. Its API posture is unusually honest for this sector: the documentation portal at trestle-documentation.corelogic.com is fully public and needs no login, the OAuth2 client-credentials flow and every OData query convention are published openly, and the OData service document at api.cotality.com/trestle/odata answers anonymously with a 200. But nothing behind it is reachable. The $metadata document and every entity set return 401 Bearer, and credentials are only issued after a developer registers a Technology Provider or Broker account, requests a connection to a specific multiple listing organization, and completes an e-signed data licence contract that all parties sign — a contract most MLSs will only ratify if a licensed broker or agent sponsors it or the technology provider files periodic participant reports. Trestle is RESO-certified and publicly documented, and still effectively uncallable without a signed licence. Certification is not reachability.

## Kin Score — 42.0 / 100 (developing)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 42.0).

| Facet | Score |
|---|---|
| Discoverability | 83.3 |
| Contract Quality | 7.0 |
| Governance | 18.2 |
| Contract Governance | 18.2 |
| Operational Transparency | 65.8 |
| Developer Ergonomics | 63.7 |
| Commercial Clarity | 42.1 |
| Access Clarity | 42.1 |

## Agent readiness — 17.5 (agent-aware)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | yes |
| Idempotency | no |
| Error Semantics | documented |
| OpenAPI Examples | documented |
| Rate Limit Signal | documented |
| Event Surface Described | no |
| Agent Skills | derived |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## APIs (4)

- **Trestle RESO Web API** — The primary Trestle interface — a RESO Web API 2.0 / OData 4.0 endpoint that republishes MLS data mapped to the RESO Data Dictionary. The anonymously readable OData service docu...
- **Trestle Direct Web API** — A bidirectional OData interface into the Matrix MLS database, separate from the RESO feed. The CRM reference documents Contacts, EmailHistory, Lists, PortalContents, SavedSearch...
- **Trestle Participant Reporting API** — A compliance API that lets technology providers report to each MLS which brokers they hold contracts with — the mechanism by which the licence relationship behind a data feed is...
- **Trestle RETS** — Trestle's legacy Real Estate Transaction Standard interface, documented as compliant with RETS 1.8. RESO no longer updates the RETS specification, but Trestle continues to serve...

## MCP servers (1)

- **Trestle MCP Server** — Trestle publishes no MCP server, no tool manifest, and no agent-facing surface of any kind. Its parent, Cotality, DOES operate a hosted MCP server — but it fronts a different pr...

## Security (3)

- **Trestle Authentication** — oauth2/openIdConnect/http · 4 schemes
- **Trestle Domain Security** — TLSv1.3 · DMARC
- **Trestle Vulnerability Disclosure** — Bugcrowd

## Tags

Real-Estate, United States, MLS, RESO, Property Listings, IDX, PropTech, Data Distribution, OData, RETS, Listing Syndication

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/trestle/). Scores are computed from the provider's own public artifacts under a published rubric.