unit.co
Unit is a financial infrastructure platform that lets software companies embed accounts, payments, cards, and capital products into their own products. It offers both a custom API-based integration path and managed ready-to-launch banking experiences.
Unit exposes a documented REST API for its financial platform plus published white-label UI SDK/package integrations; authentication is via bearer org API tokens or customer API tokens depending on the surface and scope.
- Unit REST APIdiscovered
Sign up for a Unit sandbox account at Sandbox and choose Custom Build. In the Unit Dashboard, go to Developer → API Tokens to create an org-level token with the scopes you need; the docs say org API tokens can also be created programmatically or through the Dashboard. Use the live dashboard at app.unit.co for production tokens after your live environment is enabled.
First create or identify a Unit customer in your program. Then use an org token with the customer-token-write scope to call the Customer Token API described at Customer API Tokens. For sensitive scopes, first create a verification challenge at POST /customers/:customerId/token/verification, collect the OTP from the customer, then create the customer token at POST /customers/:customerId/token with verificationToken and verificationCode. In sandbox, the docs say to use passcode 000001 for this verification flow.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://unit.co/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing