# AX Check: unit.co Checked 2026-09-29. Docs and sandbox setup are clear, but pricing is nowhere to be found Quickstart, API reference, and curl examples all resolve cleanly. All 3 coding sessions found no pricing page and could only guess at fee categories. ## Onboarding needs a login ## Coding sessions All three independent sessions (DeepSeek V4.1 Flash, Kimi K3, Qwen 3.8 Max) completed their runs and could follow the sandbox quickstart, but each reported no public pricing page. They could only describe likely fee categories like platform, per-account, and per-transaction charges without stating actual figures, with one explicitly refusing to guess at numbers. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/0e8bb428-75e9-466c-a541-1aa521e254cb) · [Read transcript](https://www.ax-check.com/unit.co/sessions/deepseek.json) Final output states Unit has no public pricing and frames the likely cost structure (platform/implementation fees + per-account/per-transaction/card fees) with explicit caveats that it varies by enabled products, volume, and partner bank, and tells the user not to rely on any number. Session findings unavailable. ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/86de8d04-b274-4128-bafc-ff07f17076fb) · [Read transcript](https://www.ax-check.com/unit.co/sessions/kimi.json) Final output states there is no public pricing page, that production pricing is a negotiated monthly platform fee plus per-account/per-transaction charges, and explicitly flags the sandbox as free/self-serve while noting it couldn't find published tiers — names the assumptions and caveats rather than inventing a number. #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained real Unit API credentials. It identified that a sandbox token requires signing up at app.s.unit.sh with an email-verified dashboard account, explicitly said it could not do that autonomously, and instead tested connectivity with a deliberately invalid token string ('bogus'), which correctly returned a 401 unauthorized. No authenticated product operation (e.g. actually creating an application record) was ever demonstrated. Event 169: ```text I can't fully execute the flow because a sandbox API token requires signing up at `app.s.unit.sh` with an email-verified dashboard account — I can't do that autonomously. ``` Event 163: ```text === bogus token vs live sandbox === Unit API error: [ { title: 'Bearer token is invalid or expired', status: '401', code: 'unauthorized' } ] ``` Event 96: ```text Sandbox signup is self-serve via the Unit Dashboard but requires an email-verified account — I'll flag that as the one manual step. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-serve API token without email-verified signup**: Product behavior/session limitation: Unit's sandbox requires creating an account at app.s.unit.sh and verifying an email before an API token is issued. The agent has no way to complete email verification autonomously, so it could not obtain a real token or execute an authenticated create-application call. This is a normal login/signup requirement, not a product defect. Event 169: ```text I can't fully execute the flow because a sandbox API token requires signing up at `app.s.unit.sh` with an email-verified dashboard account — I can't do that autonomously. ``` - **Documented sandbox API host no longer resolves**: Agent error/stale docs: the agent's own knowledge (and early guesses) pointed to https://api.s.unit.co as the sandbox base URL, but that host would not resolve (DNS failure), forcing extra discovery work before finding the current host https://api.s.unit.sh via the docs' sandbox page. This cost several tool calls but was fully recovered without further impact. Event 21: ```text * Could not resolve host: api.s.unit.co * Closing connection --- 404 ``` Event 72: ```text The sandbox base URL is `https://api.s.unit.sh` now. Let me test it. ``` #### Suggested Changes - **Publish a public pricing page linked from the main site**: The agent tried https://www.unit.co/pricing/ and was redirected to a 404 'Not Found' page, and could only conclude pricing is demo/sales-negotiated. Add a pricing or 'how billing works' page linked from the main nav or docs, and verify it resolves with a 200 status and lists at least indicative fee structures. Event 87: ```text 404 https://www.unit.co/pricing Not Found Platform Overview Platform Build with Unit's powerful infrastructure. ``` - **Update docs/SDK references from api.s.unit.co to api.s.unit.sh**: The deprecated sandbox host api.s.unit.co no longer resolves via DNS, which could mislead developers using older docs or cached references. Audit docs.unit.co and any SDK README/examples for the old host and replace with api.s.unit.sh; verify by curling the old host and confirming redirects or removal rather than silent DNS failure. Event 21: ```text * Could not resolve host: api.s.unit.co * Closing connection --- 404 ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/018cae4f-417e-4571-8e45-63281cac1801) · [Read transcript](https://www.ax-check.com/unit.co/sessions/qwen.json) No cost figure is ever given — final output only says 'Unit does not publish pricing... I won't guess at numbers'; it names the fee categories (platform, per-account/card/payment, interchange) but supplies zero dollar figures or ranges tied to a plan/region/workload. #### End-to-end onboarding - **Onboarding needs a login**: Agent scaffolded a TypeScript example using the official @unit-finance/unit-node-sdk but never obtained a real Unit API token. The example script explicitly checks for UNIT_TOKEN and exits with a blocked message when absent, which is exactly what happened when run. No authenticated call against Unit's hosted API ever succeeded; agent explicitly states Unit requires a sales-gated partner account to get credentials, which it could not self-serve. Event 67: ```text BLOCKED: set UNIT_TOKEN with an API token from your Unit dashboard (requires a Unit partner account). Nothing to call without it. run exit: 1 ``` Event 73: ```text I could not execute real API calls: **Unit requires an API token from a partner account, and signup is sales-gated** ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to obtain a Unit API token**: Unit's Banking-as-a-Service platform requires an API token issued via a partner account, and the agent had no path to generate one autonomously. This is a product/credential gating issue, not an agent error or environment limitation — the agent correctly identified it and stopped rather than guessing or faking a token. Event 73: ```text Unit requires an API token from a partner account, and signup is sales-gated (it's an enterprise Banking-as-a-Service platform — you can't self-serve register like Stripe). ``` - **SDK type definitions did not match the agent's initial usage**: Agent's first draft called unit.applications.createIndividualApplication and passed an object to the Unit constructor, both of which do not exist in the installed SDK version (7.0.2). This was an agent authoring error (wrote code against assumed API shape rather than checked types first), quickly self-corrected after inspecting the SDK's .d.ts files. Event 32: ```text example.ts(38,47): error TS2339: Property 'createIndividualApplication' does not exist on type 'Applications'. ``` #### Suggested Changes - **Publish a self-service sandbox signup path for the Node SDK quickstart**: The agent could not proceed past a token wall because obtaining a Unit API token requires going through a sales-gated partner account process. Product owner should verify whether a lighter-weight sandbox-only signup (email + instant token) exists and, if so, surface it directly in the unit-node-sdk README or docs.unit.co quickstart so developers evaluating the SDK are not blocked immediately. Event 73: ```text it's an enterprise Banking-as-a-Service platform — you can't self-serve register like Stripe ``` - **Align published TypeScript types with documented method names in unit-node-sdk**: The agent (correctly following the SDK's public method conventions elsewhere) tried unit.applications.createIndividualApplication and a config-object constructor, both of which do not match the actual shipped types (constructor takes positional token/basePath args, and application creation is a single generic .create method with a discriminated union). Check the SDK's README/quickstart examples against the actual compiled .d.ts in the published npm package to ensure they're consistent, and add a type-checked example snippet to the README to catch such drift. Event 32: ```text example.ts(27,14): error TS2554: Expected 2-3 arguments, but got 1. ``` Event 44: ```text constructor(token: string, basePath: string, config?: UnitConfig); ``` ### Task given to each agent Help me build a simple example using Unit. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop. No product credentials were supplied and no purchases were authorized. ## Score: B · 81/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — Homepage answers Markdown requests ```text Homepage returned text/html for a text/markdown request; no Markdown representation offered. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt links docs, API reference, guides and platform pages with organized sections. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt groups content under clear headings like Developers, Platform, and Resources. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt lists API documentation and developer tooling; no MCP or skills offered. ``` - **Pass** — A compact guide representation exists ```text llms.txt is a compact Markdown guide covering platform, developers, and resources. ``` - **Pass** — A focused guide is directly retrievable ```text Quickstart page gives concrete steps: signup, token, then curl calls. ``` - **Pass** — Equivalent instructions fit a token budget ```text llms.txt is 1973 tokens, well under the 8000-token budget. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown unsupported, so link preservation across formats cannot be measured. ``` - **Pass** — The compact guide is independently actionable ```text Quickstart gives concrete steps: sign up sandbox, create token, then curl calls to create account, fund, issue card, spend. ``` - **Pass** — Install and next-step links resolve ```text Fetched quickstart, tooling, basic-entities and sandbox pages all returned HTTP 200. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Docs quickstart page gives concrete sandbox steps: create application, fund account, issue card. ``` - **Pass** — Installation commands are extractable ```text Quickstart shows extractable curl commands with headers, auth token, and JSON payloads. ``` - **Pass** — Code examples are available without interaction ```text Quickstart and Basic Entities show full curl request examples inline without interaction. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text Quickstart prerequisites require sandbox signup and API token with scopes; Bearer auth shown. ``` ### Pricing - **Failed** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 1 fell short. DeepSeek V4.1 Flash: Final output states Unit has no public pricing and frames the likely cost structure (platform/implementation fees + per-account/per-transaction/card fees) with explicit caveats that it varies by enabled products, volume, and partner bank, and tells the user not to rely on any number. Kimi K3: Final output states there is no public pricing page, that production pricing is a negotiated monthly platform fee plus per-account/per-transaction charges, and explicitly flags the sandbox as free/self-serve while noting it couldn't find published tiers — names the assumptions and caveats rather than inventing a number. Qwen 3.8 Max: No cost figure is ever given — final output only says 'Unit does not publish pricing... I won't guess at numbers'; it names the fee categories (platform, per-account/card/payment, interchange) but supplies zero dollar figures or ranges tied to a plan/region/workload. This behavioural item does not affect the fast grade. ``` - **Skipped** — Pricing is readable without interaction ```text Only the homepage was fetched; no Unit pricing page appears in the evidence. ``` - **Skipped** — Prices are stated, not gated ```text No Unit pricing page was fetched, so no stated or gated prices are observable. ``` - **Skipped** — Pricing units and limits are explicit ```text No Unit pricing page was fetched, so pricing units and limits cannot be judged. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text API reference at /docs/api/ and OpenAPI 3.0 spec linked on the Using the API page. ``` - **Skipped** — An MCP server is documented and well-formed ```text No MCP server documentation found in the fetched Unit docs. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented; only API, SDKs, and Postman collection offered. ``` - **Skipped** — SDK packages resolve on their registries ```text SDKs listed on GitHub but no registry lookup result supplied to confirm resolution. ``` - **Skipped** — Agent skills are published ```text No agent skills published or documented in the fetched Unit pages. ``` [Full report data](https://www.ax-check.com/unit.co/report.json)