Integrate Teller Connect (the browser/native SDK) into your application; initialize it with your application_id and on successful enrollment receive an enrollment containing an access_token and accounts list
Store the access_token server-side; authenticate all Teller API requests using HTTP Basic Auth with the access_token as the username and an empty password
Retrieve accounts: GET /accounts returns all accounts for the enrollment; each account has an id, type, subtype, name, institution, and links to sub-resources
Retrieve transactions: GET /accounts/{account_id}/transactions; use the count and from_id query parameters for pagination — from_id should be set to the last transaction ID received to fetch older records
For balance checks: GET /accounts/{account_id}/balances returns ledger and available balances; note these are live requests to the institution and may be slower than cached data
Known gotchas
Teller uses mutual TLS (mTLS) for API authentication in addition to the access_token; your server must present the client certificate issued to your application or requests will be rejected
Teller Connect enrollments are per-institution per-user; a user with accounts at two banks requires two separate enrollment flows to obtain two separate access_tokens
Some institutions supported by Teller use screen-scraping rather than direct API connections; data freshness and field completeness may differ from institutions with native API support
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp