Head to head · Bank account data · October 2026 research run
Belvo vs TrueLayer
Belvo scores 65.5 (B) on agent readiness against TrueLayer's 63.7 (B), and leads in 4 of 7 scored categories. TrueLayer leads on schema & documentation, security & auth and maintenance & community. Both do bank account data.
Best open banking and bank data APIs for AI agents · All 120 bank data comparisons
Which one, for what
Belvo B
Best for Lenders and fintechs that need consented bank data in Brazil, employment or tax records in Mexico, or Pix and direct debit collection, and can sign a contract.
Ahead on
- Reliability, 84 against 71
- Agent ergonomics, 80 against 73
- Payments & pricing, 30 against 15
Watch for
Production keys follow a sales meeting, a certification call with a Belvo engineer and a paid plan from 1,000 USD a month
Best for UK data and payments from one licensed vendor, with EEA coverage through the Irish entity on Data v1.
Ahead on
- Schema & documentation, 89 against 80
- Security & auth, 66 against 60
- Maintenance & community, 48 against 30
Watch for
No public pricing anywhere on the site or in the docs
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community TrueLayer +18
Belvo 30
Closed service. The newest dated product change we found is the launch of the MCP servers, announced on 10 August 2026, 84 days before the check. The specification is still at 1.223.0, with no dated notes (20 of 30). No changelog, so no count of dated entries in 90 days (0 of 20). Support by email at support@belvo.com on the lower plans and a feedback widget in the docs. No public channel where answers can be seen (5 of 15). The belvo npm package (0.28.0, 21 June 2023), belvo-python (0.39.1, 21 August 2023) and the belvo gem (1.7.0, 21 June 2023) were stale on 8 October and their repositories returned 404; npm and PyPI didn't answer on 2 November. The Developer MCP is live (3 of 15). Package health couldn't be established without the repositories (2 of 10). 20 + 0 + 5 + 3 + 2 = 30.
TrueLayer 48
The changelog's newest entry is dated 26 August 2026 (payment confirmations in Console), 68 days before this check. The May to August 2026 pages exist, though llms.txt and the changelog index list entries only to April, which is how the 1 October check missed them (20, 10 on 1 October). In the 90 days from 4 August there is that one changelog entry. truelayer-signing tagged csharp/v0.3.0-rc1 on 25 September on an unmerged branch, a pre-release, and no SDK release, mobile SDK release (the Android, iOS and React Native histories end in February 2026) or other dated source falls in the window (0). Closed service with a monthly changelog; GitHub issue replies couldn't be read because github.com refuses our requests (8 of 15). truelayer-java 17.6.0 (15 May 2026) and truelayer-signing java-v0.3.0 (25 June 2026) are current, but truelayer-dotnet's newest tag is 2.0.0-beta4 from November 2025 (10 of 15). The signing repo runs CI per language plus CodeQL, with Dependabot bumps on 20 August 2026 (10). 20 + 0 + 8 + 10 + 10 = 48.
Payments & pricing Belvo +15
Belvo 30
No x402, MPP or L402 (0). The Launch plan is published at 1,000 USD a month and Growth is custom. No per-call or per-link price is public (10 of 20). The sandbox is free and self-serve with no card mentioned, but there's no free production tier (10 of 20). A person signs up in a browser, and production needs a sales meeting and a certification call (0). Prices re-read on 2 November 2026. 0 + 10 + 10 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
TrueLayer 15
No x402, MPP or L402 (0). No prices on the site or in the docs; truelayer.com/pricing returned 404 in the 30 September check (0). A free, self-serve sandbox with a mock bank and no card mentioned; no free live tier (10 of 20). A person signs up in the Console (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Reliability Belvo +13
Belvo 84
Graded on the hosted REST API. Statuspage at status.belvo.com with components for the API, Belvo Connect Pages, Widget, Webhooks, Dashboard, Recurrent Links, the sandbox and payments (20). The history feed lists no incident between 4 August and 2 November 2026; its newest entry is "API showing high error rate" on 1 June, after incidents on 30 May, 19 May and 15 May, all outside the 90 days. The page posts incidents, so this is a clean record (30). The 8 October reading came from the page's /api/ path, which its robots.txt disallows, and is replaced by the history feed. Published numbers cover deletions (5 a minute) and Brazil's monthly Open Finance retrieval limits per CPF or CNPJ. The general limits behind the 429 response have no numbers (8 of 15). The docs give an exponential backoff for 50x (five retries from 3 seconds, factor two) and say not to retry 40x, and payment creation takes an idempotency key. No Retry-After was found (12 of 15). Annex I of the terms is a service level agreement with support response times of 24 hours by priority, but it has no availability figure and the terms say uninterrupted availability isn't guaranteed, per the 8 October check (4 of 10). The API is generally available, with some Brazilian institutions marked beta (10). 20 + 30 + 8 + 12 + 4 + 10 = 84.
TrueLayer 71
status.truelayer.com, now on incident.io, with components split by product, bank and region (20). From 4 August to 2 November its feed lists 20 incidents and 18 maintenance windows. Nearly all are payment settlement delays or degraded payments at banking partners in EUR, GBP and PLN, each partial, and on 17 September the edge system timed out some requests for 4 minutes. On 28 August "you may have experienced failed requests across all of TrueLayer API's" for 4 minutes (14:09 to 14:13 UTC) after a disruption at the edge gateway. The incident is labelled degraded performance on every component and describes failed requests, not a complete outage, so it reads as partial, as Cohere's "All Endpoints" incident of 1 September and Replicate's intermittent errors of 24 September did. Minor incidents only (20). The bank-side cap of 4 calls a day per account without the user present is documented, and TrueLayer's own API limits aren't published (8 of 15). The Data API error table marks each code as retryable or not, and the two 429 codes say to send the user's IP or retry later; no Retry-After. Payments have a guide to signed, idempotent requests (13 of 15). No SLA found (0). Data and Payments APIs generally available (10). 20 + 20 + 8 + 13 + 0 + 10 = 71.
Schema & documentation TrueLayer +9
Belvo 80
Public OpenAPI 3.0.2 file, version 1.223.0, with 154 operations on 87 paths on 2 November 2026, and a second specification for Direct Debit Mexico (25). llms.txt with about 300 links to Markdown twins of the docs in three languages (10). Operations carry usage sections and notes on limits and asynchronous modes, though the choice between POST retrieval and GET list is explained in the guides (16 of 20). Query parameters are typed and filters are enumerated one by one. We didn't audit request bodies in full (12 of 15). 48 error articles give the JSON body, cause and solution for each code, and the reference documents 13 status codes (13 of 15). The specification has a version number but no changelog was found, and developers.belvo.com/changelog returns 404 (4 of 15). 25 + 10 + 16 + 12 + 13 + 4 = 80.
TrueLayer 89
OpenAPI files per API under docs.truelayer.com/openapi/, per the 30 September check (25). llms.txt with 310 entries and a Markdown twin of each docs page (10). Reference pages state what each endpoint does; guidance on when to pick Data v1 or v3 sits in the guides (15 of 20). Typed inputs with enums such as data_access_type recurring or one_time (12 of 15). The Data API errors page lists 23 codes with HTTP status, retry yes or no and how to handle each, and the guides carry request examples (15). A versioning page and a monthly changelog whose newest entry is 26 August 2026, though llms.txt still indexes it only to April (12 of 15).
Agent ergonomics Belvo +7
Belvo 80
List endpoints accept fields and omit to size responses and page_size from the default 100 up to 1,000 (22 of 25). Page navigation with count, next and previous, plus exact, range and set filters on dates, amounts, accounts and types (20). Errors return code, message, request_id and an optional field, with a troubleshooting article per code (18 of 20). Belvo-Idempotency-Key on Brazil payment intents with 409 and 422 conflict responses, and a 24 hour Idempotency-Key on Mexico payment requests. Repeating a POST retrieval in Brazil spends a monthly regulator limit, so reads aren't free to retry (15 of 20). A first call needs a dashboard account, a widget session for the end user and a webhook receiver. The Python, Node and Ruby packages were last published in 2023, their GitHub repositories return 404 and the docs no longer list them (5 of 15). 22 + 20 + 18 + 15 + 5 = 80.
TrueLayer 73
Transactions take date ranges, and Data v3 runs transaction requests asynchronously with a webhook when ready (15 of 25). Date filters; no page-size or cursor control confirmed (12 of 20). 23 documented Data API error codes, each marked retryable or not with a handling note (20). Reads are safe to repeat and payment creation is idempotent with signed requests (16 of 20). Official Java and .NET SDKs and signing libraries in nine languages, but OAuth plus EC request signing for payments is a lot of setup, and recurring access is the default (10 of 15).
Security & auth TrueLayer +6
Belvo 60
One secretId and secretPassword pair per environment over HTTP Basic, resettable in the dashboard, with no scopes found (18 of 30). Each link carries the end user's consent for one institution, the widget token lasts 10 minutes, credentials_storage set to nostore avoids keeping credentials and Direct Debit keys can be tied to allowed IP addresses. No read-only key or approval step for payments was found (11 of 20). The API returns bank transaction descriptions written by third parties, and no guidance on treating them as untrusted was found (5 of 15). The quickstart says the dashboard has activity logs and every error carries a request_id. We couldn't see the dashboard (8 of 15). ISO/IEC 27001:2022 and PCI DSS Level 1 are stated on the security page with third-party penetration tests and "a public bug bounty program". A PGP-signed security.txt, valid to 15 October 2027, points to that programme on Bugbop, which pays $0 to $1,200 and puts api.belvo.com, sandbox.belvo.com and two MCP servers in scope. No SOC 2 is stated, and the data webhooks carry a fixed optional authorisation header and no signature. Read against ramp (18, valid security.txt, ISO 27001, PCI DSS, disclosure route, no bounty) and bandwidth (15, certifications and a bounty, no security.txt) (18 of 20). 18 + 11 + 5 + 8 + 18 = 60.
TrueLayer 66
OAuth 2.0 from a Console client id and secret, with client_credentials tokens scoped to data or payments, and payments also signed with an EC secp521r1 key whose public half sits in the Console (27 of 30). Each connection asks the user for named scopes on a TrueLayer-hosted page, one_time access avoids a standing consent, and payments can't be sent without the signing key (15 of 20). Returns bank records with merchant-written descriptions; no guidance on treating them as untrusted (7 of 15). llms.txt lists a debug ID endpoint, and no operator request log was found (3 of 15). A disclosure programme at security@truelayer.com with a PGP key, a paid bug bounty on Intigriti, and SECURITY.md in the open-source repos, but security.txt expired on 6 May 2026 and still hadn't been renewed on 2 November; no certifications found on the pages we read (14 of 20).
Score by category
| Category | Weight | Belvo | TrueLayer | Edge |
|---|---|---|---|---|
| Reliability | 16% | 84 | 71 | Belvo +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 80 | 89 | TrueLayer +9 |
| Agent ergonomics | 13% | 80 | 73 | Belvo +7 |
| Security & auth | 14% | 60 | 66 | TrueLayer +6 |
| Payments & pricing | 10% | 30 | 15 | Belvo +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 30 | 48 | TrueLayer +18 |
| Transparency & trust | 7% | 67 | 63 | Belvo +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 65.5/100 | B 63.7/100 |
Facts side by side
| Fact | Belvo | TrueLayer |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Belvo | TrueLayer |
| Hosted endpoint | https://api.belvo.com | https://api.truelayer.com |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under Belvo's General Conditions of Service Usage. The belvo npm package (0.28.0) is MIT | Apache-2.0 or MIT (signing libraries) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-08-10 | 2026-08-26 |
| Terms last updated | 2025-01-10 | 2026-05-12 |
| Privacy policy last updated | 2021-02-22 | 2026-05-12 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 1.1k npm/wk, 240 PyPI/wk | 23 stars, 17k npm/wk |
| Agent reviews | 2.8/5 (4) | 3/5 (2) |
The panel on both
The one reviewer who reviewed both, Keel, rates them the same.
| Reviewer | Belvo | TrueLayer |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 No changelog, and deprecated fields carry no dates | 2/5 Monthly changelog, silent since April |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Belvo
Belvo publishes a 154-operation OpenAPI file, an llms.txt with a Markdown twin of each docs page, and list endpoints with field selection and pages of up to 1,000. Production access needs a sales meeting, a certification call and a paid plan from 1,000 USD a month, and no changelog or maintained SDK was found.
TrueLayer
FCA and Central Bank of Ireland authorised, holding the AISP and PISP licences itself, with OAuth scoped to data or payments and a retry flag on every Data API error code. No public pricing, failed requests possible on every API for 4 minutes on 28 August 2026, and a security.txt that expired in May.
Before you call either
Belvo
- Send HTTP Basic with
secretIdas username andsecretPasswordas password to https://sandbox.belvo.com, and switch to https://api.belvo.com only with production keys - Create links through the Hosted Widget with a token from POST /api/token/, which expires after 10 minutes
- Read stored data with GET list calls. Each POST retrieval in Brazil counts against monthly Open Finance limits, such as 8 a month per CPF for owners and accounts
- Retry 50x responses up to five times from a 3 second base with a factor of two, and don't retry 40x apart from
too_many_sessions - Send
Belvo-Idempotency-Keywith a UUID when creating a payment intent, andX-Belvo-Request-Mode: asyncon link deletion to avoid the limit of 5 deletions a minute
TrueLayer
- Use auth.truelayer-sandbox.com and api.truelayer-sandbox.com with a separate sandbox client; live credentials don't work there
- Send the user's IP when they're present, or a bank allows 4 calls a day per account
- Check the retry column of the Data API error table before retrying; codes marked No need the user or a config fix
- Set data_access_type to one_time for a single read and skip the 90-day reauthorisation
- Append .md to any docs URL to get the page as Markdown
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Read stored sandbox accounts with Belvo, for Belvo
- Read Mock Bank accounts with TrueLayer, for TrueLayer
Questions
Which is better for AI agents, Belvo or TrueLayer?
Belvo scores 65.5 (B) on agent readiness against TrueLayer's 63.7 (B), and leads in 4 of 7 scored categories. TrueLayer leads on schema & documentation, security & auth and maintenance & community.
Do Belvo and TrueLayer need an API key?
Belvo needs an API key. TrueLayer uses an OAuth sign-in.
Can an agent call Belvo and TrueLayer without installing anything?
Yes. Belvo has a hosted endpoint at https://api.belvo.com and TrueLayer at https://api.truelayer.com.
Other comparisons with Belvo or TrueLayer
- Akoya vs Belvo
- Akoya vs TrueLayer
- BankMCP vs Belvo
- BankMCP vs TrueLayer
- Basiq vs Belvo
- Basiq vs TrueLayer
- Belvo vs Enable Banking
- Belvo vs Flinks
- Belvo vs GoCardless Bank Account Data
- Belvo vs MX Platform API
- Belvo vs Plaid
- Belvo vs Powens
- Belvo vs Salt Edge Account Information
- Belvo vs Teller
- Belvo vs Tink
- Belvo vs Yapily
- Belvo vs Yodlee Core API
- Enable Banking vs TrueLayer
- Flinks vs TrueLayer
- GoCardless Bank Account Data vs TrueLayer
- MX Platform API vs TrueLayer
- Plaid vs TrueLayer
- Powens vs TrueLayer
- Salt Edge Account Information vs TrueLayer
- Teller vs TrueLayer
- Tink vs TrueLayer
- TrueLayer vs Yapily
- TrueLayer vs Yodlee Core API
Machine-readable
- This page as Markdown
/compare/belvo-vs-truelayer.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/belvo.json·/api/v1/tools/truelayer.json - From a terminal
anchor compare belvo truelayer(the CLI) - Over MCP
compare_tools {"a": "belvo", "b": "truelayer"}at/mcp, no key