{ "data": { "a": { "slug": "akoya", "name": "Akoya", "vendor": "Akoya LLC", "vendorUrl": "https://akoya.com", "kind": "http-api", "category": "banking-data", "summary": "Akoya runs a US data access network through which consumers permit apps to read their bank and brokerage accounts. Data recipients call FDX-based REST APIs for accounts, balances, transactions, customer details, statements and consent, after an OAuth consent flow.", "url": "https://www.anchorterminal.com/tools/akoya", "markdownUrl": "https://www.anchorterminal.com/tools/akoya.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/akoya.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/akoya.json", "license": "Proprietary service under the Akoya Terms of Use and a signed data access agreement", "transports": [ "http" ], "remoteUrl": "https://products.ddp.akoya.com", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 authorisation code grant with OpenID Connect. A person requests a Data Recipient Hub account (MFA is mandatory), registers an app and receives a client ID and secret. The consumer signs in at their own institution, picks the accounts to share, and the app exchanges the code at `/token` for an ID token and a refresh token. The ID token is the bearer token for data calls. The only scopes are `openid profile offline_access`, and what an app can read is set by its product subscriptions and the consumer's account selection. The service APIs take a 24-hour service token from separate credentials. Sandbox access is self-service. Production needs a questionnaire, a security review and a signed agreement.", "pricing": "paid", "pricingNotes": "No price is published. The pricing page names Standard (fewer than 10,000 monthly connections, self-service onboarding) and Enterprise (10,000 or more, custom pricing) without figures, and its FAQ says a set-up or implementation fee may apply. The sandbox is free and self-service with test data, so an agent's owner can start without a contract. Live data needs production approval (https://akoya.com/pricing, checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI specifications 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.akoya.com", "openapi": "https://docs.akoya.com/guides/akoya-apis-3-0-0-spec", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.consent" ], "tags": [ "hosted", "oauth", "openapi", "fdx", "us-only", "sandbox", "webhooks", "sales-led", "closed-source", "soc2" ], "lastRelease": "2026-08-05", "graded": true, "anchor": { "graded": true, "score": 48.3, "grade": "D", "agentReady": false, "rank": 623, "ranked": true, "rankOf": 722, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 33, "payments": 10, "reliability": 28, "schema": 70, "security": 64, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Six OpenAPI 3.1 specifications, a free self-service sandbox and read-only data endpoints behind per-consumer OAuth tokens make the API straightforward to test. Production needs a security review and a signed agreement, no price is published, and no public status page, SLA, SDK or `llms.txt` was found.", "bestFor": "A US fintech that wants consumer-permissioned data over direct institution APIs in FDX format and can pass a security review.", "strengths": [ "Data APIs are read-only GET endpoints, and each token covers one consumer, one app and the accounts that consumer selected", "OpenAPI 3.1 specifications are published for the Token, Service Token, data, Apps Management, Notifications and Consent APIs", "Free self-service sandbox with a test institution (`mikomo`), scripted test users and a public Postman workspace", "Written version policy. Breaking changes only in major versions, with a six-month sunset after deprecation", "Webhooks report consent revocation, consent updates and planned or unplanned outages, with three delivery attempts" ], "weaknesses": [ "No price is published. Standard (under 10,000 monthly connections) and Enterprise are named without figures, and a set-up fee may apply", "Production access needs an onboarding questionnaire, a security review (SOC 2 report or questionnaire) and an agreement signed by Docusign", "No public status page, SLA or numeric rate limit for the data APIs was found. Availability figures sit inside the Data Recipient Hub", "The Terms of Use forbid using any automated system to access the network and allow changes and termination without prior notice", "No SDK, `llms.txt` or Markdown docs. The OpenAPI files are code blocks to copy from docs pages, not downloadable files" ], "agentNotes": [ "Send `x-akoya-interaction-type` (USER or BATCH) and `x-akoya-last-access` on every v3 data call, plus `x-akoya-intent-type` if the app subscribes to Payments", "Use the `id_token` as the bearer token. The `/token` response has no `access_token` field, so generic OAuth libraries need adjusting", "Treat ID tokens as valid for 15 minutes, refresh on error 602, and store the new refresh token returned by every refresh", "Page transactions by following `links.next.href` unchanged. Set `limit`, `startTime` and `endTime` on the first call only", "On 429 with code 1207 slow the request rate. On 5xx retry up to three times with exponential backoff" ], "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": 48.3 } ], "editorialScores": { "ergonomics": 67, "maintenance": 33, "payments": 10, "reliability": 28, "schema": 70, "security": 64, "transparency": 44 }, "provenanceScore": 72 }, "connect": { "http": "curl --request GET --url 'https://sandbox-products.ddp.akoya.com/accounts-info/v3/mikomo' --header 'x-akoya-interaction-type: USER' --header 'x-akoya-last-access: 2025-11-24T00:00:00Z' --header 'accept: application/json' --header 'authorization: Bearer {{id_token}}'" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/akoya" }, "area": "domain-data", "provenance": { "legalEntity": "Akoya LLC", "domain": "akoya.com", "domainRegistered": "1998-06-24", "endpointOnVendorDomain": true, "terms": "https://akoya.com/terms-of-use", "privacy": "https://akoya.com/privacy-policy", "statusPage": "", "changelog": "https://docs.akoya.com/akoya/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Terms of Use (last updated 20 December 2024) name Akoya LLC and govern use of the Akoya Data Access Network and akoya.com. Production use also runs under a data access agreement signed through Docusign, which is not published.", "The privacy policy (last updated 9 June 2025) covers the website and Akoya's products and services, and gives the address 6 Liberty Square #2381, Boston, MA 02109.", "The OpenAPI files name https://recipient.ddp.akoya.com/terms-of-use as their licence. That address returned a 755-byte script shell to our reader.", "akoya.com/.well-known/security.txt and docs.akoya.com/.well-known/security.txt both returned 404.", "No public status page was found. status.akoya.com did not connect, and the docs place network availability and outages inside the Data Recipient Hub, behind a login.", "RDAP (Verisign) gives a registration date of 1998-06-24 for akoya.com." ], "score": 72 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/akoya.json", "live": { "slug": "akoya", "probe": { "target": "https://products.ddp.akoya.com", "method": "get", "lastAt": "2026-10-08T21:53:14.785708976Z", "lastOk": true, "lastStatus": 403, "lastMs": 350, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 333, "p95ms24h": 384, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "updatedAt": "2026-10-08T21:53:14.785708976Z" } }, "answer": "Belvo scores 63.5 (B) on agent readiness against Akoya's 48.3 (D), and leads in 5 of 7 scored categories. Akoya leads on security \u0026 auth.", "b": { "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:53:17.088482635Z", "lastOk": true, "lastStatus": 403, "lastMs": 130, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 50, "p95ms24h": 181, "samples24h": 48, "samples30d": 48, "days": [ { "date": "2026-10-08", "probes": 48, "ok": 48 } ] }, "vendorStatus": { "page": "https://status.belvo.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:57:43.01716742Z" }, "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:57:43.01716742Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Akoya LLC", "b": "Belvo", "name": "Vendor" }, { "a": "https://products.ddp.akoya.com", "b": "https://api.belvo.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Akoya Terms of Use and a signed data access agreement", "b": "Proprietary service under Belvo's General Conditions of Service Usage. The belvo npm package (0.28.0) is MIT", "name": "Licence" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-05", "b": "2026-08-10", "name": "Last release" }, { "a": "2024-12-20", "b": "2025-01-10", "name": "Terms last updated" }, { "a": "no date given", "b": "2021-02-22", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "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": "yes", "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": "1.1k npm/wk, 240 PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Belvo scores 63.5 (B) on agent readiness against Akoya's 48.3 (D), and leads in 5 of 7 scored categories. Akoya leads on security \u0026 auth.", "question": "Which is better for AI agents, Akoya or Belvo?" }, { "answer": "Akoya uses an OAuth sign-in. Belvo needs an API key.", "question": "Do Akoya and Belvo need an API key?" }, { "answer": "Yes. Akoya has a hosted endpoint at https://products.ddp.akoya.com and Belvo at https://api.belvo.com.", "question": "Can an agent call Akoya and Belvo without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 64 against 57" ], "also": null, "goodFor": "A US fintech that wants consumer-permissioned data over direct institution APIs in FDX format and can pass a security review.", "slug": "akoya", "watchFor": "No price is published. Standard (under 10,000 monthly connections) and Enterprise are named without figures, and a set-up fee may apply" }, { "aheadOn": [ "Reliability, 84 against 28", "Schema \u0026 documentation, 80 against 70", "Agent ergonomics, 80 against 67", "Payments \u0026 pricing, 20 against 10", "Transparency \u0026 trust, 64 against 58" ], "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" } ], "job": { "capability": "bank.accounts", "name": "Bank accounts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/akoya-vs-enable-banking.json", "title": "Akoya vs Enable Banking", "url": "https://www.anchorterminal.com/compare/akoya-vs-enable-banking" }, { "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-gocardless-bank-account-data.json", "title": "Akoya vs GoCardless Bank Account Data", "url": "https://www.anchorterminal.com/compare/akoya-vs-gocardless-bank-account-data" }, { "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/akoya-vs-plaid.json", "title": "Akoya vs Plaid", "url": "https://www.anchorterminal.com/compare/akoya-vs-plaid" }, { "json": "https://www.anchorterminal.com/compare/akoya-vs-salt-edge.json", "title": "Akoya vs Salt Edge Account Information", "url": "https://www.anchorterminal.com/compare/akoya-vs-salt-edge" }, { "json": "https://www.anchorterminal.com/compare/akoya-vs-teller.json", "title": "Akoya vs Teller", "url": "https://www.anchorterminal.com/compare/akoya-vs-teller" }, { "json": "https://www.anchorterminal.com/compare/akoya-vs-tink.json", "title": "Akoya vs Tink", "url": "https://www.anchorterminal.com/compare/akoya-vs-tink" }, { "json": "https://www.anchorterminal.com/compare/akoya-vs-truelayer.json", "title": "Akoya vs TrueLayer", "url": "https://www.anchorterminal.com/compare/akoya-vs-truelayer" }, { "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-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-mx.json", "title": "Belvo vs MX Platform API", "url": "https://www.anchorterminal.com/compare/belvo-vs-mx" }, { "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" } ], "scores": [ { "akoya": 28, "belvo": 84, "by": 56, "edge": "belvo", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "akoya": 70, "belvo": 80, "by": 10, "edge": "belvo", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "akoya": 67, "belvo": 80, "by": 13, "edge": "belvo", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "akoya": 64, "belvo": 57, "by": 7, "edge": "akoya", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "akoya": 10, "belvo": 20, "by": 10, "edge": "belvo", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "akoya": 33, "belvo": 30, "by": 3, "edge": "akoya", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "akoya": 58, "belvo": 64, "by": 6, "edge": "belvo", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Belvo scores 63.5 (B) on agent readiness against Akoya's 48.3 (D), and leads in 5 of 7 scored categories. Akoya leads on security \u0026 auth. Both do bank accounts.", "verdicts": { "akoya": "Six OpenAPI 3.1 specifications, a free self-service sandbox and read-only data endpoints behind per-consumer OAuth tokens make the API straightforward to test. Production needs a security review and a signed agreement, no price is published, and no public status page, SLA, SDK or `llms.txt` was found.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/akoya-vs-belvo", "json": "https://www.anchorterminal.com/compare/akoya-vs-belvo.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/akoya-vs-belvo.md", "slim": "https://www.anchorterminal.com/compare/akoya-vs-belvo.min.md" }, "markdown": "Belvo scores 63.5 (B) on agent readiness against Akoya's 48.3 (D), and leads in 5 of 7 scored categories. Akoya leads on security \u0026 auth. Both do bank accounts.\n\n- Akoya: grade D, 48.3/100, rank #623 of 722. Markdown https://www.anchorterminal.com/tools/akoya.md · JSON https://www.anchorterminal.com/api/v1/tools/akoya.json\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\n## Which one, for what\n\n### Akoya (D)\n\nGood for: A US fintech that wants consumer-permissioned data over direct institution APIs in FDX format and can pass a security review.\n\nAhead on:\n- Security \u0026 auth, 64 against 57\n\nWatch for: No price is published. Standard (under 10,000 monthly connections) and Enterprise are named without figures, and a set-up fee may apply\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 28\n- Schema \u0026 documentation, 80 against 70\n- Agent ergonomics, 80 against 67\n- Payments \u0026 pricing, 20 against 10\n- Transparency \u0026 trust, 64 against 58\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\n## Score by category\n\n| Category | Weight | Akoya | Belvo | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 28 | 84 | Belvo +56 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 80 | Belvo +10 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 80 | Belvo +13 |\n| Security \u0026 auth | 14% (17.5 this run) | 64 | 57 | Akoya +7 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 20 | Belvo +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 33 | 30 | Akoya +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 64 | Belvo +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **48.3 · D** | **63.5 · B** | |\n\n## Facts side by side\n\n| Fact | Akoya | Belvo |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Akoya LLC | Belvo |\n| Hosted endpoint | `https://products.ddp.akoya.com` | `https://api.belvo.com` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under the Akoya Terms of Use and a signed data access agreement | Proprietary service under Belvo's General Conditions of Service Usage. The belvo npm package (0.28.0) is MIT |\n| Read-only variant documented | yes | no |\n| llms.txt | no | yes |\n| Last release | 2026-08-05 | 2026-08-10 |\n| Terms last updated | 2024-12-20 | 2025-01-10 |\n| Privacy policy last updated | no date given | 2021-02-22 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | 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 | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | none | 1.1k npm/wk, 240 PyPI/wk |\n\n## Verdicts\n\n**Akoya.** Six OpenAPI 3.1 specifications, a free self-service sandbox and read-only data endpoints behind per-consumer OAuth tokens make the API straightforward to test. Production needs a security review and a signed agreement, no price is published, and no public status page, SLA, SDK or `llms.txt` was found.\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## Before you call either\n\n### Akoya\n\n1. Send `x-akoya-interaction-type` (USER or BATCH) and `x-akoya-last-access` on every v3 data call, plus `x-akoya-intent-type` if the app subscribes to Payments\n2. Use the `id_token` as the bearer token. The `/token` response has no `access_token` field, so generic OAuth libraries need adjusting\n3. Treat ID tokens as valid for 15 minutes, refresh on error 602, and store the new refresh token returned by every refresh\n4. Page transactions by following `links.next.href` unchanged. Set `limit`, `startTime` and `endTime` on the first call only\n5. On 429 with code 1207 slow the request rate. On 5xx retry up to three times with exponential backoff\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## Questions\n\n### Which is better for AI agents, Akoya or Belvo?\n\nBelvo scores 63.5 (B) on agent readiness against Akoya's 48.3 (D), and leads in 5 of 7 scored categories. Akoya leads on security \u0026 auth.\n\n### Do Akoya and Belvo need an API key?\n\nAkoya uses an OAuth sign-in. Belvo needs an API key.\n\n### Can an agent call Akoya and Belvo without installing anything?\n\nYes. Akoya has a hosted endpoint at https://products.ddp.akoya.com and Belvo at https://api.belvo.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/akoya-vs-belvo.json, and with the fewest tokens: https://www.anchorterminal.com/compare/akoya-vs-belvo.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"akoya\", \"b\": \"belvo\"}`. From a terminal: `anchor compare akoya belvo`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/akoya.json and https://www.anchorterminal.com/api/v1/tools/belvo.json\n\n## Other comparisons with Akoya or Belvo\n\n- [Akoya vs Enable Banking](https://www.anchorterminal.com/compare/akoya-vs-enable-banking.md)\n- [Akoya vs Flinks](https://www.anchorterminal.com/compare/akoya-vs-flinks.md)\n- [Akoya vs GoCardless Bank Account Data](https://www.anchorterminal.com/compare/akoya-vs-gocardless-bank-account-data.md)\n- [Akoya vs MX Platform API](https://www.anchorterminal.com/compare/akoya-vs-mx.md)\n- [Akoya vs Plaid](https://www.anchorterminal.com/compare/akoya-vs-plaid.md)\n- [Akoya vs Salt Edge Account Information](https://www.anchorterminal.com/compare/akoya-vs-salt-edge.md)\n- [Akoya vs Teller](https://www.anchorterminal.com/compare/akoya-vs-teller.md)\n- [Akoya vs Tink](https://www.anchorterminal.com/compare/akoya-vs-tink.md)\n- [Akoya vs TrueLayer](https://www.anchorterminal.com/compare/akoya-vs-truelayer.md)\n- [Akoya vs Yapily](https://www.anchorterminal.com/compare/akoya-vs-yapily.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 MX Platform API](https://www.anchorterminal.com/compare/belvo-vs-mx.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", "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": "Akoya vs Belvo", "url": "" } ], "description": "Belvo scores 63.5 (B) on agent readiness against Akoya's 48.3 (D), and leads in 5 of 7 scored categories. Akoya leads on security \u0026 auth. Both do bank accounts. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Akoya D 48.3", "Belvo B 63.5", "scores" ], "h1": "Akoya vs Belvo", "image": "https://www.anchorterminal.com/assets/og/compare-akoya-vs-belvo.png", "path": "/compare/akoya-vs-belvo", "published": "2026-10-01", "section": "tools", "title": "Akoya vs Belvo for AI agents, D 48.3 vs B 63.5 | Anchor Terminal", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/akoya-vs-belvo" }, "tokens": { "markdown": 2200, "slim": 630 }, "version": 1 }