Manage the Subscription Lifecycle
Every recurring relationship has a lifecycle. Subscriberbot manages all of it — subscribe, unsubscribe, manage, and view (full CRUDL) — from one place, regardless of category.
The lifecycle
Discover ─▶ Subscribe ─▶ Use ─▶ Renew ──┐
│ │
▼ ▼
Upgrade / Downgrade Pause
│ │
└────▶ Cancel ◀┘
Core actions
Every action is available through the API, the dashboard, or the Concierge. Where a provider has shipped an adapter, actions execute first-party (true one-click subscribe/cancel). Where it has not, Subscriberbot assists with the steps.
mutation Upgrade {
subUpdateRelationship(id: "rel_123", input: { planId: "plan_pro_annual" }) {
id
plan { name price interval }
}
}
mutation Cancel {
subCancelRelationship(id: "rel_123", reason: UNUSED) {
id
status # CANCELLED
effectiveDate
}
}
Renewals
The Renewal Agent tracks every renewal and auto-renewal date and emits a RenewalDetected event ahead of time. You can review upcoming commitments at any moment:
query {
subListRenewalEvents(window: NEXT_30_DAYS) {
relationship { provider { name } }
renewalDate
amount
autoRenew
}
}
The Digital Asset Vault
As relationships generate documents, Subscriberbot files them in the Digital Asset Vault — invoices, contracts, licenses, receipts, warranties, and certificates — each linked to its Relationship so nothing is lost when a subscription ends.
Bundles and consolidation
The Concierge can consolidate overlapping relationships, and Subscription Bundles can package related services (for example, several AI tools) into a single, often cheaper, bundle. See the AI Brain for how overlap is detected.
Next
- Automate lifecycle actions with policies.
All lifecycle operations target production by default. To use local or alpha, set BURDENOFF_ENV=local|alpha or pass the appropriate endpoint. See Environment Selection for endpoint details.