Akahu
Akahu provides open banking and open finance infrastructure for New Zealand. It enables individuals and businesses to securely connect their financial accounts to trusted third‑party applications, offering APIs for account aggregation, payments, and data sharing while complying with local regulations and promoting financial innovation.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Akahu the way a machine reads it — 95 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Akahu scores 54.4/100 (strong), with a separate agent-readiness read of 32/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Akahu's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/akahu/"
title="Akahu on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/akahu.svg"
alt="Akahu Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/akahu/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/akahu/"
title="Akahu on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/akahu/card.svg"
alt="Akahu Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Akahu
Each block below is one kind of artifact we hold for Akahu. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 27
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Akahu Accounts API
The Accounts API from Akahu — 5 operation(s) for accounts.
Akahu Applications API
The Applications API from Akahu — 4 operation(s) for applications.
Akahu Auth API
The Auth API from Akahu — 2 operation(s) for auth.
Akahu Authorisations API
The Authorisations API from Akahu — 1 operation(s) for authorisations.
Akahu Categories API
The Categories API from Akahu — 2 operation(s) for categories.
Akahu Connections API
The Connections API from Akahu — 3 operation(s) for connections.
Akahu Data Refresh API
The Data Refresh API from Akahu — 2 operation(s) for data refresh.
Akahu Datafiles API
The Datafiles API from Akahu — 3 operation(s) for datafiles.
Akahu Documents API
The Documents API from Akahu — 3 operation(s) for documents.
Akahu Feedback API
The Feedback API from Akahu — 1 operation(s) for feedback.
Akahu Identity API
The Identity API from Akahu — 6 operation(s) for identity.
Akahu Me API
The Me API from Akahu — 1 operation(s) for me.
Akahu Merchants API
The Merchants API from Akahu — 1 operation(s) for merchants.
Akahu Orgs API
The Orgs API from Akahu — 1 operation(s) for orgs.
Akahu Outlets API
The Outlets API from Akahu — 1 operation(s) for outlets.
Akahu Parties API
The Parties API from Akahu — 1 operation(s) for parties.
Akahu Payments API
The Payments API from Akahu — 6 operation(s) for payments.
Akahu PDFs API
The PDFs API from Akahu — 2 operation(s) for pdfs.
Akahu Referrals API
The Referrals API from Akahu — 5 operation(s) for referrals.
Akahu Reports API
The Reports API from Akahu — 8 operation(s) for reports.
Akahu Resources API
The Resources API from Akahu — 1 operation(s) for resources.
Akahu Sharing Requests API
The Sharing Requests API from Akahu — 2 operation(s) for sharing requests.
Akahu Status API
The Status API from Akahu — 1 operation(s) for status.
Akahu Support API
The Support API from Akahu — 1 operation(s) for support.
Akahu Transaction Enrichment API
The Transaction Enrichment API from Akahu — 1 operation(s) for transaction enrichment.
Akahu Transactions API
The Transactions API from Akahu — 7 operation(s) for transactions.
Akahu Webhooks API
The Webhooks API from Akahu — 5 operation(s) for webhooks.
Scroll within the panel for all 27 ·
Agent Skills 5
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
akahu-create-and-retrieve-application
AGENT SKILLakahu-get-account-transactions
AGENT SKILLakahu-payments-make-and-retrieve
AGENT SKILLakahu-sharing-requests-create-and-retrieve
AGENT SKILLakahu-verify-name
AGENT SKILLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Akahu Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Akahu Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Akahu Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Akahu Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Akahu API Rules
SPECTRALJSON Schema 55
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessRequest
JSON SCHEMAAccount_2
JSON SCHEMAAccount
JSON SCHEMAAppTokenId
JSON SCHEMAApplicationCreateParams
JSON SCHEMAApplication
JSON SCHEMAApplicationUpdateParams
JSON SCHEMAAuthorisationRequestSuccessResponse
JSON SCHEMACategory
JSON SCHEMAConnection
JSON SCHEMACreateReferralParams
JSON SCHEMACreateReferralRedemptionParams
JSON SCHEMACreateSharingRequestParams
JSON SCHEMADatafileId
JSON SCHEMADatafile
JSON SCHEMADocumentId
JSON SCHEMADocument
JSON SCHEMAEnduringLoginHint
JSON SCHEMAGenieCategory
JSON SCHEMAGenieFeedback
JSON SCHEMAGenieMerchant
JSON SCHEMAGenieOutlet
JSON SCHEMAGenieSearchRequest
JSON SCHEMAGenieSearchResponse
JSON SCHEMAMe
JSON SCHEMAOAuthRedirectMode
JSON SCHEMAOneOffIdentity
JSON SCHEMAOneOffPaymentConnectionsResponse
JSON SCHEMAOneOffPaymentRequestResponse
JSON SCHEMAOneOffPaymentRequest
JSON SCHEMAOneOffPayment
JSON SCHEMAOneOffVerifyNameResult
JSON SCHEMAOrg
JSON SCHEMAParty
JSON SCHEMAPayment
JSON SCHEMAPdfExport
JSON SCHEMAPdfStatement
JSON SCHEMAPendingTransaction
JSON SCHEMAReferralRedemption
JSON SCHEMAReferral
JSON SCHEMAReportAccount
JSON SCHEMAReportDataSource
JSON SCHEMAReportInsight
JSON SCHEMAReport
JSON SCHEMAReportTransaction
JSON SCHEMAResource
JSON SCHEMASharingRequest
JSON SCHEMAStatus
JSON SCHEMAToken
JSON SCHEMATransaction_2
JSON SCHEMATransaction
JSON SCHEMAVerifyNameData
JSON SCHEMAVerifyNameResult
JSON SCHEMAWebhookEvent
JSON SCHEMAWebhook
JSON SCHEMAScroll within the panel for all 55 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Akahu — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/akahu · machine-readable index on apis.io
This is an independent, third-party profile of Akahu, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.