Australia Consumer Data Right register (accredited data recipients; banking, energy, non-bank lending)

Where this market publishes its structure

• CDR Register accredited data recipients (api.cdr.gov.au/cdr-register/v1/all/data-recipients, x-v 3) machine-readable, 39 legal entities (31 active, 8 surrendered), 42 brands, 268 software products; 13 in-market providers linked (TrueLayer, Intuit Inc surrendered = lapsed)
• CDR Register data holder brands (/all/, /banking/, /energy/ brands/summary, x-v 2) machine-readable, 378 brands; ALREADY read by open-banking (sweep-standard-registers.py, 49 repos); edges reused, sector context only, no new holder edges
• CDR Register /banking/ and /energy/ data-recipients machine-readable, return the same 39 entities as /all/; the register does not scope recipients by sector

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 56 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 1 · reaches banks, carriers, systems or channels (an aggregator)

covered 5 · reached mainly through aggregators

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

mixed 2 · no single mode dominates

list 1 · a long list on its own page, mostly unevidenced

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: 5; bridges: 0.