The Problem That Started This
I was sitting one night going through my bank statement and realized I was paying for Notion, Cursor, GitHub Pro, Figma, and three other tools I had not opened in months. All in USD. All with forex markup eating another 5 to 7% on top. I opened every "subscription tracker" app I could find and they all did the same thing, showed me a list. None of them could actually do anything about it.
That was the moment I decided to build something that acts, not just tracks.
What I Built
Unsubscribely is an autonomous subscription management platform where an AI agent controls your money, not you manually logging into 12 different websites.
Here is how it works. You add your subscriptions and lock funds into a smart contract vault you own on Algorand. From that point the OpenClaw agent, directly integrated with an LLM brain, takes over completely. Three days before any renewal it messages you on Telegram and asks keep or cancel. You reply in plain english or even send a voice note. The agent understands you, makes the decision, and executes it on-chain. No dashboards to check. No forms to fill. Just a conversation.
If you say keep, the payment goes through autonomously. If you say cancel, the vault is killed, your funds come back to your wallet, and an immutable cancellation proof gets written on the blockchain so no service can ever claim you did not cancel. The agent also handles browser automation, it will log into the service website and click cancel for you if you have saved credentials.
The monthly savings for a typical Indian developer adds up fast:
$$\text{Monthly Savings} = \sum_{i=1}^{n} \text{ForgottenSub}_i + \text{ForexLoss}_i$$
The Stack
Built on Algorand smart contracts with on-chain Box Storage for permanent billing history, OpenClaw agent with Gemini LLM for intent and decision making, Supabase for user data, Telegram bot for the conversational interface, Playwright for browser automation, and an MCP server with 12 tools so Claude or ChatGPT can also manage your subscriptions through natural language. External AI agents pay per API call using x402 payment protocol where payment itself is the credential.
What Broke and What I Learned
I had never written a smart contract before this. The hardest bug was in the vault contract itself. Every payment release writes a permanent record into Algorand Box Storage, but allocating that storage shifts the contract minimum balance mid-transaction. My first ten deployments failed silently with no useful error. I had to read the AVM specification directly to understand what was happening and restructure the transaction order entirely.
The second bug was the agent calling the wrong method on upgraded vaults because my database had stale data. The fix was to stop trusting the database and read contract state directly from the blockchain before every single operation. That one line of reasoning, on-chain state is truth and the database is just a cache, changed how I think about building with blockchains permanently.
Try It
Built With
- ai
- algorand
- blockchain
- gemini
- javascript
- node.js
- openclaw
- playwright
- python
- react
- react-native
- supabase
- tailwindcss
- telegram
- typescript
- vite
Log in or sign up for Devpost to join the conversation.