Basiq
Basiq is an Australian open banking and financial data API platform providing unified access to bank account data and enrichment services. It enables fintechs, lenders, and financial service providers to connect to 180+ Australian and New Zealand banks via CDR (Consumer Data Right) and third-party connectors. The Basiq API provides user management, bank connections, account balances, transaction history, income verification, and expense categorization. Uses JWT Bearer token authentication.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Basiq the way a machine reads it — 76 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 — Basiq scores 57.4/100 (developing), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Basiq
Each block below is one kind of artifact we hold for Basiq. 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 6
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.
Basiq Accounts API
The Accounts API from Basiq — 2 operation(s) for accounts.
Basiq Affordability API
The Affordability API from Basiq — 2 operation(s) for affordability.
Basiq Authentication API
The Authentication API from Basiq — 1 operation(s) for authentication.
Basiq Connections API
The Connections API from Basiq — 2 operation(s) for connections.
Basiq Transactions API
The Transactions API from Basiq — 2 operation(s) for transactions.
Basiq Users API
The Users API from Basiq — 2 operation(s) for users.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Basiq API
OPEN COLLECTIONPricing 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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Basiq 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.
Basiq Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Basiq Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Bank Connections
Connect to 180+ Australian and New Zealand banks via CDR and third-party connectors.
Account Data
Retrieve real-time account balances, available funds, and account metadata.
Transaction History
Access enriched transaction history with categorization and merchant data.
Income Verification
Automated income stream identification and regular/irregular income calculation.
Expense Categorization
Transaction-based expense categorization for affordability and budgeting analysis.
CDR Compliance
Consumer Data Right (CDR) compliant data access for Australian open banking.
Data Enrichment
Transaction enrichment with merchant names, categories, and subcategories.
Scroll within the panel for all 7 ·
Semantic 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.
Basiq Context
JSON-LDSpectral Rules 2
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.
Basiq API Rules
SPECTRALBasiq API Rules
SPECTRALJSON Schema 13
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.
Account
JSON SCHEMAAccountListResponse
JSON SCHEMAConnection
JSON SCHEMAConnectionListResponse
JSON SCHEMACreateConnectionRequest
JSON SCHEMACreateUserRequest
JSON SCHEMAErrorResponse
JSON SCHEMAExpenseReport
JSON SCHEMAIncomeVerification
JSON SCHEMATokenResponse
JSON SCHEMATransaction
JSON SCHEMATransactionListResponse
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 13 ·
JSON Structure 13
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Account
JSON STRUCTUREAccountlistresponse
JSON STRUCTUREConnection
JSON STRUCTUREConnectionlistresponse
JSON STRUCTURECreateconnectionrequest
JSON STRUCTURECreateuserrequest
JSON STRUCTUREErrorresponse
JSON STRUCTUREExpensereport
JSON STRUCTUREIncomeverification
JSON STRUCTURETokenresponse
JSON STRUCTURETransaction
JSON STRUCTURETransactionlistresponse
JSON STRUCTUREUser
JSON STRUCTUREScroll within the panel for all 13 ·
Examples 13
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Account
EXAMPLEAccountlistresponse
EXAMPLEConnection
EXAMPLEConnectionlistresponse
EXAMPLECreateconnectionrequest
EXAMPLECreateuserrequest
EXAMPLEErrorresponse
EXAMPLEExpensereport
EXAMPLEIncomeverification
EXAMPLETokenresponse
EXAMPLETransaction
EXAMPLETransactionlistresponse
EXAMPLEUser
EXAMPLEScroll within the panel for all 13 ·
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.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Lending and Credit Assessment
Use income verification and expense data to assess creditworthiness and affordability.
Personal Finance Apps
Aggregate bank accounts and transactions for budgeting and financial planning tools.
Mortgage Applications
Automate bank statement verification and income confirmation for home loan applications.
BNPL Affordability
Assess buy-now-pay-later affordability using real-time transaction and income data.
Financial Advisory
Provide financial planners with complete client financial pictures across institutions.
Account Verification
Verify bank account ownership for payment and identity verification workflows.
Integrations 8
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Xero
MYOB
Salesforce
Zapier
Commonwealth Bank
ANZ
Westpac
NAB
Scroll within the panel for all 8 ·
Resources
Every other property we hold for Basiq — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/basiq · machine-readable index on apis.io