{ "data": { "a": { "slug": "belvo", "name": "Belvo", "vendor": "Belvo", "vendorUrl": "https://belvo.com", "kind": "http-api", "category": "banking-data", "summary": "Belvo is an open finance API for Latin America. It reads bank accounts, transactions and investments in Brazil, employment records in Brazil and Mexico and tax data in Mexico, and starts Pix payments in Brazil and direct debits in Mexico.", "url": "https://www.anchorterminal.com/tools/belvo", "markdownUrl": "https://www.anchorterminal.com/tools/belvo.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/belvo.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/belvo.json", "license": "Proprietary service under Belvo's General Conditions of Service Usage. The belvo npm package (0.28.0) is MIT", "transports": [ "http" ], "remoteUrl": "https://api.belvo.com", "packages": [ { "registry": "npm", "name": "belvo" }, { "registry": "pypi", "name": "belvo-python" } ], "auth": "api-key", "authNotes": "HTTP Basic with a `secretId` and `secretPassword` generated in the dashboard, one pair for each environment. The password is shown once and a lost one means resetting the keys. No scopes or read-only keys were found. Sandbox keys are self-serve after email sign-up. Production keys follow a request to Belvo, a sales meeting and a certification call. End users connect accounts in the Hosted Widget, started with a 10 minute token from POST /api/token/. The Direct Debit API in Mexico has its own keys and optional IP allowlisting set up by support.", "pricing": "paid", "pricingNotes": "The Launch plan is 1,000 USD a month and Growth is priced by sales, both through Contact Sales (https://belvo.com/plans-and-pricing/). No per-call or per-link price is published, and the terms put the price in a signed Service Order with a 12 month term. The sandbox is free, self-serve and for testing only, so an agent can start without a contract but can't reach real accounts. Changing the refresh rate of recurrent links is priced by sales.", "priceSummary": "$1000 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI file or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 1084, "pypiWeekly": 240, "asOf": "2026-10-08" }, "docsUrl": "https://developers.belvo.com/", "llmsTxt": "https://developers.belvo.com/llms.txt", "openapi": "https://developers.belvo.com/_bundle/apis/BelvoOpenApiSpec.yaml", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.payments", "bank.consent" ], "tags": [ "hosted", "openapi", "llms-txt", "api-key", "webhooks", "sandbox", "brazil", "mexico", "latin-america", "sales-led", "status-page", "closed-source" ], "lastRelease": "2026-08-10", "graded": true, "anchor": { "graded": true, "score": 63.5, "grade": "B", "agentReady": false, "rank": 309, "ranked": true, "rankOf": 722, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 30, "payments": 20, "reliability": 84, "schema": 80, "security": 57, "transparency": 64 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Belvo publishes a 146-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.", "bestFor": "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.", "strengths": [ "Public OpenAPI 3.0.2 file, version 1.223.0, with 146 operations on 83 paths, and a separate specification for Direct Debit in Mexico", "llms.txt lists a Markdown twin of every docs page in English, Spanish and Portuguese", "List endpoints take `fields`, `omit`, `page_size` up to 1,000 and range filters on dates and amounts", "Retention is set per link and per call with `stale_in`, `credentials_storage` and `save_data`", "ISO/IEC 27001:2022 and PCI DSS Level 1 are stated on the security page" ], "weaknesses": [ "Production keys follow a sales meeting, a certification call with a Belvo engineer and a paid plan from 1,000 USD a month", "One `secretId` and `secretPassword` pair per environment over HTTP Basic, with no scopes or read-only keys found", "No changelog was found, and the Python, Node and Ruby packages were last published in 2023 with their GitHub repositories returning 404", "Bank data covers Brazil only in the docs read on 8 October 2026, and Mexico has employment, fiscal and direct debit products", "security.txt expired on 22 March 2025", "General rate limits carry no published numbers, and the data webhooks have no signature, only an optional fixed authorisation header" ], "agentNotes": [ "Send HTTP Basic with `secretId` as username and `secretPassword` as 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-Key` with a UUID when creating a payment intent, and `X-Belvo-Request-Mode: async` on link deletion to avoid the limit of 5 deletions a minute" ], "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": 63.5 } ], "editorialScores": { "ergonomics": 80, "maintenance": 30, "payments": 20, "reliability": 84, "schema": 80, "security": 57, "transparency": 46 }, "provenanceScore": 81 }, "connect": { "http": "curl -X GET https://sandbox.belvo.com/api/ \\\n -H \"Authorization: Basic $(echo -n 'YOUR_SECRET_ID:YOUR_SECRET_PASSWORD' | base64)\"", "claudeCode": "claude mcp add --transport http belvo-docs https://developers.belvo.com/mcp", "config": { "mcpServers": { "belvo-docs": { "type": "http", "url": "https://developers.belvo.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/belvo" }, "area": "domain-data", "unitPrices": [ { "item": "Launch plan", "unit": "month", "usd": 1000, "note": "Production access, through sales. Growth plan is custom" } ], "provenance": { "legalEntity": "Belvo Tecnologias Ltda.", "domain": "belvo.com", "domainRegistered": "2005-07-17", "endpointOnVendorDomain": true, "terms": "https://belvo.com/terms-service/", "privacy": "https://belvo.com/privacy-policy-end-users/", "statusPage": "https://status.belvo.com", "changelog": "", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The General Conditions of Service Usage, last updated 10 January 2025, define Belvo as Belvo Tecnologias Ltda., CNPJ 37.869.837/0001-81, and Belvo Instituição de Pagamento Ltda., CNPJ 43.215.815/0001-09, with affiliates. They are governed by Brazilian law with the courts of São Paulo.", "The legal notice also names Belvo Technologies, SAPI de CV in Mexico City (RFC BTE1912023D6) and Belvo Technologies Inc. Sucursal en España in Barcelona.", "The privacy link is the end-user policy, which covers data Belvo processes through its platform for clients. A separate policy for clients and site visitors at https://belvo.com/privacy-policy-clients/ was last updated 15 July 2024.", "security.txt is PGP-signed, gives security@belvo.com and a disclosure policy on Federacy, and expired on 22 March 2025.", "No changelog was found. developers.belvo.com/changelog returns 404 and llms.txt lists none.", "Verisign RDAP gives a registration date of 2005-07-17 for belvo.com." ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/belvo.json", "live": { "slug": "belvo", "probe": { "target": "https://api.belvo.com", "method": "get", "lastAt": "2026-10-08T21:12:05.542099971Z", "lastOk": true, "lastStatus": 403, "lastMs": 36, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 50, "p95ms24h": 181, "samples24h": 41, "samples30d": 41, "days": [ { "date": "2026-10-08", "probes": 41, "ok": 41 } ] }, "vendorStatus": { "page": "https://status.belvo.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:05:52.216286465Z" }, "pages": [ { "url": "https://belvo.com/plans-and-pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:15:32.924207659Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e45bde6abe6f" }, { "url": "https://belvo.com/privacy-policy-end-users/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:15:35.22055183Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "44ff1673e0c9" }, { "url": "https://belvo.com/terms-service/", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:15:55.309282506Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "fc9af45fbdce" } ], "updatedAt": "2026-10-08T21:12:05.542099971Z" } }, "answer": "Belvo scores 63.5 (B) on agent readiness against MX Platform API's 62.5 (B), and leads in 4 of 7 scored categories. MX Platform API leads on schema \u0026 documentation and maintenance \u0026 community.", "b": { "slug": "mx", "name": "MX Platform API", "vendor": "MX Technologies, Inc.", "vendorUrl": "https://www.mx.com", "kind": "http-api", "category": "banking-data", "summary": "MX Technologies' Platform API connects US and Canadian bank accounts for account aggregation, balance checks, account and owner verification and up to 24 months of categorised transactions, through REST endpoints or the embedded Connect Widget.", "url": "https://www.anchorterminal.com/tools/mx", "markdownUrl": "https://www.anchorterminal.com/tools/mx.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mx.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mx.json", "repo": "https://github.com/mxenabled/openapi", "license": "Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://api.mx.com", "packages": [ { "registry": "npm", "name": "mx-platform-node" }, { "registry": "pypi", "name": "mx-platform-python" }, { "registry": "npm", "name": "@mxenabled/web-widget-sdk" } ], "auth": "api-key", "authNotes": "Self-serve for development, MX approval for production. Every request sends Basic auth of `client_id:api_key` from the Client Dashboard, plus `Accept-Version`. Development and production keys are separate, and a rotated key stays valid for 30 days. All calling IP addresses must be allowlisted in the dashboard, and MX reviews addresses outside the US. Mutual TLS is optional. Four processor endpoints take a Bearer token exchanged from an authorisation code. OAuth institutions appear only after MX registers the client with them.", "pricing": "paid", "pricingNotes": "No public price. www.mx.com/pricing/ returns 404 and the product pages ask for a demo. Developer API keys are free and reach the integration environment (`https://int-api.mx.com`) with up to 100 users and a subset of institutions, so an agent's owner can test without a contract. Production keys are requested from MX in the Client Dashboard (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the OpenAPI file or mx.com (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 9, "npmWeekly": 2631, "pypiWeekly": 1997, "asOf": "2026-10-08" }, "docsUrl": "https://docs.mx.com/", "llmsTxt": "https://docs.mx.com/llms.txt", "openapi": "https://docs.mx.com/openapi/platform-api/v20260929.yaml", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.consent" ], "tags": [ "hosted", "openapi", "llms-txt", "typescript", "python", "ruby", "java", "csharp", "webhooks", "sales-led", "enterprise", "status-page", "soc2" ], "lastRelease": "2026-09-29", "graded": true, "anchor": { "graded": true, "score": 62.5, "grade": "B", "agentReady": false, "rank": 336, "ranked": true, "rankOf": 722, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 71, "payments": 15, "reliability": 63, "schema": 85, "security": 60, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "OpenAPI files for all three Platform API versions, an llms.txt index and a Markdown twin of every docs page", "Each version is supported for at least 18 months, then deprecated for 12, and deprecated endpoints send `Deprecation`, `Sunset` and `Link` headers", "Rate limits are published per method, 2,000 GET and 750 POST requests a second in production", "Free developer keys reach the integration environment with up to 100 users and the `mxbank` test institution", "API keys rotate with a 30-day overlap, every calling IP must be allowlisted, and mutual TLS and JWE-encrypted responses are available" ], "weaknesses": [ "No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard", "Three platform-wide incidents of elevated errors since 10 July 2026 (42, 89 and 37 minutes), marked critical or major", "One `client_id` and `api_key` pair reaches every endpoint, with no scopes and no read-only key", "No SDK targets v20260929. The newest SDK releases date from January and February 2026 and cover v20250224 and v20111101", "A 429 carries no `Retry-After`, and the API has no idempotency key", "The privacy statement excludes data MX processes for clients, and no DPA or sub-processor list is public" ], "agentNotes": [ "Send `Accept: application/json`, `Accept-Version: v20260929` and Basic auth of `client_id:api_key` on every call. A missing version returns 406", "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", "Test against `https://int-api.mx.com` with institution `mxbank`, username `mxuser` and any password. It has no aggregation throttle", "Set your own `id` when creating users and members. A repeat returns 409, which makes a retried create safe", "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", "Pass `includes[]=merchant` or `includes[]=category` as an array on transaction lists. A comma-separated string returns 400" ], "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": 71, "payments": 15, "reliability": 63, "schema": 85, "security": 60, "transparency": 46 }, "provenanceScore": 80 }, "connect": { "install": "npm install mx-platform-node@^3", "http": "curl -X GET 'https://int-api.mx.com/users' \\\n -H 'Accept: application/json' \\\n -H 'Accept-Version: v20260929' \\\n -H 'Authorization: Basic BASE_64_ENCODING_OF{client_id:api_key}'" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/mx" }, "area": "domain-data", "provenance": { "legalEntity": "MX Technologies, Inc.", "domain": "mx.com", "domainRegistered": "1994-04-28", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "https://status.mx.com", "changelog": "https://docs.mx.com/resources/changelog/", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The privacy statement and the terms name MX Technologies, Inc., 3401 North Thanksgiving Way, Suite 500, Lehi, Utah 84043.", "`terms` is left out. The only terms on mx.com are an end-user and website Terms of Use dated 15 January 2020 (https://www.mx.com/terms/). No client or developer agreement for the Platform API is published.", "`privacy` is left out. The privacy statement at https://www.mx.com/privacy/ (30 September 2025) says it does not apply to personal data MX processes as a processor on behalf of its clients, which is the data the API handles.", "The API answers at api.mx.com and int-api.mx.com.", "security.txt at https://www.mx.com/.well-known/security.txt is PGP-signed, gives vulns@mx.com and expires 2030-12-31. Its Policy link redirects to the trust page.", "Verisign's RDAP server gives a registration date of 1994-04-28 and GoDaddy.com, LLC as registrar." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mx.json", "live": { "slug": "mx", "probe": { "target": "https://api.mx.com", "method": "get", "lastAt": "2026-10-08T21:12:16.259214321Z", "lastOk": true, "lastStatus": 404, "lastMs": 675, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 726, "p95ms24h": 827, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.mx.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:06:13.020289952Z" }, "updatedAt": "2026-10-08T21:12:16.259214321Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Belvo", "b": "MX Technologies, Inc.", "name": "Vendor" }, { "a": "https://api.belvo.com", "b": "https://api.mx.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "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 Belvo's General Conditions of Service Usage. The belvo npm package (0.28.0) is MIT", "b": "Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-10", "b": "2026-09-29", "name": "Last release" }, { "a": "2025-01-10", "b": "no document linked", "name": "Terms last updated" }, { "a": "2021-02-22", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "1.1k npm/wk, 240 PyPI/wk", "b": "9 stars, 2.6k npm/wk, 2k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Belvo scores 63.5 (B) on agent readiness against MX Platform API's 62.5 (B), and leads in 4 of 7 scored categories. MX Platform API leads on schema \u0026 documentation and maintenance \u0026 community.", "question": "Which is better for AI agents, Belvo or MX Platform API?" }, { "answer": "Both need an API key.", "question": "Do Belvo and MX Platform API need an API key?" }, { "answer": "Yes. Belvo has a hosted endpoint at https://api.belvo.com and MX Platform API at https://api.mx.com.", "question": "Can an agent call Belvo and MX Platform API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 84 against 63", "Agent ergonomics, 80 against 74", "Payments \u0026 pricing, 20 against 15" ], "also": null, "goodFor": "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.", "slug": "belvo", "watchFor": "Production keys follow a sales meeting, a certification call with a Belvo engineer and a paid plan from 1,000 USD a month" }, { "aheadOn": [ "Schema \u0026 documentation, 85 against 80", "Maintenance \u0026 community, 71 against 30" ], "also": null, "goodFor": "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.", "slug": "mx", "watchFor": "No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard" } ], "job": { "capability": "bank.accounts", "name": "Bank accounts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/akoya-vs-belvo.json", "title": "Akoya vs Belvo", "url": "https://www.anchorterminal.com/compare/akoya-vs-belvo" }, { "json": "https://www.anchorterminal.com/compare/akoya-vs-mx.json", "title": "Akoya vs MX Platform API", "url": "https://www.anchorterminal.com/compare/akoya-vs-mx" }, { "json": "https://www.anchorterminal.com/compare/belvo-vs-enable-banking.json", "title": "Belvo vs Enable Banking", "url": "https://www.anchorterminal.com/compare/belvo-vs-enable-banking" }, { "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-gocardless-bank-account-data.json", "title": "Belvo vs GoCardless Bank Account Data", "url": "https://www.anchorterminal.com/compare/belvo-vs-gocardless-bank-account-data" }, { "json": "https://www.anchorterminal.com/compare/belvo-vs-plaid.json", "title": "Belvo vs Plaid", "url": "https://www.anchorterminal.com/compare/belvo-vs-plaid" }, { "json": "https://www.anchorterminal.com/compare/belvo-vs-salt-edge.json", "title": "Belvo vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/belvo-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/belvo-vs-teller.json", "title": "Belvo vs Teller", "url": "https://www.anchorterminal.com/compare/belvo-vs-teller" }, { "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-truelayer.json", "title": "Belvo vs TrueLayer", "url": "https://www.anchorterminal.com/compare/belvo-vs-truelayer" }, { "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-mx.json", "title": "Enable Banking vs MX Platform API", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-mx" }, { "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/gocardless-bank-account-data-vs-mx.json", "title": "GoCardless Bank Account Data vs MX Platform API", "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-mx" }, { "json": "https://www.anchorterminal.com/compare/mx-vs-plaid.json", "title": "MX Platform API vs Plaid", "url": "https://www.anchorterminal.com/compare/mx-vs-plaid" }, { "json": "https://www.anchorterminal.com/compare/mx-vs-salt-edge.json", "title": "MX Platform API vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/mx-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/mx-vs-teller.json", "title": "MX Platform API vs Teller", "url": "https://www.anchorterminal.com/compare/mx-vs-teller" }, { "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-truelayer.json", "title": "MX Platform API vs TrueLayer", "url": "https://www.anchorterminal.com/compare/mx-vs-truelayer" }, { "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" } ], "scores": [ { "belvo": 84, "by": 21, "edge": "belvo", "key": "reliability", "mx": 63, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "belvo": 80, "by": 5, "edge": "mx", "key": "schema", "mx": 85, "name": "Schema \u0026 documentation", "weight": 13 }, { "belvo": 80, "by": 6, "edge": "belvo", "key": "ergonomics", "mx": 74, "name": "Agent ergonomics", "weight": 13 }, { "belvo": 57, "by": 3, "edge": "mx", "key": "security", "mx": 60, "name": "Security \u0026 auth", "weight": 14 }, { "belvo": 20, "by": 5, "edge": "belvo", "key": "payments", "mx": 15, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "belvo": 30, "by": 41, "edge": "mx", "key": "maintenance", "mx": 71, "name": "Maintenance \u0026 community", "weight": 7 }, { "belvo": 64, "by": 1, "edge": "belvo", "key": "transparency", "mx": 63, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Belvo scores 63.5 (B) on agent readiness against MX Platform API's 62.5 (B), and leads in 4 of 7 scored categories. MX Platform API leads on schema \u0026 documentation and maintenance \u0026 community. Both do bank accounts.", "verdicts": { "belvo": "Belvo publishes a 146-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.", "mx": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/belvo-vs-mx", "json": "https://www.anchorterminal.com/compare/belvo-vs-mx.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/belvo-vs-mx.md", "slim": "https://www.anchorterminal.com/compare/belvo-vs-mx.min.md" }, "markdown": "Belvo scores 63.5 (B) on agent readiness against MX Platform API's 62.5 (B), and leads in 4 of 7 scored categories. MX Platform API leads on schema \u0026 documentation and maintenance \u0026 community. Both do bank accounts.\n\n- Belvo: grade B, 63.5/100, rank #309 of 722. Markdown https://www.anchorterminal.com/tools/belvo.md · JSON https://www.anchorterminal.com/api/v1/tools/belvo.json\n- 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\n\n## Which one, for what\n\n### Belvo (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 84 against 63\n- Agent ergonomics, 80 against 74\n- Payments \u0026 pricing, 20 against 15\n\nWatch for: Production keys follow a sales meeting, a certification call with a Belvo engineer and a paid plan from 1,000 USD a month\n\n### MX Platform API (B)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 85 against 80\n- Maintenance \u0026 community, 71 against 30\n\nWatch for: No public price, SLA or client agreement. Production keys are requested from MX in the Client Dashboard\n\n\n## Score by category\n\n| Category | Weight | Belvo | MX Platform API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 84 | 63 | Belvo +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 85 | MX Platform API +5 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 74 | Belvo +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 57 | 60 | MX Platform API +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 15 | Belvo +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 30 | 71 | MX Platform API +41 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 63 | Belvo +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.5 · B** | **62.5 · B** | |\n\n## Facts side by side\n\n| Fact | Belvo | MX Platform API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Belvo | MX Technologies, Inc. |\n| Hosted endpoint | `https://api.belvo.com` | `https://api.mx.com` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Belvo's General Conditions of Service Usage. The belvo npm package (0.28.0) is MIT | Proprietary service. The SDKs and the OpenAPI files on GitHub are MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-08-10 | 2026-09-29 |\n| Terms last updated | 2025-01-10 | no document linked |\n| Privacy policy last updated | 2021-02-22 | no document linked |\n| Customer content may train models | not found in the text | |\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 | yes | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 1.1k npm/wk, 240 PyPI/wk | 9 stars, 2.6k npm/wk, 2k PyPI/wk |\n\n## Verdicts\n\n**Belvo.** Belvo publishes a 146-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.\n\n**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.\n\n## Before you call either\n\n### Belvo\n\n1. Send HTTP Basic with `secretId` as username and `secretPassword` as password to https://sandbox.belvo.com, and switch to https://api.belvo.com only with production keys\n2. Create links through the Hosted Widget with a token from POST /api/token/, which expires after 10 minutes\n3. 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\n4. 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`\n5. Send `Belvo-Idempotency-Key` with a UUID when creating a payment intent, and `X-Belvo-Request-Mode: async` on link deletion to avoid the limit of 5 deletions a minute\n\n### MX Platform API\n\n1. Send `Accept: application/json`, `Accept-Version: v20260929` and Basic auth of `client_id:api_key` on every call. A missing version returns 406\n2. 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\n3. Test against `https://int-api.mx.com` with institution `mxbank`, username `mxuser` and any password. It has no aggregation throttle\n4. Set your own `id` when creating users and members. A repeat returns 409, which makes a retried create safe\n5. 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\n6. Pass `includes[]=merchant` or `includes[]=category` as an array on transaction lists. A comma-separated string returns 400\n\n## Questions\n\n### Which is better for AI agents, Belvo or MX Platform API?\n\nBelvo scores 63.5 (B) on agent readiness against MX Platform API's 62.5 (B), and leads in 4 of 7 scored categories. MX Platform API leads on schema \u0026 documentation and maintenance \u0026 community.\n\n### Do Belvo and MX Platform API need an API key?\n\nBoth need an API key.\n\n### Can an agent call Belvo and MX Platform API without installing anything?\n\nYes. Belvo has a hosted endpoint at https://api.belvo.com and MX Platform API at https://api.mx.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/belvo-vs-mx.json, and with the fewest tokens: https://www.anchorterminal.com/compare/belvo-vs-mx.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"belvo\", \"b\": \"mx\"}`. From a terminal: `anchor compare belvo mx`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/belvo.json and https://www.anchorterminal.com/api/v1/tools/mx.json\n\n## Other comparisons with Belvo or MX Platform API\n\n- [Akoya vs Belvo](https://www.anchorterminal.com/compare/akoya-vs-belvo.md)\n- [Akoya vs MX Platform API](https://www.anchorterminal.com/compare/akoya-vs-mx.md)\n- [Belvo vs Enable Banking](https://www.anchorterminal.com/compare/belvo-vs-enable-banking.md)\n- [Belvo vs Flinks](https://www.anchorterminal.com/compare/belvo-vs-flinks.md)\n- [Belvo vs GoCardless Bank Account Data](https://www.anchorterminal.com/compare/belvo-vs-gocardless-bank-account-data.md)\n- [Belvo vs Plaid](https://www.anchorterminal.com/compare/belvo-vs-plaid.md)\n- [Belvo vs Salt Edge Account Information](https://www.anchorterminal.com/compare/belvo-vs-salt-edge.md)\n- [Belvo vs Teller](https://www.anchorterminal.com/compare/belvo-vs-teller.md)\n- [Belvo vs Tink](https://www.anchorterminal.com/compare/belvo-vs-tink.md)\n- [Belvo vs TrueLayer](https://www.anchorterminal.com/compare/belvo-vs-truelayer.md)\n- [Belvo vs Yapily](https://www.anchorterminal.com/compare/belvo-vs-yapily.md)\n- [Enable Banking vs MX Platform API](https://www.anchorterminal.com/compare/enable-banking-vs-mx.md)\n- [Flinks vs MX Platform API](https://www.anchorterminal.com/compare/flinks-vs-mx.md)\n- [GoCardless Bank Account Data vs MX Platform API](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-mx.md)\n- [MX Platform API vs Plaid](https://www.anchorterminal.com/compare/mx-vs-plaid.md)\n- [MX Platform API vs Salt Edge Account Information](https://www.anchorterminal.com/compare/mx-vs-salt-edge.md)\n- [MX Platform API vs Teller](https://www.anchorterminal.com/compare/mx-vs-teller.md)\n- [MX Platform API vs Tink](https://www.anchorterminal.com/compare/mx-vs-tink.md)\n- [MX Platform API vs TrueLayer](https://www.anchorterminal.com/compare/mx-vs-truelayer.md)\n- [MX Platform API vs Yapily](https://www.anchorterminal.com/compare/mx-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": "Belvo vs MX Platform API", "url": "" } ], "description": "Belvo scores 63.5 (B) on agent readiness against MX Platform API's 62.5 (B), and leads in 4 of 7 scored categories. MX Platform API leads on schema \u0026 documentation and maintenance \u0026 community. Both do bank accounts. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Belvo B 63.5", "MX Platform API B 62.5", "scores" ], "h1": "Belvo vs MX Platform API", "image": "https://www.anchorterminal.com/assets/og/compare-belvo-vs-mx.png", "path": "/compare/belvo-vs-mx", "published": "2026-10-01", "section": "tools", "title": "Belvo vs MX Platform API for AI agents, B 63.5 vs B 62.5", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/belvo-vs-mx" }, "tokens": { "markdown": 2350, "slim": 680 }, "version": 1 }