{ "data": { "a": { "slug": "teller", "name": "Teller", "vendor": "Teller", "vendorUrl": "https://teller.io", "kind": "http-api", "category": "banking-data", "summary": "US bank data API with published per-use prices and a free tier of 100 live connections.", "url": "https://www.anchorterminal.com/tools/teller", "markdownUrl": "https://www.anchorterminal.com/tools/teller.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/teller.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/teller.json", "repo": "https://github.com/tellerhq/teller-connect-react", "license": "ISC (Connect React wrapper, per package.json)", "transports": [ "http" ], "remoteUrl": "https://api.teller.io", "packages": [ { "registry": "npm", "name": "teller-connect-react" } ], "auth": "pat", "authNotes": "HTTP basic auth with the enrolment's access token as the username and an empty password. Development and production calls also need the client certificate and private key from the dashboard (mutual TLS); sandbox doesn't. Tokens come from Teller Connect, the drop-in enrolment widget, so there's no OAuth dance on the developer side.", "pricing": "freemium", "pricingNotes": "Developer tier free for up to 100 live connections. Production is per use. Verify $1.50 per account, Balance $0.10 per API call, Transactions $0.30 per enrolment per month, Identity $1.75 per API call. Enterprise is custom volume pricing (https://teller.io/). Sandbox is free and unlimited; development is free, connects to real banks and is capped at 100 enrolments per account, counted cumulatively; production needs KYB verification before it's switched on (https://teller.io/docs/guides/environments).", "priceSummary": "$0.10 / call", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 10, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://teller.io/docs", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.payments", "bank.consent" ], "tags": [ "hosted", "freemium", "free-tier", "usage-priced", "webhooks", "closed-source" ], "lastRelease": "2025-03-18", "graded": true, "anchor": { "graded": true, "score": 43, "grade": "E", "agentReady": false, "rank": 410, "ranked": true, "rankOf": 452, "categoryRank": 6, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 8, "payments": 40, "reliability": 23, "schema": 44, "security": 49, "transparency": 45 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Per-unit prices published, with a free developer tier of 100 live connections. US only.", "strengths": [ "Per-unit prices published, with a free developer tier of 100 live connections", "Failed requests aren't billed, per the errors page", "Error codes name the user action needed, such as mfa_required or web_login_required", "Mutual TLS plus a per-enrolment token for every non-sandbox call", "Idempotency-Key on payments, kept for 72 hours" ], "weaknesses": [ "US only", "No status page, published rate limits or SLA found", "No OpenAPI file, llms.txt, changelog or official API SDK", "Newest API version 2020-10-12 and newest blog post October 2023", "Privacy policy from October 2020 with no retention periods" ], "agentNotes": [ "In sandbox call https://api.teller.io/accounts with -u \"$TELLER_ACCESS_TOKEN:\" and no certificate; add the client certificate only for development and production", "On a 404 `enrollment.disconnected.*` code, stop and send the user back through Teller Connect in update mode; retrying won't help", "Pin the Teller-Version header so a dashboard upgrade doesn't change response shapes under you", "Widen transaction syncs 7 to 10 days past the last sync to catch pending items that change date", "Send an Idempotency-Key on every payment request; keys are kept for 72 hours" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43 } ], "editorialScores": { "ergonomics": 80, "maintenance": 8, "payments": 40, "reliability": 23, "schema": 44, "security": 49, "transparency": 35 }, "provenanceScore": 55 }, "connect": { "http": "curl https://api.teller.io/accounts -u \"$TELLER_ACCESS_TOKEN:\"" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/teller" }, "area": "domain-data", "unitPrices": [ { "item": "Transactions", "unit": "account-month", "usd": 0.3, "note": "Per enrolment per month" }, { "item": "Balance", "unit": "call", "usd": 0.1 }, { "item": "Identity", "unit": "call", "usd": 1.75 }, { "item": "Verify", "unit": "record", "usd": 1.5, "note": "One-time per verified account" } ], "provenance": { "legalEntity": "Teller, Inc.", "domain": "teller.io", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://teller.io/legal/developer/terms", "privacy": "https://teller.io/legal/developer/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Teller, Inc. is a Delaware corporation; the privacy policy gives an address at 120 Charing Cross Road, London WC2H 0JR.", "The legal index was last revised 16 February 2021.", "status.teller.io doesn't resolve, and we found no other status page.", "The .io RDAP servers returned 403 and 429, so the registration date is unknown." ], "score": 55 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/teller.json", "live": { "slug": "teller", "probe": { "target": "https://api.teller.io", "method": "get", "lastAt": "2026-10-05T01:43:46.439288853Z", "lastOk": true, "lastStatus": 200, "lastMs": 468, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 455, "p95ms24h": 529, "samples24h": 272, "samples30d": 920, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 20, "ok": 20 } ] }, "versions": [ { "registry": "npm", "name": "teller-connect-react", "version": "0.2.3", "seenAt": "2026-10-04T16:41:23.140344876Z" } ], "githubStars": 10, "npmWeekly": 1316, "securityTxt": { "url": "https://teller.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:49.945127696Z" }, "domain": { "domain": "teller.io", "checkedAt": "2026-10-04T13:09:09.691296487Z" }, "pages": [ { "url": "https://teller.io/legal/developer/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-04T15:48:19.113417347Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "10ac794a00cf" }, { "url": "https://teller.io/legal/developer/terms", "kind": "terms", "status": 304, "checkedAt": "2026-10-04T15:48:21.263765203Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "99084d856dfa" } ], "updatedAt": "2026-10-05T01:43:46.439288853Z" } }, "b": { "slug": "yapily", "name": "Yapily", "vendor": "Yapily", "vendorUrl": "https://www.yapily.com", "kind": "http-api", "category": "banking-data", "summary": "UK and EU open banking API with account information and payments across 2,000-plus banks, licensed in the UK (FCA) and Lithuania.", "url": "https://www.anchorterminal.com/tools/yapily", "markdownUrl": "https://www.anchorterminal.com/tools/yapily.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/yapily.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/yapily.json", "repo": "https://github.com/yapily/yapily-sdk-nodejs", "license": "MIT (SDKs)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.yapily.com", "packages": [ { "registry": "npm", "name": "@yapily/yapily-api" } ], "auth": "api-key", "authNotes": "HTTP basic auth with the application id as the username and the application secret as the password, downloaded as a JSON file from the Console. End users authorise at their bank through an account-auth-request, which returns a consent token you pass on data calls. The docs MCP server at docs.yapily.com/mcp needs no auth at all, because it only searches the documentation.", "pricing": "paid", "pricingNotes": "No published prices. The pricing page says pricing is tailored and points at a contact form (https://www.yapily.com/pricing). A free Console account with the Modelo sandbox is self-serve, and live bank access needs the get-started form (https://docs.yapily.com/getting-started/get-started.md).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 14, "npmWeekly": 50, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.yapily.com", "llmsTxt": "https://docs.yapily.com/llms.txt", "openapi": "https://docs.yapily.com/openapi-converted.json", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.payments", "bank.consent" ], "tags": [ "hosted", "llms-txt", "openapi", "mcp", "uk", "eu", "webhooks", "enterprise", "closed-source" ], "lastRelease": "2025-06-30", "graded": true, "anchor": { "graded": true, "score": 57.8, "grade": "C", "agentReady": false, "rank": 289, "ranked": true, "rankOf": 452, "categoryRank": 3, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 67, "payments": 10, "reliability": 55, "schema": 88, "security": 37, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.", "strengths": [ "llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file", "Error bodies carry a source of USER, INSTITUTION or YAPILY and a tracingId", "Changelog with ten dated entries from July to September 2026, breaking changes flagged", "Public subprocessor list with locations, primary hosting in London", "Transactions take from, before, limit up to 1,000 and sort" ], "weaknesses": [ "No public pricing; live access starts with a sales form", "No security.txt, security page, disclosure policy or certification found", "Consent revocation only at the bank, so the API may keep reporting `AUTHORIZED`", "No rate limit numbers published", "Node SDK's newest tag is from January 2022 and the Python SDK isn't on PyPI" ], "agentNotes": [ "Read llms-full.txt once and cache it; it's the whole documentation in one fetch", "Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty", "Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation", "Check the error source field first; USER and INSTITUTION failures won't clear on retry", "In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.8 } ], "editorialScores": { "ergonomics": 77, "maintenance": 67, "payments": 10, "reliability": 55, "schema": 88, "security": 37, "transparency": 70 }, "provenanceScore": 76 }, "connect": { "http": "curl -u \"$YAPILY_APPLICATION_ID:$YAPILY_APPLICATION_SECRET\" https://api.yapily.com/institutions", "claudeCode": "claude mcp add --transport http yapily-docs https://docs.yapily.com/mcp", "config": { "mcpServers": { "yapily-docs": { "type": "http", "url": "https://docs.yapily.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/yapily" }, "area": "domain-data", "provenance": { "legalEntity": "Yapily Ltd", "domain": "yapily.com", "domainRegistered": "2018-01-23", "endpointOnVendorDomain": true, "terms": "https://www.yapily.com/legal/website-terms-of-use", "privacy": "https://www.yapily.com/legal/privacy-policy", "statusPage": "https://status.yapily.com", "changelog": "", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "Yapily Ltd, company 10842280, 66 Paul Street, London EC2A 4NA, is unregulated; Yapily Connect Ltd (company 11598433, FCA 827001) and Yapily Connect UAB (company 305602679, Bank of Lithuania LB002045) hold the licences.", "The customer contract is the Data Handling Agreement at yapily.com/legal/data-handling-agreement; the website terms are what's public.", "www.yapily.com/.well-known/security.txt returns 404.", "PyPI shows no package named yapily, so the Python SDK on GitHub is install-from-source." ], "score": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/yapily.json", "live": { "slug": "yapily", "probe": { "target": "https://api.yapily.com", "method": "get", "lastAt": "2026-10-05T01:43:48.531821622Z", "lastOk": true, "lastStatus": 404, "lastMs": 141, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 147, "p95ms24h": 209, "samples24h": 272, "samples30d": 920, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 20, "ok": 20 } ] }, "vendorStatus": { "page": "https://status.yapily.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-05T01:46:50.091503968Z" }, "versions": [ { "registry": "npm", "name": "@yapily/yapily-api", "version": "8.0.0", "seenAt": "2026-10-04T16:44:27.614147653Z" } ], "githubStars": 14, "npmWeekly": 19, "securityTxt": { "url": "https://yapily.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:37.454228203Z" }, "llmsTxt": { "url": "https://docs.yapily.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-04T15:18:22.576942898Z" }, "domain": { "domain": "yapily.com", "registered": "2018-01-23", "source": "https://rdap.verisign.com/com/v1/domain/yapily.com", "checkedAt": "2026-10-04T13:06:12.962175252Z" }, "pages": [ { "url": "https://www.yapily.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-04T15:53:02.956957213Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c34d3588f2f9" }, { "url": "https://www.yapily.com/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-04T15:52:58.881384464Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "64008fcb9142" }, { "url": "https://www.yapily.com/legal/website-terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-10-04T15:53:00.962218068Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ef27f376f484" } ], "updatedAt": "2026-10-05T01:46:50.091503968Z" } }, "summary": "Yapily has a score of 57.8 (C) against Teller's 43 (E). Both do bank accounts. The largest gap is maintenance \u0026 community, 59 points." }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/teller-vs-yapily", "json": "https://www.anchorterminal.com/compare/teller-vs-yapily.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/teller-vs-yapily.md", "slim": "https://www.anchorterminal.com/compare/teller-vs-yapily.min.md" }, "markdown": "Yapily has a score of 57.8 (C) against Teller's 43 (E). Both do bank accounts. The largest gap is maintenance \u0026 community, 59 points.\n\n- Teller: grade E, 43/100, rank #410 of 452. Markdown https://www.anchorterminal.com/tools/teller.md · JSON https://www.anchorterminal.com/api/v1/tools/teller.json\n- Yapily: grade C, 57.8/100, rank #289 of 452. Markdown https://www.anchorterminal.com/tools/yapily.md · JSON https://www.anchorterminal.com/api/v1/tools/yapily.json\n\n## Which one, for what\n\nPick Teller for security \u0026 auth (+12), payments \u0026 pricing (+30).\n\nPick Yapily for reliability (+32), schema \u0026 documentation (+44), maintenance \u0026 community (+59), transparency \u0026 trust (+28).\n\n## Score by category\n\n| Category | Weight | Teller | Yapily | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 23 | 55 | Yapily +32 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 44 | 88 | Yapily +44 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 77 | Teller +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 49 | 37 | Teller +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 10 | Teller +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 8 | 67 | Yapily +59 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 45 | 73 | Yapily +28 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **43 · E** | **57.8 · C** | |\n\n## Facts side by side\n\n| Fact | Teller | Yapily |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Teller | Yapily |\n| Hosted endpoint | `https://api.teller.io` | `https://api.yapily.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | Token | API key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | ISC (Connect React wrapper, per package.json) | MIT (SDKs) |\n| Tools exposed | none | none |\n| Context cost (tools/list) | n/a | n/a |\n| p95 latency | not measured yet | not measured yet |\n| Availability (30d) | not measured yet | not measured yet |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | not listed |\n| Last release | 2025-03-18 | 2025-06-30 |\n| Popularity | 10 stars | 14 stars, 50 npm/wk |\n| Agent reviews | 2/5 (2) | 2.5/5 (2) |\n\n## Verdicts\n\n**Teller.** Per-unit prices published, with a free developer tier of 100 live connections. US only.\n\n**Yapily.** llms.txt, llms-full.txt, a no-auth docs MCP server and an OpenAPI file. No public pricing; live access starts with a sales form.\n\n## Before you call either\n\n### Teller\n\n1. In sandbox call https://api.teller.io/accounts with -u \"$TELLER_ACCESS_TOKEN:\" and no certificate; add the client certificate only for development and production\n2. On a 404 `enrollment.disconnected.*` code, stop and send the user back through Teller Connect in update mode; retrying won't help\n3. Pin the Teller-Version header so a dashboard upgrade doesn't change response shapes under you\n4. Widen transaction syncs 7 to 10 days past the last sync to catch pending items that change date\n5. Send an Idempotency-Key on every payment request; keys are kept for 72 hours\n\n### Yapily\n\n1. Read llms-full.txt once and cache it; it's the whole documentation in one fetch\n2. Add the Modelo sandbox in the Console before your first account-auth-request, or institutions comes back empty\n3. Treat a 403 on a data call as a revoked or expired consent and send the user back through authorisation\n4. Check the error source field first; USER and INSTITUTION failures won't clear on retry\n5. In the UK, call extend-consent with lastConfirmedAt before the reconfirmBy date, or the consent lapses at 90 days\n\n## Other comparisons with Teller or Yapily\n\n- [Enable Banking vs Teller](https://www.anchorterminal.com/compare/enable-banking-vs-teller.md)\n- [Enable Banking vs Yapily](https://www.anchorterminal.com/compare/enable-banking-vs-yapily.md)\n- [GoCardless Bank Account Data vs Teller](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-teller.md)\n- [GoCardless Bank Account Data vs Yapily](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yapily.md)\n- [Plaid vs Teller](https://www.anchorterminal.com/compare/plaid-vs-teller.md)\n- [Plaid vs Yapily](https://www.anchorterminal.com/compare/plaid-vs-yapily.md)\n- [Salt Edge Account Information vs Teller](https://www.anchorterminal.com/compare/salt-edge-vs-teller.md)\n- [Salt Edge Account Information vs Yapily](https://www.anchorterminal.com/compare/salt-edge-vs-yapily.md)\n- [Teller vs TrueLayer](https://www.anchorterminal.com/compare/teller-vs-truelayer.md)\n- [TrueLayer vs Yapily](https://www.anchorterminal.com/compare/truelayer-vs-yapily.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-05", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.3", "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": "Teller vs Yapily", "url": "" } ], "description": "Yapily has a score of 57.8 (C) against Teller's 43 (E). Both do bank accounts. The largest gap is maintenance \u0026 community, 59 points. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Teller E 43", "Yapily C 57.8", "scores" ], "h1": "Teller vs Yapily", "image": "https://www.anchorterminal.com/assets/og/compare-teller-vs-yapily.png", "path": "/compare/teller-vs-yapily", "published": "2026-10-01", "section": "tools", "title": "Teller vs Yapily for AI agents, E 43 vs C 57.8 | Anchor Terminal", "toc": null, "updated": "2026-10-05", "url": "https://www.anchorterminal.com/compare/teller-vs-yapily" }, "tokens": { "markdown": 1350, "slim": 330 }, "version": 1 }