Apple Accessory & Device Ecosystem (MFi, Matter, Apple partners)

Where this market publishes its structure

• Apple MFi licensed accessory search (mfi.apple.com/en/account/accessory-search; public JSON /account/web/api/licensee/*) machine-readable, 48084 accessory-technology rows, 5223 brands across 175 technology/category lists; brand name only; 34 brand registrations linked to 25 providers; 5,419 names refused (no repo, too short: HP, LG; Wikidata contradiction: Nissan, Aura)
• Apple Partner Network partner discovery (partnernetwork.apple.com; apple.com/business/partners/ redirects to /business/enterprise/) machine-readable, browser strategy (client-rendered; plain POST to the search endpoint is 403 outside the page); 1309 partners in 66 countries; 2 device-management vendors linked, resellers / MSPs held
• CSA certified products, Matter (csa-iot.org/csa-iot_products; /wp-json/wp/v2/product) machine-readable, 15213 Matter products, 385 companies, name only; deep offsets 504 so read newest- and oldest-first; 9 deduped against iot-smart-home, 2 linked (ecoflow, tuya)
• Apple Platform Deployment guide (support.apple.com/guide/deployment) / Apple Business + School Manager MDM vendors not machine-readable: no vendor list published: the guide documents MDM payloads only (device-management recorded the same 2026-10-20)
• Apple Business / Education app vendor programs not machine-readable: no public register; apple.com/business/partners/ is the Partner Network tool above

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-21 from the 141 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.

gravity 2 · other companies invest to build on it

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

covered 2 · reached mainly through aggregators

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

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

distribution 2 · only sells through cloud marketplaces

undeclared 98 · 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: 1; bridges: 0.