Zai
Zai (hellozai.com, formerly Assembly Payments / Assembly) is an Australian payments and Payments-as-a-Service provider headquartered in Melbourne. Zai gives platforms, marketplaces and vertical software companies a programmable way to onboard users, hold funds in managed wallet accounts, collect pay-ins (card, direct debit, BPAY, PayID), and disburse pay-outs across many parties in a single transaction flow. It is API-first: the Assembly API exposes wallet accounts, users, items, transactions, bank accounts, card accounts, fees, callbacks and batch disbursements, layered with Australia's New Payments Platform rails through dedicated Virtual Accounts / PayID and PayTo APIs, plus an Asynchronous API for long-running operations. Authentication is OAuth2 client-credentials (bearer tokens on PayTo), with a Live and Pre-live (sandbox) environment, webhooks with signature verification, and a developer dashboard. Positioned as the embedded-payments and marketplace-money-movement layer for the Australian market and platforms operating there.
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 Zai the way a machine reads it — 39 machine-readable artifacts across 4 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 — Zai scores 52.6/100 (developing), with a separate agent-readiness read of 42/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.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Zai'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/zai/"
title="Zai on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zai.svg"
alt="Zai Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/zai/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zai/"
title="Zai on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zai/card.svg"
alt="Zai 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 Zai
Each block below is one kind of artifact we hold for Zai. 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 26
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.
Zai Addresses API
The Addresses API from Zai — 1 operation(s) for addresses.
Zai Authentication API
The Authentication API from Zai — 1 operation(s) for authentication.
Zai Bank Accounts API
The Bank Accounts API from Zai — 6 operation(s) for bank accounts.
Zai Batch Transactions API
The Batch Transactions API from Zai — 2 operation(s) for batch transactions.
Zai BPay Accounts API
The BPay Accounts API from Zai — 3 operation(s) for bpay accounts.
Zai Callbacks API
The Callbacks API from Zai — 4 operation(s) for callbacks.
Zai Card Accounts API
The Card Accounts API from Zai — 4 operation(s) for card accounts.
Zai Charges API
The Charges API from Zai — 4 operation(s) for charges.
Zai Companies API
The Companies API from Zai — 2 operation(s) for companies.
Zai Direct Debit Authorities API
The Direct Debit Authorities API from Zai — 2 operation(s) for direct debit authorities.
Zai Disbursements API
The Disbursements API from Zai — 7 operation(s) for disbursements.
Zai Fees API
The Fees API from Zai — 2 operation(s) for fees.
Zai Item Actions API
The Item Actions API from Zai — 8 operation(s) for item actions.
Zai Items API
The Items API from Zai — 9 operation(s) for items.
Zai Marketplaces API
The Marketplaces API from Zai — 1 operation(s) for marketplaces.
Zai Pay I Ds API
The PayIDs API from Zai — 3 operation(s) for payids.
Zai PayTo Agreements API
Agreement Management APIs
Zai PayTo Payments API
Payment Initiation APIs
Zai Requests API
The Requests API from Zai — 2 operation(s) for requests.
Zai Sub Wallets API
The Sub-wallets API from Zai — 9 operation(s) for sub-wallets.
Zai Token Auth API
The Token Auth API from Zai — 1 operation(s) for token auth.
Zai Tools API
The Tools API from Zai — 1 operation(s) for tools.
Zai Transactions API
The Transactions API from Zai — 7 operation(s) for transactions.
Zai Users API
The Users API from Zai — 9 operation(s) for users.
Zai Virtual Accounts API
The Virtual Accounts API from Zai — 5 operation(s) for virtual accounts.
Zai Wallet Accounts API
The Wallet Accounts API from Zai — 6 operation(s) for wallet accounts.
Scroll within the panel for all 26 ·
Postman Collections 4
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 4
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).
Assembly API
OPEN COLLECTIONAsynchronous API
OPEN COLLECTIONPayTo
OPEN COLLECTIONVirtual Accounts and PayIDs
OPEN COLLECTIONEvent 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.
Zai Webhooks
ASYNCAPISecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Zai — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
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 5
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/zai · machine-readable index on apis.io
This is an independent, third-party profile of Zai, 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.