# AX Check: finta.com Checked 2026-09-19. Pricing is clear, but docs leave agents guessing on setup. Pricing page lists all tiers and limits openly. But no documentation index or quickstart was found, so agents can't confirm setup steps or auth details. ## Onboarding needs a login ## Coding sessions Two of three independent sessions completed and reported very different pricing: one found a paid tiered plan ($7-$15/mo) from the pricing page, the other concluded the product is free open-source software via a package registry. The third session did not complete. ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/80d06c6f-7dee-456d-9f69-5a9aa51ecd2c) · [Read transcript](https://www.ax-check.com/finta.com/sessions/deepseek.json) Final output gives a pricing table ($7/mo Standard, $15/mo Pro, annual discounts) sourced from the pricing doc, with named assumptions (trial length, API-access plan tier, rate limits) and flags a doc inconsistency it found rather than presenting a bare number. #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained real Finta API credentials on its own. It verified the public, unauthenticated GET /health endpoint returns 200, but every authenticated endpoint (GET /me, /accounts, /transactions) returned 401 with no valid API key. Creating a key requires a human to sign up in the Finta dashboard, subscribe (API access is Pro-plan only per docs), and generate the key via Settings > API — none of which the agent could do itself in the sandbox. Event 44: ```text == /me no auth == {"error":"Missing or invalid Authorization header","requestId":"71f2e4e9-c5ca-4b3f-b3a6-77faff3d6a33"} HTTP:401 ``` Event 55: ```text I cannot run the authenticated end-to-end flow: every data endpoint requires an API key created in the Finta dashboard, which itself requires a human to sign up, subscribe (Pro), and create the key — including a Stripe payment step. I can't self-provision that from the sandbox ``` Event 53: ```text == GET /health (no auth needed) (HTTP 200) == { "data": { "status": "ok", "timestamp": "2026-09-19T05:07:02.742Z" } } No FINTA_API_KEY set. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service path to an API key for the hosted product**: Product behavior/test environment limitation, not agent error: Finta's API access requires a paid Pro subscription and a dashboard-generated key (with a Stripe payment step), which needs human signup/billing. The agent correctly identified this and stopped rather than faking success. Event 55: ```text every data endpoint requires an API key created in the Finta dashboard, which itself requires a human to sign up, subscribe (Pro), and create the key — including a Stripe payment step. I can't self-provision that from the sandbox, and I won't stand up anything local to fake it. ``` - **Conflicting docs on API access plan and rate limits**: Agent error would be trusting either doc blindly; this is a product documentation defect. The pricing page and API overview page disagree on whether Standard plan includes API access, and the API overview page's rate limits (200/min) don't match the OpenAPI spec's rate limits (10/min Standard, 30/min Pro). Event 17: ```text Requirement Details Active subscription API access is available on Standard and Pro plans. ``` Event 37: ```text | **API access** | ✗ | ✓ | ``` Event 17: ```text Plan Limit Standard 200 requests / minute Pro Higher limits (contact us) ``` Event 36: ```text | Standard | 10 requests | 500 requests | | Pro | 30 requests | 2,000 requests | ``` #### Suggested Changes - **Reconcile API-access plan tier between pricing page and API docs**: On docs.finta.io/getting-started/pricing.md the table marks API access as Pro-only, while docs.finta.io/api/v2/overview.md states it's available on Standard and Pro. Fix one of the two pages so a developer evaluating cost doesn't need to guess which is authoritative; verify by re-reading both pages after the edit and confirming they match. Event 17: ```text Active subscription API access is available on Standard and Pro plans. ``` Event 37: ```text | **API access** | ✗ | ✓ | ``` - **Reconcile rate-limit numbers between API overview page and OpenAPI spec**: docs.finta.io/api/v2/overview.md lists Standard at 200 requests/minute, but the live OpenAPI spec at api.finta.io/v2/openapi.json lists Standard at 10 requests/minute and 500/day. Update the overview page to match the spec (or vice versa) so integrators don't design against the wrong limit; verify by diffing the two sources after the fix. Event 17: ```text Plan Limit Standard 200 requests / minute Pro Higher limits (contact us) ``` Event 36: ```text | Standard | 10 requests | 500 requests | | Pro | 30 requests | 2,000 requests | ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/01905b0e-86f9-4e78-a559-65d6143950e8) · [Read transcript](https://www.ax-check.com/finta.com/sessions/kimi.json) Final summary states pricing is $0 and grounds it in explicit assumptions: open-source LGPL v3 license, pip-installed v1.3, no accounts/tiers/rate limits, verified via pypi.org/pypi/finta/json (seq 7 web fetch). #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: No hosted product existed to onboard to. The agent identified that developer-facing 'Finta' is actually an open-source local Python library (FinTA) installed via pip, not a hosted SaaS product with accounts, API keys, or pricing tiers. No credentials were obtained or used, and no authenticated hosted operation occurred; the entire session ran locally against a pip package. Event 13: ```text pip install -q finta 2>&1 | tail -3; python -c "import finta; print('finta OK')" ``` Event 11: ```text Finta is **not a hosted product** — there's no cloud service, API keys, or pricing tiers; it's a local pip library (LGPL v3). ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No hosted product or API to onboard against**: The 'Finta' the prompt asked about resolved to a local open-source Python library (FinTA) with no cloud service, accounts, or API keys. This is a product-shape limitation, not an agent or environment error: the agent correctly identified it and proceeded with a legitimate lightweight local workflow instead of fabricating a hosted integration. Event 11: ```text Finta is **not a hosted product** — there's no cloud service, API keys, or pricing tiers; it's a local pip library (LGPL v3). ``` Event 25: ```text Finta is **not a hosted product** — it's a local library, so there was no hosted API/SDK to call. ``` #### Suggested Changes None identified in this transcript. ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/de430d90-5147-463f-aef9-310a7d09c831) · [Read transcript](https://www.ax-check.com/finta.com/sessions/qwen.json) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: Agent never obtained a real Finta API key. It found PI_GATEWAY_API_KEY (an unrelated internal credential) but no finta_-prefixed key from app.finta.io/settings/api. All authenticated Finta endpoints (/me, /accounts, /transactions) were never called with real credentials; only the public GET /health was hit live. Instead the agent built a local mock_backend.py to simulate API responses for a --demo mode, which explicitly does not count as an authenticated product operation. Event 10: ```text PI_GATEWAY_API_KEY= ``` Event 48: ```text == live health (public) == {"data":{"status":"ok","timestamp":"2026-09-19T05:07:02.742Z"}} HTTP:200 time:0.548357s == unauth call to /me (expect 401) == HTTP:401 {"error":"Missing or invalid Authorization header","requestId":"30c23da7-d2d8-4597-8a06-6309cbfa218e"} ``` Event 79: ```text Offline stand-in for the Finta API, used by `--demo` and the unit tests. Shapes mirror the live OpenAPI spec ... It exists because authenticated endpoints need a real `finta_` API key from a paying account; nothing here talks to the network. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to get a Finta API key**: Product behavior/environment limitation: creating a Finta API key requires signing up for a paid or trial account through the app.finta.io dashboard and manually generating a key from Settings, which needs human interaction (email, dashboard clicks) that the agent cannot perform unattended. The agent correctly identified this requirement from docs but had no path to obtain a real finta_ key in this sandboxed session. Event 47: ```text API keys start with the `finta_` prefix. Generate and manage them from [API settings](https://app.finta.io/settings/api). ``` Event 24: ```text finta.io:308 ``` #### Suggested Changes - **Add a sandbox or test API key option for developer evaluation**: On the API overview or API Keys documentation page (docs.finta.io/api/v2/overview or /api/v2/api-keys), offer a way to generate a temporary or sandbox key with seeded sample data so a developer can test authenticated endpoints (/me, /accounts, /transactions) without first completing signup, subscribing, and connecting a real bank. Verify by having a first-time developer call GET /me with the sandbox key and confirm a 200 response without dashboard interaction. Event 47: ```text API keys start with the `finta_` prefix. Generate and manage them from [API settings](https://app.finta.io/settings/api). ``` ### Task given to each agent Help me build a simple example using Finta. 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: C · 53/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 even when text/markdown was requested; no Markdown representation offered. ``` - **Failed** — llms.txt provides an actionable documentation index ```text https://finta.com/llms.txt returns HTTP 404, so no documentation index exists at the standard path. ``` - **Skipped** — llms.txt provides navigation guidance ```text No llms.txt body was returned (404), so navigation guidance cannot be assessed. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text No llms.txt body was returned (404), so API/MCP/skills mentions cannot be assessed. ``` - **Pass** — A compact guide representation exists ```text API docs pages return text/markdown, e.g. introduction and errors, a compact guide representation. ``` - **Pass** — A focused guide is directly retrievable ```text Finta API introduction is directly retrievable as Markdown with API key steps. ``` - **Pass** — Equivalent instructions fit a token budget ```text Introduction Markdown is 2464 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 judged. ``` - **Skipped** — The compact guide is independently actionable ```text No compact agent guide fetched; only API reference pages and signup pages were retrieved. ``` - **Pass** — Install and next-step links resolve ```text Homepage install/next-step links (signup, docs, pricing) fetched successfully with HTTP 200. ``` ### Onboarding - **Skipped** — Docs lead to a relevant quickstart ```text No docs or quickstart page was fetched; only signup pages and a 404 llms.txt. ``` - **Skipped** — Installation commands are extractable ```text No installation or CLI guide was fetched for Finta. ``` - **Skipped** — Code examples are available without interaction ```text No documentation or code-example page was fetched for Finta. ``` - **Skipped** — Prerequisites and auth boundaries are explicit ```text Signup requires email and password, but no API auth docs were fetched. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders plan tiers and prices directly in fetched HTML without interaction. ``` - **Pass** — Prices are stated, not gated ```text Prices stated openly: Taxes $500, Formation $0/mo, Startup $30/mo, Growth $300/mo. ``` - **Pass** — Pricing units and limits are explicit ```text Units and limits explicit: categorizations/mo, transactions, per-item tax add-on fees. ``` - **Pass** — Agents identify pricing and its assumptions ```text 2 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4 Pro: Final output gives a pricing table ($7/mo Standard, $15/mo Pro, annual discounts) sourced from the pricing doc, with named assumptions (trial length, API-access plan tier, rate limits) and flags a doc inconsistency it found rather than presenting a bare number. Kimi K3: Final summary states pricing is $0 and grounds it in explicit assumptions: open-source LGPL v3 license, pip-installed v1.3, no accounts/tiers/rate limits, verified via pypi.org/pypi/finta/json (seq 7 web fetch). This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text Finta API reference pages fetched as Markdown, including embedded OpenAPI spec for endpoints. ``` - **Skipped** — An MCP server is documented and well-formed ```text No MCP server documentation found in the fetched Finta documents. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented in the fetched Finta documents. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK or package registry evidence supplied for Finta. ``` - **Skipped** — Agent skills are published ```text No agent skills published or documented in the fetched Finta documents. ``` [Full report data](https://www.ax-check.com/finta.com/report.json)