Unit
Unit is a Banking-as-a-Service (BaaS) platform that lets companies embed deposit accounts, cards, payments, and lending into their own products without becoming a bank. A single REST API, built on the JSON:API specification (media type application/vnd.api+json) and secured with Bearer/JWT tokens, covers onboarding (Applications), Customers, Deposit and Credit Accounts, Debit and Credit Cards, real-time card Authorizations, Payments (Book, ACH, Wire, Recurring, Cash Deposits), Counterparties, Checks, Transactions, Statements, Tax Forms, Fees, Rewards, Credit and Repayments, and Events delivered as signed HTTP webhooks. Unit publishes an official OpenAPI 3.0.2 specification (github.com/unit-finance/openapi-unit-sdk) plus generated Node.js, Python, Ruby, and Java SDKs. Sandbox runs at api.s.unit.sh; production access is provisioned per signed BaaS agreement with Unit's partner banks.
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 — 79 machine-readable artifacts across 18 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 69.1/100 (exemplar), with a separate agent-readiness read of 33/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 Unit'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/unit-co/"
title="Unit on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/unit-co.svg"
alt="Unit Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/unit-co/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/unit-co/"
title="Unit on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/unit-co/card.svg"
alt="Unit 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 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 17
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 Accounts API
Deposit and credit accounts.
Unit API Tokens API
Org-level and customer-level authentication tokens.
Unit Applications API
Individual and business application onboarding (KYC/KYB).
Unit Authorizations API
Completed card authorizations and real-time authorization requests.
Unit Cards API
Debit and credit card issuance and management.
Unit Checks API
Check deposits and outbound check payments.
Unit Counterparties API
External bank accounts and routing-number institution lookups.
Unit Credit and Repayments API
Repayments on credit accounts and receivables.
Unit Customers API
Customer profiles created from approved applications.
Unit Events API
Platform activity log.
Unit Fees and Rewards API
Ad hoc fees and cashback-style rewards.
Unit Payments API
Book, ACH, wire, recurring, and cash-deposit payments.
Unit Risk and Fraud API
Stop payments and card/ACH disputes.
Unit Statements API
Monthly account statements.
Unit Tax Forms API
Annual tax documents.
Unit Transactions API
Posted, immutable ledger entries.
Unit Webhooks API
Subscriptions that deliver events as signed HTTP callbacks.
Scroll within the panel for all 17 ·
Postman Collections 16
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.
Unit Accounts API
POSTMANUnit Applications API
POSTMANUnit Card Authorizations API
POSTMANUnit Cards API
POSTMANUnit Checks API
POSTMANUnit Customers API
POSTMANUnit Disputes API
POSTMANUnit Fees and Rewards API
POSTMANUnit Payments API
POSTMANUnit Statements API
POSTMANUnit Stop Payments API
POSTMANUnit Tax Forms API
POSTMANUnit Transactions API
POSTMANUnit Webhooks and Events API
POSTMANScroll within the panel for all 16 ·
Open Collections 36
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).
API Collection
OPEN COLLECTIONUnit Accounts API
OPEN COLLECTIONUnit Accounts API
OPEN COLLECTIONUnit Accounts API Tokens API
OPEN COLLECTIONUnit Accounts Applications API
OPEN COLLECTIONUnit Applications API
OPEN COLLECTIONUnit Accounts Authorizations API
OPEN COLLECTIONUnit Card Authorizations API
OPEN COLLECTIONUnit Accounts Cards API
OPEN COLLECTIONUnit Cards API
OPEN COLLECTIONUnit Accounts Checks API
OPEN COLLECTIONUnit Checks API
OPEN COLLECTIONUnit Accounts Counterparties API
OPEN COLLECTIONUnit Accounts Credit and Repayments API
OPEN COLLECTIONUnit Credit and Repayments API
OPEN COLLECTIONUnit Accounts Customers API
OPEN COLLECTIONUnit Customers API
OPEN COLLECTIONUnit Disputes API
OPEN COLLECTIONUnit Accounts Events API
OPEN COLLECTIONUnit Accounts Fees and Rewards API
OPEN COLLECTIONUnit Fees and Rewards API
OPEN COLLECTIONUnit OpenAPI specifications
OPEN COLLECTIONUnit Accounts Payments API
OPEN COLLECTIONUnit Payments API
OPEN COLLECTIONUnit Accounts Risk and Fraud API
OPEN COLLECTIONUnit Sandbox and Reference API
OPEN COLLECTIONUnit Accounts Statements API
OPEN COLLECTIONUnit Statements API
OPEN COLLECTIONUnit Stop Payments API
OPEN COLLECTIONUnit Accounts Tax Forms API
OPEN COLLECTIONUnit Tax Forms API
OPEN COLLECTIONUnit Accounts Transactions API
OPEN COLLECTIONUnit Transactions API
OPEN COLLECTIONUnit Accounts Webhooks API
OPEN COLLECTIONUnit Webhooks and Events API
OPEN COLLECTIONUnit API
OPEN COLLECTIONScroll within the panel for all 36 ·
Pricing 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.
Rate 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 Co 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 Co 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 Co 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.
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 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 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
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 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/unit-co · machine-readable index on apis.io
This is an independent, third-party profile of Unit, 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.