What problem does it solve?
Agents need a safe, read-only way to answer user questions about their Link-connected financial data — such as spending history, account balances, and linked accounts — without moving money or exposing payment credentials.
Core Features & Use Cases
- Transaction Queries: List and filter Link and bank-imported transactions by date range, category, origin, or source to answer spending and income questions.
- Balance Retrieval: Fetch current and available balances for cash and credit accounts, with currency-aware formatting and per-source breakdowns.
- Source Inspection: List connected wallet sources with metadata like institution, type, capabilities, and granted actions.
- Scoped Authentication: Request only the minimum source actions needed (e.g., read_balances, read_link_transactions) via login or session upgrade flows.
- Use Case: A user asks "How much did I spend on restaurants last month?" — the agent authenticates with read_link_transactions, queries transactions filtered by date and category, and returns a summarized total.
Quick Start
Ask the agent to check your Link balance or summarize your recent spending, and it will authenticate and retrieve only the data needed to answer.