{
  "data": {
    "a": {
      "slug": "flinks",
      "name": "Flinks",
      "vendor": "Flinks Technology Inc. (National Bank of Canada)",
      "vendorUrl": "https://www.flinks.com",
      "kind": "http-api",
      "category": "banking-data",
      "summary": "Flinks is a Canadian bank-data aggregator owned by National Bank of Canada. Its REST API and Flinks Connect widget read accounts, balances, transactions and holder details from Canadian and US institutions with the holder's consent, and start Canadian bank payments.",
      "url": "https://www.anchorterminal.com/tools/flinks",
      "markdownUrl": "https://www.anchorterminal.com/tools/flinks.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/flinks.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/flinks.json",
      "license": "Proprietary service under Flinks' Master Terms and Conditions. No open-source SDK or repository was found",
      "transports": [
        "http"
      ],
      "packages": [],
      "auth": "api-key",
      "authNotes": "Two static keys issued by Flinks at onboarding. The secret key goes in the `flinks-auth-key` header of `/GenerateAuthorizeToken` and returns a single-use authorise token that expires after 15 minutes. Data endpoints take the `requestId` from `/Authorize` plus an `x-api-key` header. Neither key expires, and no scopes were found. Webhooks are signed with HMAC-SHA256 in a `flinks-authenticity-key` header. Flinks Outbound, the open banking product, uses an OAuth 2.0 authorisation code flow with a `client_id` and `client_secret` and Bearer tokens. Sandbox keys for the shared Toolbox instance are published in the docs. Production keys come from a Flinks representative after a contract.",
      "pricing": "paid",
      "pricingNotes": "Plans with a monthly minimum and a one-year term (https://www.flinks.com/pricing, checked 2026-10-08). Connect is $500 a month for 200 unique connections, $1,250 for 1,100, and custom from 20,000. Enrich is $250 a month for 100 API calls and $1,100 for 1,250. Upload is $500 a month for 20 documents and $1,500 for 100. Flinks Pay is quoted by sales. The page does not state the currency or the overage rates, and says there is no pay-as-you-go plan and no self-serve trial. The Toolbox sandbox is free, with keys published in the docs and no card.",
      "priceSummary": "Paid",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs index, the ten OpenAPI files 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.flinks.com",
      "llmsTxt": "https://docs.flinks.com/llms.txt",
      "openapi": "https://docs.flinks.com/openapi.yaml",
      "capabilities": [
        "bank.accounts",
        "bank.transactions",
        "bank.identity",
        "bank.payments",
        "bank.consent"
      ],
      "tags": [
        "hosted",
        "api-key",
        "openapi",
        "llms-txt",
        "webhooks",
        "sandbox",
        "canada",
        "us",
        "enterprise",
        "sales-led",
        "status-page",
        "closed-source"
      ],
      "lastRelease": "2026-09-01",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 52.7,
        "grade": "D",
        "agentReady": false,
        "rank": 559,
        "ranked": true,
        "rankOf": 722,
        "categoryRank": 7,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 54,
          "maintenance": 31,
          "payments": 25,
          "reliability": 53,
          "schema": 83,
          "security": 50,
          "transparency": 60
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "Ten public OpenAPI files, an llms.txt index with Markdown twins and published sandbox keys let an agent start without a signup. Live access needs a one-year contract from $500 a month, keys never expire, no rate-limit numbers are published, and the status page logged 77 incidents in 90 days.",
        "bestFor": "A lender or fintech with steady volume that needs Canadian bank data, income and lending attributes, PDF statements or Canadian bank payments.",
        "strengths": [
          "Ten OpenAPI 3.0 files are public at docs.flinks.com, 85 operations in all, with the main Connect and Enrich file holding 34",
          "Shared sandbox keys for the Toolbox instance are published in the docs, so test calls need no account",
          "llms.txt lists 216 pages with Markdown twins, and the docs add a skill file and a read-only documentation MCP server",
          "Plan prices are public. Connect starts at $500 a month for 200 unique connections, with no integration or platform fee",
          "Each instance is hosted in the country it serves, Canada or the US, and `/DeleteCard` deletes all data held for a connection"
        ],
        "weaknesses": [
          "Live access needs a contract with a monthly minimum and a one-year term. The pricing page says there is no pay-as-you-go plan or self-serve trial",
          "The secret key, `x-api-key` and HMAC secret do not expire, and no scopes or rotation steps were found for the Connect API",
          "No rate-limit numbers are published, and `TOO_MANY_REQUESTS` is documented under HTTP 401 with no Retry-After",
          "status.flinks.com lists 77 incidents in the 90 days to 8 October 2026, 16 of them on Flinks' own components",
          "`/GetAccountsDetail` returns the whole 90 or 365 days of transactions in one payload with no pagination, and no official SDK was found"
        ],
        "agentNotes": [
          "Call `/GenerateAuthorizeToken` with the secret key in `flinks-auth-key`, then pass the returned token to the Connect iframe or to `/Authorize`. The token is single-use and expires after 15 minutes.",
          "Send the account holder through Flinks Connect in a browser. The API alone cannot complete a first bank login, and sandbox iframes need `demo=true`.",
          "Store the `loginId`. Call `/Authorize` with it and `MostRecentCached: true` for a new `requestId` each session, because `/GetAccountsDetail` consumes the `requestId`.",
          "On a 202 from `/GetAccountsDetail`, poll `/GetAccountsDetailAsync` every 10 seconds for at most 30 minutes, or ask support to enable webhooks.",
          "Route each end user to the instance for their country. A `loginId` from the Canadian instance is not valid on the US one."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 52.7
          }
        ],
        "editorialScores": {
          "ergonomics": 54,
          "maintenance": 31,
          "payments": 25,
          "reliability": 53,
          "schema": 83,
          "security": 50,
          "transparency": 48
        },
        "provenanceScore": 71
      },
      "connect": {
        "http": "curl --request POST \\\n  --url https://toolbox-api.private.fin.ag/v3/{customerId}/BankingServices/GenerateAuthorizeToken \\\n  --header 'Content-Type: application/json' \\\n  --header 'flinks-auth-key: YOUR_SECRET_KEY'",
        "claudeCode": "claude mcp add flinks --transport http https://docs.flinks.com/mcp"
      },
      "letme": {
        "capability": "https://letme.dev/bank.accounts",
        "tool": "https://letme.dev/flinks"
      },
      "area": "domain-data",
      "provenance": {
        "legalEntity": "Flinks Technology Inc.",
        "domain": "flinks.com",
        "domainRegistered": "1997-06-03",
        "endpointOnVendorDomain": false,
        "terms": "https://www.flinks.com/terms-and-conditions",
        "privacy": "https://www.flinks.com/privacy-policy",
        "statusPage": "https://status.flinks.com",
        "changelog": "https://docs.flinks.com/changelog",
        "securityTxt": "none",
        "checked": "2026-10-08",
        "notes": [
          "The terms link is the Master Terms and Conditions, last updated 3 August 2023, which govern use of the Flinks technology under an order form and name Flinks Technology Inc. Service schedules for connectivity, enrichment and upload are separate pages on flinks.com.",
          "The privacy link holds the General Privacy Statement (22 September 2022) and the Services Privacy Statement (19 April 2024) on one page. The Services statement covers bank data read through the product and names National Bank of Canada as Flinks' parent company.",
          "API calls go to https://{instance}-api.private.fin.ag and the widget to https://{instance}-iframe.private.fin.ag. Flinks Outbound answers at ob.flinksapp.com. Neither is under flinks.com, so the endpoint is recorded as off the vendor's domain. We did not confirm the registrant of fin.ag.",
          "flinks.com/.well-known/security.txt, www.flinks.com/.well-known/security.txt and docs.flinks.com/.well-known/security.txt return 404. The security page gives security@flinks.com for vulnerability reports.",
          "status.flinks.com runs on incident.io. changelog.flinks.com redirects to docs.flinks.com/changelog.",
          "Verisign RDAP gives 1997-06-03 as the registration date of flinks.com and GoDaddy.com, LLC as registrar. No street address for the company was found on the pages read."
        ],
        "score": 71
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/flinks.json",
      "live": {
        "slug": "flinks",
        "vendorStatus": {
          "page": "https://status.flinks.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-08T21:57:55.355975731Z"
        },
        "updatedAt": "2026-10-08T21:57:55.355975731Z"
      }
    },
    "answer": "Yapily scores 57.6 (C) on agent readiness against Flinks's 52.7 (D), and leads in 5 of 7 scored categories. Flinks leads on security \u0026 auth and payments \u0026 pricing.",
    "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-08T21:53:39.066964063Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 155,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 155,
          "p95ms24h": 205,
          "samples24h": 270,
          "samples30d": 1962,
          "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": 246,
              "ok": 246
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.yapily.com",
          "indicator": "minor",
          "summary": "Partial System Degradation",
          "checkedAt": "2026-10-08T21:58:19.54894899Z"
        },
        "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-08T21:58:19.54894899Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Flinks Technology Inc. (National Bank of Canada)",
        "b": "Yapily",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://api.yapily.com",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "API key",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Paid",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Flinks' Master Terms and Conditions. No open-source SDK or repository was found",
        "b": "MIT (SDKs)",
        "name": "Licence"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-09-01",
        "b": "2025-06-30",
        "name": "Last release"
      },
      {
        "a": "2023-08-03",
        "b": "2022-12-05",
        "name": "Terms last updated"
      },
      {
        "a": "2022-09-22",
        "b": "no date given",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "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": "Yapily scores 57.6 (C) on agent readiness against Flinks's 52.7 (D), and leads in 5 of 7 scored categories. Flinks leads on security \u0026 auth and payments \u0026 pricing.",
        "question": "Which is better for AI agents, Flinks or Yapily?"
      },
      {
        "answer": "Both need an API key.",
        "question": "Do Flinks and Yapily need an API key?"
      },
      {
        "answer": "No hosted endpoint is listed for Flinks. Yapily has a hosted endpoint at https://api.yapily.com.",
        "question": "Can an agent call Flinks and Yapily without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Security \u0026 auth, 50 against 37",
          "Payments \u0026 pricing, 25 against 10"
        ],
        "also": null,
        "goodFor": "A lender or fintech with steady volume that needs Canadian bank data, income and lending attributes, PDF statements or Canadian bank payments.",
        "slug": "flinks",
        "watchFor": "Live access needs a contract with a monthly minimum and a one-year term. The pricing page says there is no pay-as-you-go plan or self-serve trial"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 88 against 83",
          "Agent ergonomics, 77 against 54",
          "Maintenance \u0026 community, 67 against 31",
          "Transparency \u0026 trust, 71 against 60"
        ],
        "also": [
          "A hosted endpoint, with nothing to install"
        ],
        "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-flinks.json",
        "title": "Akoya vs Flinks",
        "url": "https://www.anchorterminal.com/compare/akoya-vs-flinks"
      },
      {
        "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-flinks.json",
        "title": "Belvo vs Flinks",
        "url": "https://www.anchorterminal.com/compare/belvo-vs-flinks"
      },
      {
        "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-flinks.json",
        "title": "Enable Banking vs Flinks",
        "url": "https://www.anchorterminal.com/compare/enable-banking-vs-flinks"
      },
      {
        "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-gocardless-bank-account-data.json",
        "title": "Flinks vs GoCardless Bank Account Data",
        "url": "https://www.anchorterminal.com/compare/flinks-vs-gocardless-bank-account-data"
      },
      {
        "json": "https://www.anchorterminal.com/compare/flinks-vs-mx.json",
        "title": "Flinks vs MX Platform API",
        "url": "https://www.anchorterminal.com/compare/flinks-vs-mx"
      },
      {
        "json": "https://www.anchorterminal.com/compare/flinks-vs-plaid.json",
        "title": "Flinks vs Plaid",
        "url": "https://www.anchorterminal.com/compare/flinks-vs-plaid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/flinks-vs-salt-edge.json",
        "title": "Flinks vs Salt Edge Account Information",
        "url": "https://www.anchorterminal.com/compare/flinks-vs-salt-edge"
      },
      {
        "json": "https://www.anchorterminal.com/compare/flinks-vs-teller.json",
        "title": "Flinks vs Teller",
        "url": "https://www.anchorterminal.com/compare/flinks-vs-teller"
      },
      {
        "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-truelayer.json",
        "title": "Flinks vs TrueLayer",
        "url": "https://www.anchorterminal.com/compare/flinks-vs-truelayer"
      },
      {
        "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-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-yapily.json",
        "title": "Plaid vs Yapily",
        "url": "https://www.anchorterminal.com/compare/plaid-vs-yapily"
      },
      {
        "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-yapily.json",
        "title": "Teller vs Yapily",
        "url": "https://www.anchorterminal.com/compare/teller-vs-yapily"
      },
      {
        "json": "https://www.anchorterminal.com/compare/tink-vs-yapily.json",
        "title": "Tink vs Yapily",
        "url": "https://www.anchorterminal.com/compare/tink-vs-yapily"
      },
      {
        "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": 2,
        "edge": "yapily",
        "flinks": 53,
        "key": "reliability",
        "name": "Reliability",
        "weight": 16,
        "yapily": 55
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 5,
        "edge": "yapily",
        "flinks": 83,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13,
        "yapily": 88
      },
      {
        "by": 23,
        "edge": "yapily",
        "flinks": 54,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13,
        "yapily": 77
      },
      {
        "by": 13,
        "edge": "flinks",
        "flinks": 50,
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14,
        "yapily": 37
      },
      {
        "by": 15,
        "edge": "flinks",
        "flinks": 25,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10,
        "yapily": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 36,
        "edge": "yapily",
        "flinks": 31,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7,
        "yapily": 67
      },
      {
        "by": 11,
        "edge": "yapily",
        "flinks": 60,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7,
        "yapily": 71
      }
    ],
    "summary": "Yapily scores 57.6 (C) on agent readiness against Flinks's 52.7 (D), and leads in 5 of 7 scored categories. Flinks leads on security \u0026 auth and payments \u0026 pricing. Both do bank accounts.",
    "verdicts": {
      "flinks": "Ten public OpenAPI files, an llms.txt index with Markdown twins and published sandbox keys let an agent start without a signup. Live access needs a one-year contract from $500 a month, keys never expire, no rate-limit numbers are published, and the status page logged 77 incidents in 90 days.",
      "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/flinks-vs-yapily",
    "json": "https://www.anchorterminal.com/compare/flinks-vs-yapily.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/flinks-vs-yapily.md",
    "slim": "https://www.anchorterminal.com/compare/flinks-vs-yapily.min.md"
  },
  "markdown": "Yapily scores 57.6 (C) on agent readiness against Flinks's 52.7 (D), and leads in 5 of 7 scored categories. Flinks leads on security \u0026 auth and payments \u0026 pricing. Both do bank accounts.\n\n- Flinks: grade D, 52.7/100, rank #559 of 722. Markdown https://www.anchorterminal.com/tools/flinks.md · JSON https://www.anchorterminal.com/api/v1/tools/flinks.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### Flinks (D)\n\nGood for: A lender or fintech with steady volume that needs Canadian bank data, income and lending attributes, PDF statements or Canadian bank payments.\n\nAhead on:\n- Security \u0026 auth, 50 against 37\n- Payments \u0026 pricing, 25 against 10\n\nWatch for: Live access needs a contract with a monthly minimum and a one-year term. The pricing page says there is no pay-as-you-go plan or self-serve trial\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 83\n- Agent ergonomics, 77 against 54\n- Maintenance \u0026 community, 67 against 31\n- Transparency \u0026 trust, 71 against 60\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No public pricing; live access starts with a sales form\n\n\n## Score by category\n\n| Category | Weight | Flinks | Yapily | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 53 | 55 | Yapily +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 88 | Yapily +5 |\n| Agent ergonomics | 13% (16.2 this run) | 54 | 77 | Yapily +23 |\n| Security \u0026 auth | 14% (17.5 this run) | 50 | 37 | Flinks +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 10 | Flinks +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 31 | 67 | Yapily +36 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 71 | Yapily +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **52.7 · D** | **57.6 · C** | |\n\n## Facts side by side\n\n| Fact | Flinks | Yapily |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Flinks Technology Inc. (National Bank of Canada) | Yapily |\n| Hosted endpoint | no (local only) | `https://api.yapily.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Flinks' Master Terms and Conditions. No open-source SDK or repository was found | MIT (SDKs) |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-01 | 2025-06-30 |\n| Terms last updated | 2023-08-03 | 2022-12-05 |\n| Privacy policy last updated | 2022-09-22 | no date given |\n| Customer content may train models | not found in the text | yes |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | 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**Flinks.** Ten public OpenAPI files, an llms.txt index with Markdown twins and published sandbox keys let an agent start without a signup. Live access needs a one-year contract from $500 a month, keys never expire, no rate-limit numbers are published, and the status page logged 77 incidents in 90 days.\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### Flinks\n\n1. Call `/GenerateAuthorizeToken` with the secret key in `flinks-auth-key`, then pass the returned token to the Connect iframe or to `/Authorize`. The token is single-use and expires after 15 minutes.\n2. Send the account holder through Flinks Connect in a browser. The API alone cannot complete a first bank login, and sandbox iframes need `demo=true`.\n3. Store the `loginId`. Call `/Authorize` with it and `MostRecentCached: true` for a new `requestId` each session, because `/GetAccountsDetail` consumes the `requestId`.\n4. On a 202 from `/GetAccountsDetail`, poll `/GetAccountsDetailAsync` every 10 seconds for at most 30 minutes, or ask support to enable webhooks.\n5. Route each end user to the instance for their country. A `loginId` from the Canadian instance is not valid on the US one.\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, Flinks or Yapily?\n\nYapily scores 57.6 (C) on agent readiness against Flinks's 52.7 (D), and leads in 5 of 7 scored categories. Flinks leads on security \u0026 auth and payments \u0026 pricing.\n\n### Do Flinks and Yapily need an API key?\n\nBoth need an API key.\n\n### Can an agent call Flinks and Yapily without installing anything?\n\nNo hosted endpoint is listed for Flinks. Yapily has a hosted endpoint at https://api.yapily.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/flinks-vs-yapily.json, and with the fewest tokens: https://www.anchorterminal.com/compare/flinks-vs-yapily.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"flinks\", \"b\": \"yapily\"}`. From a terminal: `anchor compare flinks yapily`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/flinks.json and https://www.anchorterminal.com/api/v1/tools/yapily.json\n\n## Other comparisons with Flinks or Yapily\n\n- [Akoya vs Flinks](https://www.anchorterminal.com/compare/akoya-vs-flinks.md)\n- [Akoya vs Yapily](https://www.anchorterminal.com/compare/akoya-vs-yapily.md)\n- [Belvo vs Flinks](https://www.anchorterminal.com/compare/belvo-vs-flinks.md)\n- [Belvo vs Yapily](https://www.anchorterminal.com/compare/belvo-vs-yapily.md)\n- [Enable Banking vs Flinks](https://www.anchorterminal.com/compare/enable-banking-vs-flinks.md)\n- [Enable Banking vs Yapily](https://www.anchorterminal.com/compare/enable-banking-vs-yapily.md)\n- [Flinks vs GoCardless Bank Account Data](https://www.anchorterminal.com/compare/flinks-vs-gocardless-bank-account-data.md)\n- [Flinks vs MX Platform API](https://www.anchorterminal.com/compare/flinks-vs-mx.md)\n- [Flinks vs Plaid](https://www.anchorterminal.com/compare/flinks-vs-plaid.md)\n- [Flinks vs Salt Edge Account Information](https://www.anchorterminal.com/compare/flinks-vs-salt-edge.md)\n- [Flinks vs Teller](https://www.anchorterminal.com/compare/flinks-vs-teller.md)\n- [Flinks vs Tink](https://www.anchorterminal.com/compare/flinks-vs-tink.md)\n- [Flinks vs TrueLayer](https://www.anchorterminal.com/compare/flinks-vs-truelayer.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 Yapily](https://www.anchorterminal.com/compare/mx-vs-yapily.md)\n- [Plaid vs Yapily](https://www.anchorterminal.com/compare/plaid-vs-yapily.md)\n- [Salt Edge Account Information vs Yapily](https://www.anchorterminal.com/compare/salt-edge-vs-yapily.md)\n- [Teller vs Yapily](https://www.anchorterminal.com/compare/teller-vs-yapily.md)\n- [Tink vs Yapily](https://www.anchorterminal.com/compare/tink-vs-yapily.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": "Flinks vs Yapily",
        "url": ""
      }
    ],
    "description": "Yapily scores 57.6 (C) on agent readiness against Flinks's 52.7 (D), and leads in 5 of 7 scored categories. Flinks leads on security \u0026 auth and payments \u0026 pricing. Both do bank accounts. Category scores, facts, verdicts and agent notes side by side.",
    "facts": [
      "Flinks D 52.7",
      "Yapily C 57.6",
      "scores"
    ],
    "h1": "Flinks vs Yapily",
    "image": "https://www.anchorterminal.com/assets/og/compare-flinks-vs-yapily.png",
    "path": "/compare/flinks-vs-yapily",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Flinks vs Yapily for AI agents, D 52.7 vs C 57.6 | Anchor Terminal",
    "toc": null,
    "updated": "2026-10-08",
    "url": "https://www.anchorterminal.com/compare/flinks-vs-yapily"
  },
  "tokens": {
    "markdown": 2150,
    "slim": 630
  },
  "version": 1
}