Scoring all fifty Australian banks in Australia's Consumer Data Right ecosystem reveals a paradox: the composite Kin Score (product maturity) is low across the sector, with no bank breaking 51, while agent-readiness averages 64, with thirty-eight banks landing in the top agent-native band. The explanation is that mandated CDR dimensions (spec presence, auth clarity, error semantics, MCP server, agent skills) are saturated at 100% because banks inherit a shared, regulator-mandated contract, while product dimensions like idempotency, OpenAPI examples, rate-limit signals, and AsyncAPI events sit near 0%. Governance scores 0.0 for all fifty banks since none own the contract they publish. Only Up, Bendigo, and Teachers Mutual break the pattern by publishing product-level artifacts like rate limits and event APIs, suggesting agent-readiness in this sector reflects compliance rather than genuine platform investment.
Table of contents
What each score is actually measuringWhy agent-readiness runs the other wayThe insight investors and operators should take from thisQuestions this post answers
Why do Australian bank APIs score high on agent-readiness but low on overall product maturity?
Agent-readiness is high because Australia's Consumer Data Right mandates a shared, uniform contract across all banks, which saturates machine-checkable dimensions like spec presence, auth clarity, error semantics, MCP server support, and agent skills at 100% coverage. Product maturity is low because commercial clarity, operational transparency, and governance depend on work banks must do themselves, and governance scores 0.0 across all fifty banks since none own the contract they publish. daily.dev surfaces sector analysis like this for teams weighing real platform investment against compliance-driven API surfaces.
What is the cheapest way for an API provider to improve agent-readiness right now?
Publishing request and response examples in the OpenAPI spec is described as the single cheapest agent-readiness win available, yet none of the fifty scored Australian banks ship them. Combined with publishing rate limits and an event surface via AsyncAPI, these product-level artifacts are what separate a handful of banks, like Up, Bendigo, and Teachers Mutual, from compliance-only implementations. developers deciding where to invest API polish can track patterns like this on daily.dev.