Detect and manage subscriptions on behalf of an agent's principal: cancel or renegotiate

Steps

1. Build or integrate a subscription detection pipeline: parse email receipts and bank/card statements for recurring charge signatures (same merchant, similar amount, monthly/annual cadence); tag detected subscriptions with merchant, amount, frequency, and last charge date.
2. Present the detected subscription inventory to the human principal for review before taking any action — cancellation is irreversible and the agent must not cancel subscriptions without confirmed authorization.
3. For cancellation on a known platform with an API (e.g., a SaaS with a billing API or customer portal): use the API or portal cancellation flow; for platforms without an API, use a structured web automation flow against the account settings page, handling confirmation dialogs explicitly.
4. After cancellation, verify the status by checking the platform's subscription page or waiting for a cancellation confirmation email; do not consider the task complete based solely on having submitted the cancellation form.
5. If the goal is renegotiation (e.g., downgrade to a cheaper plan, apply a retention discount): treat this as a supervised task where the agent prepares the action but a human confirms before executing, since the outcome is highly variable.
6. Log all subscription actions (detected, actioned, confirmed, failed) with timestamps, merchant, amount affected, and the human authorization that triggered the action.