# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/flinks-vs-mx
- Markdown: https://www.anchorterminal.com/compare/flinks-vs-mx.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/flinks-vs-mx.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/flinks-vs-mx.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

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.

- 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
- MX Platform API: grade B, 62.5/100, rank #336 of 722. Markdown https://www.anchorterminal.com/tools/mx.md · JSON https://www.anchorterminal.com/api/v1/tools/mx.json

## 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

| Category | Weight | Flinks | MX Platform API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 53 | 63 | MX Platform API +10 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 83 | 85 | MX Platform API +2 |
| Agent ergonomics | 13% (16.2 this run) | 54 | 74 | MX Platform API +20 |
| Security & auth | 14% (17.5 this run) | 50 | 60 | MX Platform API +10 |
| Payments & pricing | 10% (12.5 this run) | 25 | 15 | Flinks +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 31 | 71 | MX Platform API +40 |
| Transparency & trust | 7% (8.8 this run) | 60 | 63 | MX Platform API +3 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **52.7 · D** | **62.5 · B** | |

## Facts side by side

| Fact | Flinks | MX Platform API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Flinks Technology Inc. (National Bank of Canada) | MX Technologies, Inc. |
| Hosted endpoint | no (local only) | `https://api.mx.com` |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under Flinks' Master Terms and Conditions. No open-source SDK or repository was found | Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-09-01 | 2026-09-29 |
| Terms last updated | 2023-08-03 | no document linked |
| Privacy policy last updated | 2022-09-22 | no document linked |
| Customer content may train models | not found in the text |  |
| Terms restrict automated access | not found in the text |  |
| Terms restrict benchmarking | not found in the text |  |
| Terms or service can change without notice | yes |  |
| Arbitration or class-action waiver | not found in the text |  |
| Popularity | none | 9 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.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/flinks-vs-mx.json, and with the fewest tokens: https://www.anchorterminal.com/compare/flinks-vs-mx.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "flinks", "b": "mx"}`. From a terminal: `anchor compare flinks mx`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/flinks.json and https://www.anchorterminal.com/api/v1/tools/mx.json

## Other comparisons with Flinks or MX Platform API

- [Akoya vs Flinks](https://www.anchorterminal.com/compare/akoya-vs-flinks.md)
- [Akoya vs MX Platform API](https://www.anchorterminal.com/compare/akoya-vs-mx.md)
- [Belvo vs Flinks](https://www.anchorterminal.com/compare/belvo-vs-flinks.md)
- [Belvo vs MX Platform API](https://www.anchorterminal.com/compare/belvo-vs-mx.md)
- [Enable Banking vs Flinks](https://www.anchorterminal.com/compare/enable-banking-vs-flinks.md)
- [Enable Banking vs MX Platform API](https://www.anchorterminal.com/compare/enable-banking-vs-mx.md)
- [Flinks vs GoCardless Bank Account Data](https://www.anchorterminal.com/compare/flinks-vs-gocardless-bank-account-data.md)
- [Flinks vs Plaid](https://www.anchorterminal.com/compare/flinks-vs-plaid.md)
- [Flinks vs Salt Edge Account Information](https://www.anchorterminal.com/compare/flinks-vs-salt-edge.md)
- [Flinks vs Teller](https://www.anchorterminal.com/compare/flinks-vs-teller.md)
- [Flinks vs Tink](https://www.anchorterminal.com/compare/flinks-vs-tink.md)
- [Flinks vs TrueLayer](https://www.anchorterminal.com/compare/flinks-vs-truelayer.md)
- [Flinks vs Yapily](https://www.anchorterminal.com/compare/flinks-vs-yapily.md)
- [GoCardless Bank Account Data vs MX Platform API](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-mx.md)
- [MX Platform API vs Plaid](https://www.anchorterminal.com/compare/mx-vs-plaid.md)
- [MX Platform API vs Salt Edge Account Information](https://www.anchorterminal.com/compare/mx-vs-salt-edge.md)
- [MX Platform API vs Teller](https://www.anchorterminal.com/compare/mx-vs-teller.md)
- [MX Platform API vs Tink](https://www.anchorterminal.com/compare/mx-vs-tink.md)
- [MX Platform API vs TrueLayer](https://www.anchorterminal.com/compare/mx-vs-truelayer.md)
- [MX Platform API vs Yapily](https://www.anchorterminal.com/compare/mx-vs-yapily.md)