Overture Maps Foundation (members + data contributors)

Where this market publishes its structure

• Overture Maps Foundation members (overturemaps.org/about/members/; landscape.overturemaps.org/data/full.json, the embedded landscape's own public data file) machine-readable, 50 members (3 Steering, 3 General, 44 Contributor), all with homepage_url; 13 linked; 2 out of market; 15 held
• Overture data contributors (docs.overturemaps.org/attribution/, Places + Buildings themes) machine-readable, 17 contributor links (12 Places companies + Buildings sources); 2 new providers linked (foursquare, birdeye), microsoft out of market, research / public datasets held
• Overture documentation (docs.overturemaps.org: GERS schema, data releases) machine-readable, no participant list; context only, no edges
• Overture GitHub organisation (github.com/OvertureMaps) machine-readable, org repos only; no member or contributor identities; context only

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 109 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.

builds-on 9 · publishes apps on other platforms' stores

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

covered 6 · reached mainly through aggregators

regulated 4 · named in a regulator's register or partners' contracts

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

mixed 2 · no single mode dominates

long-tail 2 · reached only through iPaaS bridges

distribution 10 · only sells through cloud marketplaces

unknown 4 · every listing has an unknown builder

undeclared 50 · 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 (), 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: 4; bridges: 0.