Head to head · Bank accounts · October 2026 research run

Flinks vs MX Platform API

MX Platform API scores 62.5 (B) on agent readiness against Flinks's 52.7 (D), and leads in 6 of 7 scored categories. Flinks leads on payments & pricing. Both do bank accounts.

Which one, for what

Flinks D

Good for A lender or fintech with steady volume that needs Canadian bank data, income and lending attributes, PDF statements or Canadian bank payments.

Ahead on

  • Payments & pricing, 25 against 15

Watch 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

MX Platform API B

Good for A US or Canadian bank, credit union or fintech with a signed MX contract that wants aggregation, verification and categorised transactions plus embeddable finance widgets.

Ahead on

  • Reliability, 63 against 53
  • Agent ergonomics, 74 against 54
  • Security & auth, 60 against 50
  • Maintenance & community, 71 against 31

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard

Score by category

CategoryWeight this runFlinksMX Platform APIEdge
Reliability16%205363MX Platform API +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28385MX Platform API +2
Agent ergonomics13%16.25474MX Platform API +20
Security & auth14%17.55060MX Platform API +10
Payments & pricing10%12.52515Flinks +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83171MX Platform API +40
Transparency & trust7%8.86063MX Platform API +3
Negative events≤1500
Total52.7 · D62.5 · B

Facts side by side

FactFlinksMX Platform API
KindHTTP APIHTTP API
VendorFlinks Technology Inc. (National Bank of Canada)MX Technologies, Inc.
Hosted endpointno (local only)https://api.mx.com
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPaidPaid
x402nono
LicenceProprietary service under Flinks' Master Terms and Conditions. No open-source SDK or repository was foundProprietary service. The SDKs and the OpenAPI files on GitHub are MIT
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-09-012026-09-29
Terms last updated2023-08-03no document linked
Privacy policy last updated2022-09-22no document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticeyes
Arbitration or class-action waivernot found in the text
Popularitynone9 stars, 2.6k npm/wk, 2k PyPI/wk

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.

MX Platform API

Three public OpenAPI files, llms.txt, Markdown docs and a written version policy with 18 months of support and Deprecation and Sunset response headers. No price, client agreement or SLA is published, production keys need MX's approval, every calling IP address must be allowlisted, and the status page records three platform-wide error incidents since 10 July 2026.

Before you call either

Flinks

  1. 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.
  2. 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.
  3. Store the loginId. Call /Authorize with it and MostRecentCached: true for a new requestId each session, because /GetAccountsDetail consumes the requestId.
  4. On a 202 from /GetAccountsDetail, poll /GetAccountsDetailAsync every 10 seconds for at most 30 minutes, or ask support to enable webhooks.
  5. Route each end user to the instance for their country. A loginId from the Canadian instance is not valid on the US one.

MX Platform API

  1. Send Accept: application/json, Accept-Version: v20260929 and Basic auth of client_id:api_key on every call. A missing version returns 406
  2. Ask the owner to allowlist the calling machine's static IP in the Client Dashboard first. Other addresses get 403, and some failed authentication returns 404
  3. Test against https://int-api.mx.com with institution mxbank, username mxuser and any password. It has no aggregation throttle
  4. Set your own id when creating users and members. A repeat returns 409, which makes a retried create safe
  5. Expect 202 without an error when a standard aggregation is throttled (three hours by default). Balance checks stop at 5 per member every 2 hours with 429
  6. Pass includes[]=merchant or includes[]=category as an array on transaction lists. A comma-separated string returns 400

Questions

Which is better for AI agents, Flinks or MX Platform API?

MX Platform API scores 62.5 (B) on agent readiness against Flinks's 52.7 (D), and leads in 6 of 7 scored categories. Flinks leads on payments & pricing.

Do Flinks and MX Platform API need an API key?

Both need an API key.

Can an agent call Flinks and MX Platform API without installing anything?

No hosted endpoint is listed for Flinks. MX Platform API has a hosted endpoint at https://api.mx.com.

Other comparisons with Flinks or MX Platform API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.