Find recurring expenses and audit subscriptions
Use the read-only Lunch Money connector to review expected bills, distinguish saved recurring items from suggestions, and prepare a provider-by-provider cancellation checklist.
Examples on this page are fictional. Lunch Money for Agents is an unofficial integration and is not affiliated with or endorsed by Lunch Money.
Before you start
Connect through the setup flow, then ask for a narrow date range. Enter your Lunch Money API token only on the browser connection page, never in chat or client configuration.
The connector can read recurring items. It cannot create or edit them, cancel a subscription, change a payment, or move money. Read the security and data explanation before sending financial records to an AI client.
1. Ask for recorded recurring items
Start with items already returned as recurring records. Both dates are required when you provide a range. This prompt maps to lunchmoney_list_recurring_items with include_suggested: false.
List my recorded recurring items from 2026-09-01 through 2026-09-30. Show payee, amount, currency, cadence, anchor date, and status. Use include_suggested false. Keep currencies separate and do not infer a recurring expense from transaction history.
The tool returns expected recurring transactions, not proof that a charge posted or that a provider will bill on a particular day. Treat the anchor date as a schedule reference and confirm the next charge, price, and cancellation terms with the provider.
2. Turn the result into a monthly review
A fictional result could look like this. The two monthly rows total 56.99 USD for this review window. Keep the 71.88 USD annual item separate; dividing it by twelve gives a 5.99 USD planning estimate, not a monthly charge.
| Fictional payee | Expected amount | Cadence | Schedule anchor | Status |
|---|---|---|---|---|
| Northstar Video | 14.99 USD | Month | Sep 12 | Reviewed |
| Harbor Fitness | 42.00 USD | Month | Sep 18 | Reviewed |
| Cloud Keep | 71.88 USD | Year | Oct 19 | Reviewed |
For each row, compare the expected amount with the provider's current plan page or receipt. Mark what you use, what you need to investigate, and what you plan to cancel. Do not paste account numbers, tokens, or full transaction exports into the prompt.
3. Review suggestions separately
If you want candidates that Lunch Money has suggested, make a second request with include_suggested: true. Keep each item's returned status visible. A suggested item is a review candidate, not a confirmed subscription.
List recurring-item candidates for the same dates with include_suggested true. Separate reviewed records from suggestions using the returned status. Do not label a suggestion as confirmed, and do not infer a subscription from one transaction.
For example, a single fictional 48.25 USD rail ticket in transaction history is a one-off expense unless there is other verified evidence. A suggested weekly grocery pattern is still only a candidate until you review it in Lunch Money.
4. Check dates and cancel with the provider
Confirm the provider, plan name, expected amount, currency, and next billing date outside the connector.
Check trial end dates, annual renewals, and notice periods in the provider's current terms.
Cancel directly with the provider. The connector cannot perform the cancellation.
If needed, update the recurring item in Lunch Money itself. This connector cannot edit Lunch Money records.
Keep the provider's confirmation and check a later statement for another charge.
What this workflow can and cannot establish
It can organize recurring-item records returned by Lunch Money for a bounded review. It cannot prove a subscription is active, predict an exact charge, interpret a contract, or cancel anything. Review provider records before acting.
For connection instructions, use the website setup picker or the repository's client setup guide. For an overview of available read-only questions, return to Lunch Money for Agents.