Unit
Unit is a US Banking-as-a-Service (BaaS) platform that lets companies embed banking, cards, and payments into their own products. Its REST API — organized around Applications, Customers, Accounts (deposit, credit, wallet/FBO, DACA), Cards, Payments (book, ACH, wire, recurring, received, cash deposit), Checks, Card Authorizations, Disputes, Transactions, Statements, Tax Forms, Fees & Rewards, Credit repayments, Stop Payments, and Webhooks — is authenticated with organization and customer bearer tokens and secured with idempotency keys and resource tagging. Unit publishes a public OpenAPI 3.0.2 specification (openapi-unit-sdk) and generates official Node, Python, Ruby, and Java SDKs from it.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Unit the way a machine reads it — 26 machine-readable artifacts across 16 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 — Unit scores 72.7/100 (exemplar), with a separate agent-readiness read of 72/100 (agent native). 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 Unit
Each block below is one kind of artifact we hold for Unit. 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 16
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.
Unit Applications API
End-customer onboarding — create and manage individual and business Applications, application forms, KYC/KYB document upload, verification, and beneficial owners.
Unit Customers API
Manage created Customers (individual and business), authorized and API users, customer archival, and customer-scoped bearer tokens for end-user access.
Unit Accounts API
Deposit, credit, wallet (FBO) and DACA accounts — open, close, freeze and unfreeze, per-account limits, deposit products, customer relationships, and repayment information.
Unit Cards API
Issue and manage debit and credit cards — create, close, freeze/unfreeze, replace, report lost or stolen, set per-card limits, and check secure PIN status, with mobile wallet in...
Unit Payments API
Move money via Book, ACH and wire Payments plus recurring, received (incoming ACH), and cash deposit flows, with counterparties, ACH returns, and institution routing-number look...
Unit Checks API
Check payments (print-and-mail) and mobile check deposits — create, approve, cancel, return, confirm, and manage front and back check images.
Unit Card Authorizations API
Real-time card authorization requests for programmatic approve/decline control, plus retrieval and listing of completed card authorizations.
Unit Disputes API
Retrieve and list card transaction disputes and track their status through the dispute lifecycle.
Unit Transactions API
List and retrieve account transactions across all payment, card, fee, and reward activity for reconciliation and ledgering.
Unit Statements API
Retrieve monthly account statements as HTML or PDF, including bank-branded PDF statements for end customers.
Unit Tax Forms API
List and retrieve customer tax forms and download their PDF renderings for year-end reporting.
Unit Fees and Rewards API
Charge and reverse Fees on accounts and create or retrieve Rewards paid out to customer accounts.
Unit Credit and Repayments API
Credit account repayments and recurring repayments — create, retrieve, and enable or disable scheduled repayments for lending programs.
Unit Stop Payments API
Create, retrieve, and disable stop payments and positive-pay controls to block or match expected payments on accounts.
Unit Webhooks and Events API
Register webhook endpoints, enable or disable delivery, and list and retrieve the Events (resource state changes) Unit emits across the platform.
Unit Sandbox and Reference API
Sandbox-only simulation endpoints (received ACH payments, ATM deposits, card activation) plus store and ATM location reference data for testing integrations.
Scroll within the panel for all 16 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
unit-mcp.yml
MCP SERVERPricing 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.
Unit 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.
Unit 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.
Unit Finops
FINOPSEvent 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.
Unit Events Webhooks
ASYNCAPISecurity Posture 4
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.
Resources
Every other property we hold for Unit — 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 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 4
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/unit · machine-readable index on apis.io