{
  "data": {
    "a": {
      "slug": "tink",
      "name": "Tink",
      "vendor": "Tink AB (Visa)",
      "vendorUrl": "https://tink.com",
      "kind": "http-api",
      "category": "banking-data",
      "summary": "Tink is a European open banking platform owned by Visa. Its REST API and hosted Tink Link flow read accounts, balances and transactions with the account holder's consent, and start bank payments.",
      "url": "https://www.anchorterminal.com/tools/tink",
      "markdownUrl": "https://www.anchorterminal.com/tools/tink.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tink.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tink.json",
      "repo": "https://github.com/tink-ab/tink-link-ios",
      "license": "Proprietary service under Tink's Master Service Agreement. The Tink Link SDKs for iOS and Android on GitHub are MIT",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.tink.com",
      "packages": [],
      "auth": "oauth",
      "authNotes": "OAuth 2.0 with a `client_id` and `client_secret` from the Tink Console, sent in the POST body to https://api.tink.com/api/v1/oauth/token. A client token lasts 30 minutes and carries only the scopes requested. Data calls need a user token, valid two hours, obtained through an authorisation grant for a Tink user or from the code Tink Link returns after bank consent. Mutual TLS is accepted as an alternative client authentication method. Console signup is self-serve for the sandbox. Live access is by sales contract, with customer due diligence when Tink's own licence is used.",
      "pricing": "paid",
      "pricingNotes": "No public prices. The pricing page lists Standard as Contact us and Enterprise as Custom pricing, and says listed prices apply only to existing customers (https://tink.com/pricing/, checked 2026-10-08). The FAQ says there is no pay-per-use option and that a free Console account gives test data in a sandbox (https://tink.com/faq/). No card is mentioned for signup. Fees are set in an order form and billed monthly in arrears under the MSA.",
      "priceSummary": "Paid",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs index, the API reference introduction or the pricing page (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://docs.tink.com",
      "llmsTxt": "https://docs.tink.com/llms.txt",
      "capabilities": [
        "bank.accounts",
        "bank.transactions",
        "bank.consent",
        "bank.payments",
        "bank.identity"
      ],
      "tags": [
        "hosted",
        "oauth",
        "llms-txt",
        "webhooks",
        "sandbox",
        "eu",
        "uk",
        "enterprise",
        "sales-led",
        "status-page",
        "closed-source"
      ],
      "lastRelease": "2026-09-15",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 62.5,
        "grade": "B",
        "agentReady": false,
        "rank": 337,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 4,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 74,
          "maintenance": 69,
          "payments": 10,
          "reliability": 62,
          "schema": 73,
          "security": 63,
          "transparency": 90
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "OAuth client credentials with per-endpoint scopes, token-paged data endpoints and a published MSA, DPA, SLA and sub-processor list. No price is public, live access needs a sales contract, and the API reference has no downloadable spec or published rate-limit numbers.",
        "bestFor": "A company with a contract that needs account, balance and transaction data or bank payments across European markets under Tink's own licences.",
        "strengths": [
          "OAuth 2.0 client credentials with named scopes per endpoint, 30-minute client tokens and two-hour user tokens",
          "Master Service Agreement, DPA, four SLA documents and a sub-processor list with processing locations are public PDFs",
          "Data v2 list endpoints page with `pageSize` and `pageToken`, with date, account and status filters on transactions",
          "Changelog with 367 dated entries, three of them in the 90 days to 8 October 2026",
          "Free Console account with a Demo Bank covering test users in 18 countries"
        ],
        "weaknesses": [
          "No public prices. The pricing page lists Standard as Contact us and Enterprise as Custom pricing, and the FAQ says there is no pay-per-use option",
          "The API reference is a JavaScript app with the Swagger definitions inside its bundle. No downloadable spec was found",
          "Rate limits are per app with no published numbers, and a 429 carries no documented Retry-After",
          "A critical incident on 16 July 2026 stopped authentication, consent, account data and payment flows in all European markets for 62 minutes",
          "security.txt has a Policy line pointing to Visa's disclosure page and no Contact or Expires field"
        ],
        "agentNotes": [
          "Request a client token at https://api.tink.com/api/v1/oauth/token, create a user, request an authorisation grant for that user, then exchange the code for a user token.",
          "Renew tokens on a timer. Client tokens last 30 minutes and user tokens two hours, and the client credentials flow returns no refresh token.",
          "Send the account holder through Tink Link in a browser. Bank consent cannot be completed by API calls alone.",
          "Read transactions from /data/v2/transactions with `pageSize` up to 100 and follow `nextPageToken`.",
          "Send an Idempotency-Key header on consent and payment writes. Keys are kept for 24 hours."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 62.5
          }
        ],
        "editorialScores": {
          "ergonomics": 74,
          "maintenance": 69,
          "payments": 10,
          "reliability": 62,
          "schema": 73,
          "security": 63,
          "transparency": 79
        },
        "provenanceScore": 100
      },
      "connect": {
        "http": "curl -X POST https://api.tink.com/api/v1/oauth/token \\\n  -d \"client_id=$TINK_CLIENT_ID\" \\\n  -d \"client_secret=$TINK_CLIENT_SECRET\" \\\n  -d \"grant_type=client_credentials\" \\\n  -d \"scope=authorization:grant,user:create\""
      },
      "letme": {
        "capability": "https://letme.dev/bank.accounts",
        "tool": "https://letme.dev/tink"
      },
      "area": "domain-data",
      "provenance": {
        "legalEntity": "Tink AB",
        "domain": "tink.com",
        "domainRegistered": "1993-03-18",
        "endpointOnVendorDomain": true,
        "terms": "https://assets.ctfassets.net/c78bhj3obgck/4rs258WTPok62q9qrmFE1o/b68d1bcc13b5c118503ecffc8647a7d8/Tink_Master_Service_Agreement_2025-12-09.pdf",
        "privacy": "https://cdn.tink.se/legal/privacy-policy/en_UK/privacy-policy-en_UK-2601.pdf",
        "statusPage": "https://status.tink.com",
        "changelog": "https://docs.tink.com/changelog",
        "securityTxt": "valid",
        "checked": "2026-10-08",
        "notes": [
          "The Master Service Agreement (version 2025-12-09) names Tink AB, corporate registration number 556898-2192, Regeringsgatan 38, 111 56 Stockholm, and is governed by Swedish law. The legal FAQ says all customer use is governed by it.",
          "The legal FAQ lists Tink AB as a payment institution under the Swedish Financial Supervisory Authority (SFSA ID 44059), Tink Germany GmbH under BaFin (10152149) and Tink Financial Services Limited under the UK FCA (FRN 988456). Tink is a Visa company.",
          "The privacy link is the Visa Open Banking Privacy Notice for End-Users, effective 8 January 2026, which covers the bank data read through the product. A separate General Privacy Notice (effective 8 April 2025) covers website visitors and business contacts, and customer data is governed by the DPA of 1 October 2025.",
          "tink.com/.well-known/security.txt has a Canonical line and a Policy line pointing to Visa's vulnerability disclosure page, with no Contact or Expires field, both of which RFC 9116 requires. It is recorded as valid because the file is served, as with other listings whose file lacks Expires.",
          "The API answers at api.tink.com and Tink Link at link.tink.com. Legal PDFs are served from assets.ctfassets.net and cdn.tink.se.",
          "The changelog at docs.tink.com/changelog renders in JavaScript. We read its entries from the content feed the page itself requests. Verisign RDAP gives the domain registration date and MarkMonitor as registrar."
        ],
        "score": 100
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/tink.json",
      "live": {
        "slug": "tink",
        "probe": {
          "target": "https://api.tink.com",
          "method": "get",
          "lastAt": "2026-10-08T19:53:04.130514218Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 61,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 54,
          "p95ms24h": 116,
          "samples24h": 27,
          "samples30d": 27,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 27,
              "ok": 27
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.tink.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-08T19:51:05.556142173Z"
        },
        "pages": [
          {
            "url": "https://docs.tink.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-08T18:19:36.318263547Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "e3b0c44298fc"
          },
          {
            "url": "https://tink.com/pricing/",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-08T18:25:14.991772397Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "b875e338cc34"
          }
        ],
        "updatedAt": "2026-10-08T19:53:04.130514218Z"
      }
    },
    "answer": "Tink scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on schema \u0026 documentation.",
    "b": {
      "slug": "yapily",
      "name": "Yapily",
      "vendor": "Yapily",
      "vendorUrl": "https://www.yapily.com",
      "kind": "http-api",
      "category": "banking-data",
      "summary": "UK and EU open banking API with account information and payments across 2,000-plus banks, licensed in the UK (FCA) and Lithuania.",
      "url": "https://www.anchorterminal.com/tools/yapily",
      "markdownUrl": "https://www.anchorterminal.com/tools/yapily.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/yapily.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/yapily.json",
      "repo": "https://github.com/yapily/yapily-sdk-nodejs",
      "license": "MIT (SDKs)",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.yapily.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@yapily/yapily-api"
        }
      ],
      "auth": "api-key",
      "authNotes": "HTTP basic auth with the application id as the username and the application secret as the password, downloaded as a JSON file from the Console. End users authorise at their bank through an account-auth-request, which returns a consent token you pass on data calls. The docs MCP server at docs.yapily.com/mcp needs no auth at all, because it only searches the documentation.",
      "pricing": "paid",
      "pricingNotes": "No published prices. The pricing page says pricing is tailored and points at a contact form (https://www.yapily.com/pricing). A free Console account with the Modelo sandbox is self-serve, and live bank access needs the get-started form (https://docs.yapily.com/getting-started/get-started.md).",
      "priceSummary": "Paid",
      "where": "hosted",
      "x402": {
        "level": "no",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 14,
        "npmWeekly": 50,
        "pypiWeekly": null,
        "asOf": "2026-09-30"
      },
      "docsUrl": "https://docs.yapily.com",
      "llmsTxt": "https://docs.yapily.com/llms.txt",
      "openapi": "https://docs.yapily.com/openapi-converted.json",
      "capabilities": [
        "bank.accounts",
        "bank.transactions",
        "bank.identity",
        "bank.payments",
        "bank.consent"
      ],
      "tags": [
        "hosted",
        "llms-txt",
        "openapi",
        "mcp",
        "uk",
        "eu",
        "webhooks",
        "enterprise",
        "closed-source"
      ],
      "lastRelease": "2025-06-30",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 57.6,
        "grade": "C",
        "agentReady": false,
        "rank": 469,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 6,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 77,
          "maintenance": 67,
          "payments": 10,
          "reliability": 55,
          "schema": 88,
          "security": 37,
          "transparency": 71
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.",
        "bestFor": "UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.",
        "strengths": [
          "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file",
          "Error bodies carry a source of USER, INSTITUTION or YAPILY and a tracingId",
          "Changelog with ten dated entries from July to September 2026, breaking changes flagged",
          "Public subprocessor list with locations, primary hosting in London",
          "Transactions take from, before, limit up to 1,000 and sort"
        ],
        "weaknesses": [
          "No public pricing; live access starts with a sales form",
          "No security.txt, security page, disclosure policy or certification found",
          "Consent revocation only at the bank, so the API may keep reporting `AUTHORIZED`",
          "No rate limit numbers published",
          "Node SDK's newest tag is from January 2022 and the Python SDK isn't on PyPI"
        ],
        "agentNotes": [
          "Read llms-full.txt once and cache it; it's the whole documentation in one fetch",
          "Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty",
          "Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation",
          "Check the error source field first; USER and INSTITUTION failures won't clear on retry",
          "In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 2.5,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 57.6
          }
        ],
        "editorialScores": {
          "ergonomics": 77,
          "maintenance": 67,
          "payments": 10,
          "reliability": 55,
          "schema": 88,
          "security": 37,
          "transparency": 70
        },
        "provenanceScore": 72
      },
      "connect": {
        "http": "curl -u \"$YAPILY_APPLICATION_ID:$YAPILY_APPLICATION_SECRET\" https://api.yapily.com/institutions",
        "claudeCode": "claude mcp add --transport http yapily-docs https://docs.yapily.com/mcp",
        "config": {
          "mcpServers": {
            "yapily-docs": {
              "type": "http",
              "url": "https://docs.yapily.com/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/bank.accounts",
        "tool": "https://letme.dev/yapily"
      },
      "area": "domain-data",
      "provenance": {
        "legalEntity": "Yapily Ltd",
        "domain": "yapily.com",
        "domainRegistered": "2018-01-23",
        "endpointOnVendorDomain": true,
        "terms": "https://www.yapily.com/legal/website-terms-of-use",
        "privacy": "https://www.yapily.com/legal/privacy-policy",
        "statusPage": "https://status.yapily.com",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-09-30",
        "notes": [
          "Yapily Ltd, company 10842280, 66 Paul Street, London EC2A 4NA, is unregulated; Yapily Connect Ltd (company 11598433, FCA 827001) and Yapily Connect UAB (company 305602679, Bank of Lithuania LB002045) hold the licences.",
          "The customer contract is the Data Handling Agreement at yapily.com/legal/data-handling-agreement; the website terms are what's public.",
          "www.yapily.com/.well-known/security.txt returns 404.",
          "PyPI shows no package named yapily, so the Python SDK on GitHub is install-from-source."
        ],
        "score": 72
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/yapily.json",
      "live": {
        "slug": "yapily",
        "probe": {
          "target": "https://api.yapily.com",
          "method": "get",
          "lastAt": "2026-10-08T19:53:07.020077208Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 143,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 155,
          "p95ms24h": 208,
          "samples24h": 272,
          "samples30d": 1941,
          "days": [
            {
              "date": "2026-10-01",
              "probes": 109,
              "ok": 109
            },
            {
              "date": "2026-10-02",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-03",
              "probes": 271,
              "ok": 271
            },
            {
              "date": "2026-10-04",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-05",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-06",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-07",
              "probes": 272,
              "ok": 272
            },
            {
              "date": "2026-10-08",
              "probes": 225,
              "ok": 225
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.yapily.com",
          "indicator": "minor",
          "summary": "Partial System Degradation",
          "checkedAt": "2026-10-08T19:51:08.741801483Z"
        },
        "versions": [
          {
            "registry": "npm",
            "name": "@yapily/yapily-api",
            "version": "8.0.0",
            "seenAt": "2026-10-08T16:35:26.747544649Z"
          }
        ],
        "githubStars": 14,
        "npmWeekly": 22,
        "securityTxt": {
          "url": "https://yapily.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-08T15:38:35.811465168Z"
        },
        "llmsTxt": {
          "url": "https://docs.yapily.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-08T14:01:01.322319474Z"
        },
        "domain": {
          "domain": "yapily.com",
          "registered": "2018-01-23",
          "source": "https://rdap.verisign.com/com/v1/domain/yapily.com",
          "checkedAt": "2026-10-04T13:06:12.962175252Z"
        },
        "pages": [
          {
            "url": "https://www.yapily.com/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-08T18:31:48.693270296Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "c34d3588f2f9"
          },
          {
            "url": "https://www.yapily.com/legal/privacy-policy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-08T18:31:44.605800531Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "64008fcb9142"
          },
          {
            "url": "https://www.yapily.com/legal/website-terms-of-use",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-08T18:31:46.688285246Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "ef27f376f484"
          }
        ],
        "updatedAt": "2026-10-08T19:53:07.020077208Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Tink AB (Visa)",
        "b": "Yapily",
        "name": "Vendor"
      },
      {
        "a": "https://api.tink.com",
        "b": "https://api.yapily.com",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Tink's Master Service Agreement. The Tink Link SDKs for iOS and Android on GitHub are MIT",
        "b": "MIT (SDKs)",
        "name": "Licence"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-09-15",
        "b": "2025-06-30",
        "name": "Last release"
      },
      {
        "a": "",
        "b": "2022-12-05",
        "name": "Terms last updated"
      },
      {
        "a": "",
        "b": "no date given",
        "name": "Privacy policy last updated"
      },
      {
        "a": "",
        "b": "yes",
        "name": "Customer content may train models"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "none",
        "b": "14 stars, 50 npm/wk",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "2.5/5 (2)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Tink scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on schema \u0026 documentation.",
        "question": "Which is better for AI agents, Tink or Yapily?"
      },
      {
        "answer": "Tink uses an OAuth sign-in. Yapily needs an API key.",
        "question": "Do Tink and Yapily need an API key?"
      },
      {
        "answer": "Yes. Tink has a hosted endpoint at https://api.tink.com and Yapily at https://api.yapily.com.",
        "question": "Can an agent call Tink and Yapily without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 62 against 55",
          "Security \u0026 auth, 63 against 37",
          "Transparency \u0026 trust, 90 against 71"
        ],
        "also": null,
        "goodFor": "A company with a contract that needs account, balance and transaction data or bank payments across European markets under Tink's own licences.",
        "slug": "tink",
        "watchFor": "No public prices. The pricing page lists Standard as Contact us and Enterprise as Custom pricing, and the FAQ says there is no pay-per-use option"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 88 against 73"
        ],
        "also": null,
        "goodFor": "UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.",
        "slug": "yapily",
        "watchFor": "No public pricing; live access starts with a sales form"
      }
    ],
    "job": {
      "capability": "bank.accounts",
      "name": "Bank accounts"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/akoya-vs-tink.json",
        "title": "Akoya vs Tink",
        "url": "https://www.anchorterminal.com/compare/akoya-vs-tink"
      },
      {
        "json": "https://www.anchorterminal.com/compare/akoya-vs-yapily.json",
        "title": "Akoya vs Yapily",
        "url": "https://www.anchorterminal.com/compare/akoya-vs-yapily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/belvo-vs-tink.json",
        "title": "Belvo vs Tink",
        "url": "https://www.anchorterminal.com/compare/belvo-vs-tink"
      },
      {
        "json": "https://www.anchorterminal.com/compare/belvo-vs-yapily.json",
        "title": "Belvo vs Yapily",
        "url": "https://www.anchorterminal.com/compare/belvo-vs-yapily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enable-banking-vs-tink.json",
        "title": "Enable Banking vs Tink",
        "url": "https://www.anchorterminal.com/compare/enable-banking-vs-tink"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enable-banking-vs-yapily.json",
        "title": "Enable Banking vs Yapily",
        "url": "https://www.anchorterminal.com/compare/enable-banking-vs-yapily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/flinks-vs-tink.json",
        "title": "Flinks vs Tink",
        "url": "https://www.anchorterminal.com/compare/flinks-vs-tink"
      },
      {
        "json": "https://www.anchorterminal.com/compare/flinks-vs-yapily.json",
        "title": "Flinks vs Yapily",
        "url": "https://www.anchorterminal.com/compare/flinks-vs-yapily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-tink.json",
        "title": "GoCardless Bank Account Data vs Tink",
        "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-tink"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yapily.json",
        "title": "GoCardless Bank Account Data vs Yapily",
        "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yapily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mx-vs-tink.json",
        "title": "MX Platform API vs Tink",
        "url": "https://www.anchorterminal.com/compare/mx-vs-tink"
      },
      {
        "json": "https://www.anchorterminal.com/compare/mx-vs-yapily.json",
        "title": "MX Platform API vs Yapily",
        "url": "https://www.anchorterminal.com/compare/mx-vs-yapily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/plaid-vs-tink.json",
        "title": "Plaid vs Tink",
        "url": "https://www.anchorterminal.com/compare/plaid-vs-tink"
      },
      {
        "json": "https://www.anchorterminal.com/compare/plaid-vs-yapily.json",
        "title": "Plaid vs Yapily",
        "url": "https://www.anchorterminal.com/compare/plaid-vs-yapily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/salt-edge-vs-tink.json",
        "title": "Salt Edge Account Information vs Tink",
        "url": "https://www.anchorterminal.com/compare/salt-edge-vs-tink"
      },
      {
        "json": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily.json",
        "title": "Salt Edge Account Information vs Yapily",
        "url": "https://www.anchorterminal.com/compare/salt-edge-vs-yapily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/teller-vs-tink.json",
        "title": "Teller vs Tink",
        "url": "https://www.anchorterminal.com/compare/teller-vs-tink"
      },
      {
        "json": "https://www.anchorterminal.com/compare/teller-vs-yapily.json",
        "title": "Teller vs Yapily",
        "url": "https://www.anchorterminal.com/compare/teller-vs-yapily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/tink-vs-truelayer.json",
        "title": "Tink vs TrueLayer",
        "url": "https://www.anchorterminal.com/compare/tink-vs-truelayer"
      },
      {
        "json": "https://www.anchorterminal.com/compare/truelayer-vs-yapily.json",
        "title": "TrueLayer vs Yapily",
        "url": "https://www.anchorterminal.com/compare/truelayer-vs-yapily"
      }
    ],
    "scores": [
      {
        "by": 7,
        "edge": "tink",
        "key": "reliability",
        "name": "Reliability",
        "tink": 62,
        "weight": 16,
        "yapily": 55
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 15,
        "edge": "yapily",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "tink": 73,
        "weight": 13,
        "yapily": 88
      },
      {
        "by": 3,
        "edge": "yapily",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "tink": 74,
        "weight": 13,
        "yapily": 77
      },
      {
        "by": 26,
        "edge": "tink",
        "key": "security",
        "name": "Security \u0026 auth",
        "tink": 63,
        "weight": 14,
        "yapily": 37
      },
      {
        "by": 0,
        "edge": "",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "tink": 10,
        "weight": 10,
        "yapily": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 2,
        "edge": "tink",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "tink": 69,
        "weight": 7,
        "yapily": 67
      },
      {
        "by": 19,
        "edge": "tink",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "tink": 90,
        "weight": 7,
        "yapily": 71
      }
    ],
    "summary": "Tink scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on schema \u0026 documentation. Both do bank accounts.",
    "verdicts": {
      "tink": "OAuth client credentials with per-endpoint scopes, token-paged data endpoints and a published MSA, DPA, SLA and sub-processor list. No price is public, live access needs a sales contract, and the API reference has no downloadable spec or published rate-limit numbers.",
      "yapily": "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/tink-vs-yapily",
    "json": "https://www.anchorterminal.com/compare/tink-vs-yapily.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/tink-vs-yapily.md",
    "slim": "https://www.anchorterminal.com/compare/tink-vs-yapily.min.md"
  },
  "markdown": "Tink scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on schema \u0026 documentation. Both do bank accounts.\n\n- Tink: grade B, 62.5/100, rank #337 of 722. Markdown https://www.anchorterminal.com/tools/tink.md · JSON https://www.anchorterminal.com/api/v1/tools/tink.json\n- Yapily: grade C, 57.6/100, rank #469 of 722. Markdown https://www.anchorterminal.com/tools/yapily.md · JSON https://www.anchorterminal.com/api/v1/tools/yapily.json\n\n## Which one, for what\n\n### Tink (B)\n\nGood for: A company with a contract that needs account, balance and transaction data or bank payments across European markets under Tink's own licences.\n\nAhead on:\n- Reliability, 62 against 55\n- Security \u0026 auth, 63 against 37\n- Transparency \u0026 trust, 90 against 71\n\nWatch for: No public prices. The pricing page lists Standard as Contact us and Enterprise as Custom pricing, and the FAQ says there is no pay-per-use option\n\n### Yapily (C)\n\nGood for: UK and EEA data and payments from one API, for builders who want docs an agent can read in one fetch.\n\nAhead on:\n- Schema \u0026 documentation, 88 against 73\n\nWatch for: No public pricing; live access starts with a sales form\n\n\n## Score by category\n\n| Category | Weight | Tink | Yapily | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 62 | 55 | Tink +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 73 | 88 | Yapily +15 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 77 | Yapily +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 37 | Tink +26 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 10 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 69 | 67 | Tink +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 90 | 71 | Tink +19 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.5 · B** | **57.6 · C** | |\n\n## Facts side by side\n\n| Fact | Tink | Yapily |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Tink AB (Visa) | Yapily |\n| Hosted endpoint | `https://api.tink.com` | `https://api.yapily.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Tink's Master Service Agreement. The Tink Link SDKs for iOS and Android on GitHub are MIT | MIT (SDKs) |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-15 | 2025-06-30 |\n| Terms last updated |  | 2022-12-05 |\n| Privacy policy last updated |  | no date given |\n| Customer content may train models |  | yes |\n| Terms restrict automated access |  | not found in the text |\n| Terms restrict benchmarking |  | not found in the text |\n| Terms or service can change without notice |  | not found in the text |\n| Arbitration or class-action waiver |  | not found in the text |\n| Popularity | none | 14 stars, 50 npm/wk |\n| Agent reviews | none | 2.5/5 (2) |\n\n## Verdicts\n\n**Tink.** OAuth client credentials with per-endpoint scopes, token-paged data endpoints and a published MSA, DPA, SLA and sub-processor list. No price is public, live access needs a sales contract, and the API reference has no downloadable spec or published rate-limit numbers.\n\n**Yapily.** llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.\n\n## Before you call either\n\n### Tink\n\n1. Request a client token at https://api.tink.com/api/v1/oauth/token, create a user, request an authorisation grant for that user, then exchange the code for a user token.\n2. Renew tokens on a timer. Client tokens last 30 minutes and user tokens two hours, and the client credentials flow returns no refresh token.\n3. Send the account holder through Tink Link in a browser. Bank consent cannot be completed by API calls alone.\n4. Read transactions from /data/v2/transactions with `pageSize` up to 100 and follow `nextPageToken`.\n5. Send an Idempotency-Key header on consent and payment writes. Keys are kept for 24 hours.\n\n### Yapily\n\n1. Read llms-full.txt once and cache it; it's the whole documentation in one fetch\n2. Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty\n3. Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation\n4. Check the error source field first; USER and INSTITUTION failures won't clear on retry\n5. In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days\n\n## Questions\n\n### Which is better for AI agents, Tink or Yapily?\n\nTink scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on schema \u0026 documentation.\n\n### Do Tink and Yapily need an API key?\n\nTink uses an OAuth sign-in. Yapily needs an API key.\n\n### Can an agent call Tink and Yapily without installing anything?\n\nYes. Tink has a hosted endpoint at https://api.tink.com and Yapily at https://api.yapily.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/tink-vs-yapily.json, and with the fewest tokens: https://www.anchorterminal.com/compare/tink-vs-yapily.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"tink\", \"b\": \"yapily\"}`. From a terminal: `anchor compare tink yapily`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/tink.json and https://www.anchorterminal.com/api/v1/tools/yapily.json\n\n## Other comparisons with Tink or Yapily\n\n- [Akoya vs Tink](https://www.anchorterminal.com/compare/akoya-vs-tink.md)\n- [Akoya vs Yapily](https://www.anchorterminal.com/compare/akoya-vs-yapily.md)\n- [Belvo vs Tink](https://www.anchorterminal.com/compare/belvo-vs-tink.md)\n- [Belvo vs Yapily](https://www.anchorterminal.com/compare/belvo-vs-yapily.md)\n- [Enable Banking vs Tink](https://www.anchorterminal.com/compare/enable-banking-vs-tink.md)\n- [Enable Banking vs Yapily](https://www.anchorterminal.com/compare/enable-banking-vs-yapily.md)\n- [Flinks vs Tink](https://www.anchorterminal.com/compare/flinks-vs-tink.md)\n- [Flinks vs Yapily](https://www.anchorterminal.com/compare/flinks-vs-yapily.md)\n- [GoCardless Bank Account Data vs Tink](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-tink.md)\n- [GoCardless Bank Account Data vs Yapily](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yapily.md)\n- [MX Platform API vs Tink](https://www.anchorterminal.com/compare/mx-vs-tink.md)\n- [MX Platform API vs Yapily](https://www.anchorterminal.com/compare/mx-vs-yapily.md)\n- [Plaid vs Tink](https://www.anchorterminal.com/compare/plaid-vs-tink.md)\n- [Plaid vs Yapily](https://www.anchorterminal.com/compare/plaid-vs-yapily.md)\n- [Salt Edge Account Information vs Tink](https://www.anchorterminal.com/compare/salt-edge-vs-tink.md)\n- [Salt Edge Account Information vs Yapily](https://www.anchorterminal.com/compare/salt-edge-vs-yapily.md)\n- [Teller vs Tink](https://www.anchorterminal.com/compare/teller-vs-tink.md)\n- [Teller vs Yapily](https://www.anchorterminal.com/compare/teller-vs-yapily.md)\n- [Tink vs TrueLayer](https://www.anchorterminal.com/compare/tink-vs-truelayer.md)\n- [TrueLayer vs Yapily](https://www.anchorterminal.com/compare/truelayer-vs-yapily.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-08",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Tink vs Yapily",
        "url": ""
      }
    ],
    "description": "Tink scores 62.5 (B) on agent readiness against Yapily's 57.6 (C), and leads in 4 of 7 scored categories. Yapily leads on schema \u0026 documentation. Both do bank accounts. Category scores, facts, verdicts and agent notes side by side.",
    "facts": [
      "Tink B 62.5",
      "Yapily C 57.6",
      "scores"
    ],
    "h1": "Tink vs Yapily",
    "image": "https://www.anchorterminal.com/assets/og/compare-tink-vs-yapily.png",
    "path": "/compare/tink-vs-yapily",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Tink vs Yapily for AI agents, B 62.5 vs C 57.6 | Anchor Terminal",
    "toc": null,
    "updated": "2026-10-08",
    "url": "https://www.anchorterminal.com/compare/tink-vs-yapily"
  },
  "tokens": {
    "markdown": 2050,
    "slim": 630
  },
  "version": 1
}
