wallet-api

What This Skill Does

The Wallet API skill provides a seamless interface between the OpenClaw AI agent and the BudgetBakers Wallet personal finance ecosystem. By authenticating via a secure API token, the skill allows you to retrieve real-time data regarding your personal finances. It supports querying core entities such as accounts, categories, transaction records, budgets, and templates. The skill handles the complexities of the REST API, including pagination, filtering, and rate-limiting, allowing you to perform deep analysis on your spending patterns without manual data exports or manual app navigation.

Installation

To integrate this skill into your environment, use the OpenClaw CLI tool. Run the command clawhub install openclaw/skills/skills/andresubri/wallet-api. Once installed, you must obtain a valid API token from the BudgetBakers web portal at web.budgetbakers.com. Set this as an environment variable in your system configuration: export WALLET_API_TOKEN="your_token_here". Ensure your Wallet account is on a Premium plan, as the API functionality is restricted to premium users only.

Use Cases

1. Automated Expense Auditing: Automatically fetch transactions from the last month to categorize spending habits.
2. Budget Monitoring: Query budget data to receive proactive notifications if a specific category limit is approaching.
3. Financial Reporting: Aggregating account balances across different entities to get a comprehensive view of your net worth.
4. Search and Discovery: Quickly find specific transactions by payee or amount ranges, such as identifying all Amazon purchases between $100 and $500.

Example Prompts

1. "Check my recent transactions from this month and tell me how much I spent on groceries."
2. "Show me the current balance of my main checking account and list any budgets that are currently overdrawn."
3. "List all transactions from the last 30 days where the payee includes 'Amazon' and the amount was greater than 50 dollars."

Tips & Limitations

• Rate Limiting: The API is restricted to 500 requests per hour. If you exceed this, the system will return a 429 error. Use the agentHints=true parameter to receive proactive warnings.
• Synchronization: Data might experience a slight delay appearing after you record a purchase in the app. Always check the X-Last-Data-Change-At header if the data appears stale.
• Filtering: Utilize the provided filter prefixes (eq, contains, gte, lte) to perform precise queries rather than fetching large datasets, which helps stay under the request limit.