{ "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": 42.7, "grade": "E", "agentReady": false, "rank": 788, "ranked": true, "rankOf": 842, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 8, "payments": 40, "reliability": 23, "schema": 44, "security": 49, "transparency": 42 }, "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.", "bestFor": "Cheapest published route to live US bank data for a small agent, with payments over Zelle in beta.", "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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.7 } ], "editorialScores": { "ergonomics": 80, "maintenance": 8, "payments": 40, "reliability": 23, "schema": 44, "security": 49, "transparency": 35 }, "provenanceScore": 49 }, "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": 49 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/teller.json", "live": { "slug": "teller", "probe": { "target": "https://api.teller.io", "method": "get", "lastAt": "2026-10-09T11:46:42.59063238Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "timed out", "authRequired": false, "uptime24h": 34.36, "uptime30d": 91.94, "p50ms24h": 457, "p95ms24h": 516, "samples24h": 259, "samples30d": 2109, "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": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 223 }, { "date": "2026-10-09", "probes": 125, "ok": 0 } ], "outages": [ { "start": "2026-10-08T19:47:32.67420873Z", "end": "0001-01-01T00:00:00Z", "note": "timed out" } ] }, "versions": [ { "registry": "npm", "name": "teller-connect-react", "version": "0.2.3", "seenAt": "2026-10-08T16:31:34.942178299Z" } ], "githubStars": 10, "npmWeekly": 1386, "securityTxt": { "url": "https://teller.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:47.282957501Z" }, "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-08T18:25:06.666012241Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "10ac794a00cf" }, { "url": "https://teller.io/legal/developer/terms", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:25:08.824767094Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "99084d856dfa" } ], "updatedAt": "2026-10-09T11:46:42.59063238Z" } }, "answer": "Teller and Yodlee Core API score within a point of each other on agent readiness, 42.7 (E) and 41.9 (E). Yodlee Core API leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "yodlee-financial-data", "name": "Yodlee Core API", "vendor": "Yodlee, Inc.", "vendorUrl": "https://www.yodlee.com", "kind": "http-api", "category": "banking-data", "summary": "Yodlee's Core API (v1.1) aggregates a consumer's bank, card, investment, loan and insurance accounts for balances, categorised transactions, holdings, statements and account-owner details. Consumers link accounts through the embedded FastLink 4 widget.", "url": "https://www.anchorterminal.com/tools/yodlee-financial-data", "markdownUrl": "https://www.anchorterminal.com/tools/yodlee-financial-data.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/yodlee-financial-data.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/yodlee-financial-data.json", "repo": "https://github.com/Yodlee/OpenAPI", "license": "Proprietary service. The Swagger file on GitHub is MIT", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "Self-serve for the sandbox. Registering on the developer portal gives a `clientId`, a `secret` and an admin `loginName` on the API dashboard. `POST /auth/token` takes the id and secret in a form body and a `loginName` header, and returns a bearer token that lasts 30 minutes and acts for that user, or for the admin on administrative calls. Every call also sends `Api-Version: 1.1`. Each environment (sandbox, development, production) has its own credentials. How production access is granted is not stated in the public docs. Full account numbers and holder details need Yodlee Security Office approval.", "pricing": "paid", "pricingNotes": "No public price. `/pricing` returns 404 on yodlee.com and on the developer portal, and product pages ask for a demo. The sandbox is free on registration, with five preconfigured users and sample data only, so an agent's owner can test without a contract (checked 2026-10-08).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the Swagger file or yodlee.com (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 17, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.yodlee.com/resources/yodlee/yodlee-api-overview/docs", "openapi": "https://raw.githubusercontent.com/Yodlee/OpenAPI/main/swagger.yaml", "capabilities": [ "bank.accounts", "bank.transactions", "bank.identity", "bank.consent" ], "tags": [ "hosted", "oauth", "openapi", "sandbox", "webhooks", "sales-led", "closed-source", "enterprise", "soc2" ], "lastRelease": "2026-07-31", "graded": true, "anchor": { "graded": true, "score": 41.9, "grade": "E", "agentReady": false, "rank": 796, "ranked": true, "rankOf": 842, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 58, "maintenance": 33, "payments": 15, "reliability": 15, "schema": 71, "security": 49, "transparency": 53 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data.", "bestFor": "A bank, wealth firm or fintech with a Yodlee contract that needs wide account coverage, including investment holdings, loans and insurance, in the US, UK, Australia and India.", "strengths": [ "Public Swagger 2.0 file on GitHub (MIT) with 98 operations, 267 definitions and `Y`-prefixed error codes listed per operation", "Access tokens expire after 30 minutes, are bound to one end user's `loginName`, and can be revoked with `DELETE /auth/token`", "Free sandbox on registration with five preconfigured test users, per the docs", "Consent endpoints list, renew and record open banking consents, and `DELETE /user/unregister` removes a user and their data", "The Security FAQ states an annual SOC 2 Type 2 assessment, PCI DSS 4.0.1 Level One certification and yearly third-party penetration tests" ], "weaknesses": [ "No public price, service agreement or developer terms. The terms address named in the Swagger file returns 404", "No status page, rate limit, 429 guidance, idempotency key or SLA was found in the pages read", "No official server SDK. Yodlee's docs tell developers to generate a client from the Swagger file", "The Swagger file was last updated on 22 April 2026 to the November 2025 release and lacks fields added in June and July 2026, such as `isCrypto`", "The sandbox cannot register new users, and full account numbers and holder details need Yodlee Security Office approval", "The privacy notice covers only Yodlee's own consumer services and websites, and no DPA or sub-processor list is public" ], "agentNotes": [ "Get a token with `POST /auth/token`, sending `Api-Version: 1.1` and the end user's `loginName` as headers and `clientId` and `secret` in a form body. Reuse it for up to 30 minutes", "Use the admin `loginName` only for administrative calls such as webhook subscriptions. A token made with a user's `loginName` reads only that user's data", "In the sandbox, pick one of the five preconfigured users. Registering new users is not supported there", "Page `GET /transactions` with `skip` and `top` (1 to 500). Without dates it returns the last 30 days, and at most two years with `fromDate` and `toDate`", "A person must link accounts in FastLink 4 first. Then read `GET /providerAccounts` for link status before `GET /accounts`", "Subscribe to `DATA_UPDATES` or `REFRESH` webhooks, or poll `GET /dataExtracts/events` in windows of at most 60 minutes, and do not poll accounts in a loop" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 41.9 } ], "editorialScores": { "ergonomics": 58, "maintenance": 33, "payments": 15, "reliability": 15, "schema": 71, "security": 49, "transparency": 32 }, "provenanceScore": 73 }, "connect": { "http": "POST /auth/token\nApi-Version: 1.1\nloginName: \u003cloginName\u003e\nContent-Type: application/x-www-form-urlencoded\n\nclientId=\u003cclientId\u003e\u0026secret=\u003csecret\u003e" }, "letme": { "capability": "https://letme.dev/bank.accounts", "tool": "https://letme.dev/yodlee-financial-data" }, "area": "domain-data", "provenance": { "legalEntity": "Yodlee, Inc.", "domain": "yodlee.com", "domainRegistered": "1999-02-09", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://developer.yodlee.com/resources/yodlee", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The privacy notice names Yodlee, Inc. and its subsidiaries Yodlee Credit, LLC, Yodlee Data Services, LLC and Yodlee Infotech Private Limited. The company page says Yodlee was acquired by Envestnet in 2015 and joined the STG portfolio in 2025.", "`terms` is left out. No service agreement or developer terms are published. The Swagger file gives https://developer.yodlee.com/terms/condition as its terms of service, and that address returns 404.", "`privacy` is left out. The privacy notice at https://www.yodlee.com/legal/privacy-notice says it applies to Yodlee's direct-to-consumer services and websites, and that a client's own privacy practices apply to services delivered through a Yodlee client, which is how API data is handled.", "`endpointOnVendorDomain` is null. The public docs print API paths without a host, and the host is given with the credentials on a dashboard we did not read.", "No status page is linked from yodlee.com or the developer portal, and status.yodlee.com did not answer.", "https://www.yodlee.com/.well-known/security.txt returns the home page, and the same path on developer.yodlee.com returns 404.", "Verisign's RDAP server gives a registration date of 1999-02-09 and CSC Corporate Domains, Inc. as registrar." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/yodlee-financial-data.json" }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Teller", "b": "Yodlee, Inc.", "name": "Vendor" }, { "a": "https://api.teller.io", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "Token", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "ISC (Connect React wrapper, per package.json)", "b": "Proprietary service. The Swagger file on GitHub is MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2025-03-18", "b": "2026-07-31", "name": "Last release" }, { "a": "2021-06-18", "b": "no document linked", "name": "Terms last updated" }, { "a": "2020-10-12", "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": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "10 stars", "b": "17 stars", "name": "Popularity" }, { "a": "2/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Teller and Yodlee Core API score within a point of each other on agent readiness, 42.7 (E) and 41.9 (E). Yodlee Core API leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Teller or Yodlee Core API?" }, { "answer": "Teller needs an access token. Yodlee Core API uses an OAuth sign-in.", "question": "Do Teller and Yodlee Core API need an API key?" }, { "answer": "Teller has a hosted endpoint at https://api.teller.io. No hosted endpoint is listed for Yodlee Core API.", "question": "Can an agent call Teller and Yodlee Core API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 23 against 15", "Agent ergonomics, 80 against 58", "Payments \u0026 pricing, 40 against 15" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Cheapest published route to live US bank data for a small agent, with payments over Zelle in beta.", "slug": "teller", "watchFor": "US only" }, { "aheadOn": [ "Schema \u0026 documentation, 71 against 44", "Maintenance \u0026 community, 33 against 8", "Transparency \u0026 trust, 53 against 42" ], "also": null, "goodFor": "A bank, wealth firm or fintech with a Yodlee contract that needs wide account coverage, including investment holdings, loans and insurance, in the US, UK, Australia and India.", "slug": "yodlee-financial-data", "watchFor": "No public price, service agreement or developer terms. The terms address named in the Swagger file returns 404" } ], "job": { "capability": "bank.accounts", "name": "Bank accounts" }, "others": [ { "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-yodlee-financial-data.json", "title": "Akoya vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/akoya-vs-yodlee-financial-data" }, { "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-yodlee-financial-data.json", "title": "Belvo vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/belvo-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-teller.json", "title": "Enable Banking vs Teller", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-teller" }, { "json": "https://www.anchorterminal.com/compare/enable-banking-vs-yodlee-financial-data.json", "title": "Enable Banking vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/enable-banking-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-teller.json", "title": "Flinks vs Teller", "url": "https://www.anchorterminal.com/compare/flinks-vs-teller" }, { "json": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.json", "title": "Flinks vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-teller.json", "title": "GoCardless Bank Account Data vs Teller", "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-teller" }, { "json": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yodlee-financial-data.json", "title": "GoCardless Bank Account Data vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yodlee-financial-data" }, { "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-yodlee-financial-data.json", "title": "MX Platform API vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/mx-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/plaid-vs-teller.json", "title": "Plaid vs Teller", "url": "https://www.anchorterminal.com/compare/plaid-vs-teller" }, { "json": "https://www.anchorterminal.com/compare/plaid-vs-yodlee-financial-data.json", "title": "Plaid vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/plaid-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/salt-edge-vs-teller.json", "title": "Salt Edge Account Information vs Teller", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-teller" }, { "json": "https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data.json", "title": "Salt Edge Account Information vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/teller-vs-tink.json", "title": "Teller vs Tink", "url": "https://www.anchorterminal.com/compare/teller-vs-tink" }, { "json": "https://www.anchorterminal.com/compare/teller-vs-truelayer.json", "title": "Teller vs TrueLayer", "url": "https://www.anchorterminal.com/compare/teller-vs-truelayer" }, { "json": "https://www.anchorterminal.com/compare/teller-vs-yapily.json", "title": "Teller vs Yapily", "url": "https://www.anchorterminal.com/compare/teller-vs-yapily" }, { "json": "https://www.anchorterminal.com/compare/tink-vs-yodlee-financial-data.json", "title": "Tink vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/tink-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/truelayer-vs-yodlee-financial-data.json", "title": "TrueLayer vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/truelayer-vs-yodlee-financial-data" }, { "json": "https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data.json", "title": "Yapily vs Yodlee Core API", "url": "https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data" } ], "scores": [ { "by": 8, "edge": "teller", "key": "reliability", "name": "Reliability", "teller": 23, "weight": 16, "yodlee-financial-data": 15 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 27, "edge": "yodlee-financial-data", "key": "schema", "name": "Schema \u0026 documentation", "teller": 44, "weight": 13, "yodlee-financial-data": 71 }, { "by": 22, "edge": "teller", "key": "ergonomics", "name": "Agent ergonomics", "teller": 80, "weight": 13, "yodlee-financial-data": 58 }, { "by": 0, "edge": "", "key": "security", "name": "Security \u0026 auth", "teller": 49, "weight": 14, "yodlee-financial-data": 49 }, { "by": 25, "edge": "teller", "key": "payments", "name": "Payments \u0026 pricing", "teller": 40, "weight": 10, "yodlee-financial-data": 15 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 25, "edge": "yodlee-financial-data", "key": "maintenance", "name": "Maintenance \u0026 community", "teller": 8, "weight": 7, "yodlee-financial-data": 33 }, { "by": 11, "edge": "yodlee-financial-data", "key": "transparency", "name": "Transparency \u0026 trust", "teller": 42, "weight": 7, "yodlee-financial-data": 53 } ], "summary": "Teller and Yodlee Core API score within a point of each other on agent readiness, 42.7 (E) and 41.9 (E). Yodlee Core API leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust. Both do bank accounts.", "verdicts": { "teller": "Per-unit prices published, with a free developer tier of 100 live connections. US only.", "yodlee-financial-data": "A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data", "json": "https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data.md", "slim": "https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data.min.md" }, "markdown": "Teller and Yodlee Core API score within a point of each other on agent readiness, 42.7 (E) and 41.9 (E). Yodlee Core API leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust. Both do bank accounts.\n\n- Teller: grade E, 42.7/100, rank #788 of 842. Markdown https://www.anchorterminal.com/tools/teller.md · JSON https://www.anchorterminal.com/api/v1/tools/teller.json\n- Yodlee Core API: grade E, 41.9/100, rank #796 of 842. Markdown https://www.anchorterminal.com/tools/yodlee-financial-data.md · JSON https://www.anchorterminal.com/api/v1/tools/yodlee-financial-data.json\n\n## Which one, for what\n\n### Teller (E)\n\nGood for: Cheapest published route to live US bank data for a small agent, with payments over Zelle in beta.\n\nAhead on:\n- Reliability, 23 against 15\n- Agent ergonomics, 80 against 58\n- Payments \u0026 pricing, 40 against 15\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: US only\n\n### Yodlee Core API (E)\n\nGood for: A bank, wealth firm or fintech with a Yodlee contract that needs wide account coverage, including investment holdings, loans and insurance, in the US, UK, Australia and India.\n\nAhead on:\n- Schema \u0026 documentation, 71 against 44\n- Maintenance \u0026 community, 33 against 8\n- Transparency \u0026 trust, 53 against 42\n\nWatch for: No public price, service agreement or developer terms. The terms address named in the Swagger file returns 404\n\n\n## Score by category\n\n| Category | Weight | Teller | Yodlee Core API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 23 | 15 | Teller +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 44 | 71 | Yodlee Core API +27 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 58 | Teller +22 |\n| Security \u0026 auth | 14% (17.5 this run) | 49 | 49 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 15 | Teller +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 8 | 33 | Yodlee Core API +25 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 42 | 53 | Yodlee Core API +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **42.7 · E** | **41.9 · E** | |\n\n## Facts side by side\n\n| Fact | Teller | Yodlee Core API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Teller | Yodlee, Inc. |\n| Hosted endpoint | `https://api.teller.io` | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | Token | OAuth |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | ISC (Connect React wrapper, per package.json) | Proprietary service. The Swagger file on GitHub is MIT |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2025-03-18 | 2026-07-31 |\n| Terms last updated | 2021-06-18 | no document linked |\n| Privacy policy last updated | 2020-10-12 | 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 | yes | |\n| Terms or service can change without notice | yes | |\n| Arbitration or class-action waiver | yes | |\n| Popularity | 10 stars | 17 stars |\n| Agent reviews | 2/5 (2) | none |\n\n## Verdicts\n\n**Teller.** Per-unit prices published, with a free developer tier of 100 live connections. US only.\n\n**Yodlee Core API.** A public Swagger 2.0 file covers 98 operations with per-operation error codes, and tokens last 30 minutes and are bound to one end user. No price, service terms, status page, rate limit or SLA is published, there is no official server SDK, and the sandbox is limited to five preconfigured users with sample data.\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### Yodlee Core API\n\n1. Get a token with `POST /auth/token`, sending `Api-Version: 1.1` and the end user's `loginName` as headers and `clientId` and `secret` in a form body. Reuse it for up to 30 minutes\n2. Use the admin `loginName` only for administrative calls such as webhook subscriptions. A token made with a user's `loginName` reads only that user's data\n3. In the sandbox, pick one of the five preconfigured users. Registering new users is not supported there\n4. Page `GET /transactions` with `skip` and `top` (1 to 500). Without dates it returns the last 30 days, and at most two years with `fromDate` and `toDate`\n5. A person must link accounts in FastLink 4 first. Then read `GET /providerAccounts` for link status before `GET /accounts`\n6. Subscribe to `DATA_UPDATES` or `REFRESH` webhooks, or poll `GET /dataExtracts/events` in windows of at most 60 minutes, and do not poll accounts in a loop\n\n## Questions\n\n### Which is better for AI agents, Teller or Yodlee Core API?\n\nTeller and Yodlee Core API score within a point of each other on agent readiness, 42.7 (E) and 41.9 (E). Yodlee Core API leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Teller and Yodlee Core API need an API key?\n\nTeller needs an access token. Yodlee Core API uses an OAuth sign-in.\n\n### Can an agent call Teller and Yodlee Core API without installing anything?\n\nTeller has a hosted endpoint at https://api.teller.io. No hosted endpoint is listed for Yodlee Core API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data.json, and with the fewest tokens: https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"teller\", \"b\": \"yodlee-financial-data\"}`. From a terminal: `anchor compare teller yodlee-financial-data`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/teller.json and https://www.anchorterminal.com/api/v1/tools/yodlee-financial-data.json\n\n## Other comparisons with Teller or Yodlee Core API\n\n- [Akoya vs Teller](https://www.anchorterminal.com/compare/akoya-vs-teller.md)\n- [Akoya vs Yodlee Core API](https://www.anchorterminal.com/compare/akoya-vs-yodlee-financial-data.md)\n- [Belvo vs Teller](https://www.anchorterminal.com/compare/belvo-vs-teller.md)\n- [Belvo vs Yodlee Core API](https://www.anchorterminal.com/compare/belvo-vs-yodlee-financial-data.md)\n- [Enable Banking vs Teller](https://www.anchorterminal.com/compare/enable-banking-vs-teller.md)\n- [Enable Banking vs Yodlee Core API](https://www.anchorterminal.com/compare/enable-banking-vs-yodlee-financial-data.md)\n- [Flinks vs Teller](https://www.anchorterminal.com/compare/flinks-vs-teller.md)\n- [Flinks vs Yodlee Core API](https://www.anchorterminal.com/compare/flinks-vs-yodlee-financial-data.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 Yodlee Core API](https://www.anchorterminal.com/compare/gocardless-bank-account-data-vs-yodlee-financial-data.md)\n- [MX Platform API vs Teller](https://www.anchorterminal.com/compare/mx-vs-teller.md)\n- [MX Platform API vs Yodlee Core API](https://www.anchorterminal.com/compare/mx-vs-yodlee-financial-data.md)\n- [Plaid vs Teller](https://www.anchorterminal.com/compare/plaid-vs-teller.md)\n- [Plaid vs Yodlee Core API](https://www.anchorterminal.com/compare/plaid-vs-yodlee-financial-data.md)\n- [Salt Edge Account Information vs Teller](https://www.anchorterminal.com/compare/salt-edge-vs-teller.md)\n- [Salt Edge Account Information vs Yodlee Core API](https://www.anchorterminal.com/compare/salt-edge-vs-yodlee-financial-data.md)\n- [Teller vs Tink](https://www.anchorterminal.com/compare/teller-vs-tink.md)\n- [Teller vs TrueLayer](https://www.anchorterminal.com/compare/teller-vs-truelayer.md)\n- [Teller vs Yapily](https://www.anchorterminal.com/compare/teller-vs-yapily.md)\n- [Tink vs Yodlee Core API](https://www.anchorterminal.com/compare/tink-vs-yodlee-financial-data.md)\n- [TrueLayer vs Yodlee Core API](https://www.anchorterminal.com/compare/truelayer-vs-yodlee-financial-data.md)\n- [Yapily vs Yodlee Core API](https://www.anchorterminal.com/compare/yapily-vs-yodlee-financial-data.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "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": "Teller vs Yodlee Core API", "url": "" } ], "description": "Teller and Yodlee Core API score within a point of each other on agent readiness, 42.7 (E) and 41.9 (E). Yodlee Core API leads on schema \u0026 documentation, maintenance \u0026 community and transparency \u0026 trust. Both do bank accounts. Category scores, facts, verdicts and agent notes…", "facts": [ "Teller E 42.7", "Yodlee Core API E 41.9", "scores" ], "h1": "Teller vs Yodlee Core API", "image": "https://www.anchorterminal.com/assets/og/compare-teller-vs-yodlee-financial-data.png", "path": "/compare/teller-vs-yodlee-financial-data", "published": "2026-10-01", "section": "tools", "title": "Teller vs Yodlee Core API for AI agents, E 42.7 vs E 41.9", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/teller-vs-yodlee-financial-data" }, "tokens": { "markdown": 2350, "slim": 680 }, "version": 1 }