ax-check.com
by Gauge
T
Tink
tink.com
ax-check.com
Checked 29 September 2026
D
29/100
Agents need your login
Tink has no real quickstart, and pricing means "call sales"
Docs and a compact guide are missing or unassessed (14 of 23 checks); pricing page confirms rates are for existing customers only, not quoted upfront.
5 fixes to start with
Concrete changes, backed by what we found.
State what each price includes and how overages are billed.
Pricing page shows feature rows but no explicit price units, transaction volumes or limits.
https://tink.com/llms.txt returns HTTP 404, so no documentation index exists.
Recorded coding sessions
Same task, 3 models, no tink.com account. Recorded 29 September 2026 on Pi.
3 recorded · 1m 14s
1m 14s · recorded
Session findings
Select a finding to see it in context.
›Thinking…
The user is asking about Tink. Tink is a European open banking API provider (acquired by Visa), offering open banking services. They have SDKs and a REST API. However, Tink requires credentials (client ID/secret), and you need to register for the Tink Cloud Console. Let me check the environment. There might be Tink credentials in environment variables, and I should also check the state of the repository.
Also, regarding pricing: Tink is typically enterprise-priced, and pricing isn't publicly disclosed. There might be some information available though. Let me check the sandbox.
✓$ ls -la /sandbox/repo 2>/dev/null; echo "---"; env | grep -i -E "tink|api|key|token|secret|client" | sed 's/=.*/=<redacted>/'; echo "---"; ls /sandbox✓└{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 29 08:19 ..\ndrwxr-xr-x 8 root root 4096 Sep 24 20:05…ctrl+o
{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 29 08:19 ..\ndrwxr-xr-x 8 root root 4096 Sep 24 20:05 .git\n-rw-r--r-- 1 root root 408 Sep 18 08:00 .gitignore\n---\nPI_GATEWAY_API_KEY=<redacted>\nGIT_CONFIG_KEY_0=<redacted>\n---\nrepo\n","type":"text"}]}×$ cat /sandbox/repo/README* 2>/dev/null | head -50; which curl node python3 java mvn 2>/dev/null✓└{"content":[{"text":"/usr/bin/curl\n/usr/local/bin/node\n/usr/local/bin/python3\n\n\nCommand exited with code 1","type":"text"}],"details":{}}
›Thinking…
Tink credentials aren't available. Tink (tink.com) is an open banking API, and to use the hosted product, you need a Tink Cloud account with a client ID and secret. Without credentials, you can't actually call the API. Can I confirm via the API whether credentials are required? Yes—the Tink API requires OAuth client credentials. There's no sandbox without an account. Pricing: Tink doesn't publicly disclose pricing, it's per-call/enterprise contract pricing via Visa.
The user is saying: "If you're blocked, let me know. If this product doesn't have an actionable developer workflow, be upfront and stop." The developer workflow itself does exist (REST API + SDK), but credentials are required, and I don't have them. So I'm blocked by the lack of credentials. Can I still build a sample? The user is asking for "a simple sample using Tink." I could write a minimal sample script that uses the Tink REST API (e.g., fetching a list of countries or institutions), but without credentials it can't run against the actual API. That would probably count as "blocked." The user has asked to be upfront and stopped when blocked.
Should I still write the sample code? They're asking for it, and it's lightweight. But without credentials, running it would fail. I think the best approach is: be upfront—Tink requires an account/credentials that I don't have, so I'm blocked on actually using the hosted product. Still, I can provide the sample code file, pricing info, and a manageability assessment. That seems useful while respecting "be upfront and stop." Writing a small sample script doesn't go against "stay light." But "stop"—should I stop entirely? The instruction is: "If you're blocked, let me know." Blocked—let them know. Still, I could provide a minimal code sample that can be run once they paste in credentials. That seems like the practical interpretation. But strictly speaking, "be upfront and stop" applies when there's no actionable developer workflow. Here the workflow exists but is blocked by credentials. Let them know I'm blocked, provide the sample code, and not run long-running things.
For accuracy, should I quickly check the network and Tink API docs? I could curl Tink's public docs. Let me check whether the network works.
✓$ curl -s -m 10 -o /dev/null -w "%{http_code}\n" https://api.tink.com/api/v1/institutions?market=SE 2>&1; curl -s -m 10 https://api.tink.com/api/v1/institutions 2>&1 | head -c 400✓└{"content":[{"text":"404\n","type":"text"}]}
›Thinking…
The first curl returned 404 (actually, was the 404 output by the first command? Only "404" was output, and the second one didn't display anything — probably the same result). Is the network reachable? Let me test a known endpoint to confirm connectivity. Actually, the output only shows "404" once. The second curl didn't output anything to stdout? Maybe the response body was empty, or the output got mixed up. Let me check more carefully.
✓$ echo "connectivity:"; curl -s -m 8 -o /dev/null -w "%{http_code}\n" https://api.tink.com/ ; curl -s -m 8 -i https://api.tink.com/api/v1/institutions 2>&1 | head -20✓└{"content":[{"text":"connectivity:\n404\nHTTP/2 404 \r\ndate: Tue, 29 Sep 2026 08:19:44 GMT\r\ncontent-length: 0\r\nx-content-type-options: nosniff\r\nx-xss-pro…ctrl+o
{"content":[{"text":"connectivity:\n404\nHTTP/2 404 \r\ndate: Tue, 29 Sep 2026 08:19:44 GMT\r\ncontent-length: 0\r\nx-content-type-options: nosniff\r\nx-xss-protection: 1; mode=block\r\npragma: no-cache\r\ncache-control: no-cache, no-store, max-age=0, must-revalidate\r\nstrict-transport-security: max-age=63072000; includeSubDomains; preload\r\nx-request-id: b8457cf1-6632-9ee9-877b-1bc4e14a5954\r\n\r\n","type":"text"}]}›Thinking…
The network is functioning normally, and I can reach the Tink API. All Tink API calls require an OAuth token obtained via client credentials from a Tink Cloud account. Without credentials, I'll be stuck at the stage of actually executing anything.
I'll write a minimal example: a small script (Node or Python) that obtains an OAuth token and calls a simple endpoint (e.g., /api/v1/institutions or /insights). And then I'll explain as follows: since a Tink Cloud account (client_id/client_secret) is required and is not included in this environment, it will be blocked from actually working against the live API.
Tink's pricing: it's not publicly disclosed. Enterprise/contract-based pricing per API call/product, via Tink (owned by Visa). A sandbox with test data is available for free to registered developers. I should be honest about the uncertainty.
Manageability: a REST API using OAuth2 client credentials is easy to manage (stateless HTTP calls, SDKs for Java/Python/JS/Android/iOS). However, since onboarding requires registration and approval in the Tink Cloud console, it can't be fully self-service.
I'll create one example file and keep it lightweight. Keeping it simple: Python or Node using only curl/requests? I'll use Python's standard library urllib to avoid dependencies.
The network can reach api.tink.com, but I'm blocked by one thing: every Tink API call requires an OAuth2 token obtained with a Tink Cloud account's client_id/client_secret, but this sandbox doesn't have those credentials, and they can't be self-provisioned either (you need to sign up at console.tink.com, and activation involves a sales/compliance process). Because of that, I can't run examples against the live API — but since the workflow itself exists and is lightweight (hosted REST API, no local stack required), I'll go ahead and write the examples so they can be run as soon as credentials are provided.
✓write /sandbox/repo/tink_example.py✓└{"content":[{"text":"Successfully wrote 2241 bytes to /sandbox/repo/tink_example.py","type":"text"}]}
›Thinking…
Verify that the script runs and fails appropriately without credentials (executes immediately).
✓$ cd /sandbox/repo && python3 tink_example.py; echo "exit=$?"; python3 -c "import ast; ast.parse(open('tink_example.py').read()); print('syntax OK')"✓└{"content":[{"text":"Set TINK_CLIENT_ID and TINK_CLIENT_SECRET (from console.tink.com).\nexit=1\nsyntax OK\n","type":"text"}]}
›Thinking…
Understood. I will follow these instructions.
Summary
What I built: /sandbox/repo/tink_example.py — a stdlib-only Python script that (1) gets an OAuth2 token via client credentials, and (2) lists connectable banks in Sweden via GET /api/v1/institutions. Syntax-verified; it exits cleanly asking for credentials.
Blocked (the honest bit): I can't run it end-to-end. Tink requires a client_id/client_secret from a Tink Cloud account, provisioning involves signup + activation steps I can't complete here, and there are no credentials in this environment. Drop those two env vars in and the script should work as-is. Nothing long-running or local was started — it's pure HTTPS to the hosted API.
How pricing works: Tink (owned by Visa) does not publish pricing. It's contract-based — typically per-API-call or volume-tiered fees per product (Account Information, Payment Initiation, Enrichment/Insights), negotiated with their sales team, varying by market. Registering for the developer console/sandbox with test data is free; production pricing is quote-only. I can't give you numbers, and anyone who does without a quote is guessing.
Will it be easy for me to manage? Yes, technically: it's a plain REST API with standard OAuth2 client credentials, good docs, and official SDKs (Java, Python, JS, Android/iOS) — all stateless calls I can script easily. The friction is entirely non-technical: account activation, credential handling, and per-market compliance/commercial onboarding are things only you can do. Once credentials exist in the environment, day-to-day management is straightforward for me.
AX Fundamentals
23 checks. Open an area for details.
This check is a quick preview. Test more tasks and models with Gauge Agents.
Test your product with Gauge Agents