Real Estate and Proptech

Where this market publishes its structure

• RESO orgs and endorsements machine-readable
• AppFolio Stack marketplace machine-readable, partly
• Bridge Interactive not machine-readable: 403 / login
• Spark (FBS) MLS list not machine-readable: 404
• Buildium marketplace, Yardi Interfaces not machine-readable: 403

Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.

Taxonomy how this market maps onto apis.io

Derived 2026-10-23 from the 25 providers in this market we could resolve in the catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.

share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py

Leaders by position (provisional)

Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside position, never inside it. Unknown-builder listings are left out of position shares and counted here.

coverage 4 · reaches banks, carriers, systems or channels (an aggregator)

standard 5 · listed by a voluntary standard's own directory

mixed 1 · no single mode dominates

long-tail 3 · reached only through iPaaS bridges

distribution 3 · only sells through cloud marketplaces

undeclared 9 · declares nothing we can read: no number

Top workflows by market votes

Workflows (Arazzo) and their phrasing are generated by API Evangelist, ranked by market votes (integration edges in the graph, weighted by channel).

In-market workflows only: a step on the market provider's side maps to this market's business capabilities (BC-4940, BC-4950, BC-4960, BC-4970), and the partner is not a generic export/notify app. Other workflows are counted as bridges (including any whose steps do not resolve to a capability yet). Methodology. In-market: 1; bridges: 4.