The State of Australian Banking APIs

About this paper

Not one of the fifty Australian banks in my catalog reaches the “Strong” band, let alone “Exemplar” — the whole sector tops out in “Developing,” and the highest score is 56.5. There is no Australian banking API a competent agent could adopt unassisted today. That is not fifty separate failures; it is one structural fact. Australia’s Consumer Data Right mandates a byte-for-byte standard contract, so these are not fifty APIs — they are one API deployed fifty times, and once you see why, the rest of the report reads as its consequences.

I read every bank the way an integrator or an agent would: not the marketing site, the machine-readable evidence — the OpenAPI, the scopes, the security posture, the discovery surface. This report is written for two readers: the person who runs one of these banks’ API programs and needs to know where they actually stand against the field, and the investor or acquirer trying to tell a real platform from a compliance filing before writing a check. The mandate produced existence, not quality — it got fifty banks to publish an API, and none of them to publish a good one. The gap between those two things is the market, and this report is a map of it, scored provider by provider, with a punch-list any bank could execute to own it.

What's inside

1. Executive summary — the ceiling, and why it frames everything
2. The state of the sector — one regulator's API, fifty times
3. The resource taxonomy — bedrock by mandate, and the two who went further
4. The composite Kin Score — and why it's the foundation
5. Agent-readiness — the paradox in the data
6. The blueprint — what the leaders satisfied, and what none of them have
7. Standards and artifacts — why this matters for the agentic turn
8. Security, auth, scopes, and consent — where the mandate earned its keep
9. Provider-by-provider intelligence — the upper band and the majors
10. The investable thesis — build, partner, or watch

What you get for $500.00