Create an individual or business application by POSTing to /applications with the applicant's personal or business information; Unit runs KYC/KYB automatically and returns a status of Pending, Approved, or Denied.
Poll GET /applications/{id} or handle the application.awaitingDocuments or customer.created webhook to know when the application is approved and a Customer is created.
Create a deposit account by POSTing to /accounts with type depositAccount, a relationships.customer link to the approved customer ID, and the desired deposit product.
Retrieve the account details (routing number, account number) from GET /accounts/{id} once the account status is Open.
Fund the account by initiating an ACH payment via POST /payments/ach or by providing the account and routing numbers to an external sender.
Retrieve transactions and balances by calling GET /accounts/{id}/transactions and GET /accounts/{id} respectively.
Known gotchas
Unit applications go through automated KYC, but some will be flagged for manual review or require additional documents; build a document-upload flow using the /documents endpoints and the awaitingDocuments webhook rather than assuming instant approval.
Account numbers returned by Unit are not your sponsor bank's routing/account directly in all configurations; confirm with Unit whether the account numbers are virtual (mapped) or direct, as this affects how inbound wires must be addressed.
Sandbox environment application approvals are often instant and bypass real KYC logic; test rejection and document-request flows explicitly using Unit's sandbox simulation tools before going live.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp