Your agent uses the Zeabur CLI to find what is still billing, what data you haven't taken with you, and what still points at Zeabur. When everything is handled, it drafts your refund ticket.
This article is also available in 繁體中文, 简体中文, 日本語, Español, and Bahasa Indonesia.
TL;DR: Moved all your services and want to make sure nothing is left on Zeabur before you ask for a refund? Open a coding agent such as Claude Code or Codex and paste this line:
Read https://zeabur.com/blogs/leaving-zeabur-checklist.md, check what I still have on Zeabur, and draft my refund ticket at the end.Your agent uses the Zeabur CLI already logged in on your computer to list what is still billing, what data you haven't taken with you, and where your other systems still point at Zeabur. It only reads; before it stops or deletes anything, it asks you. When everything is handled, it drafts the ticket, and you send it yourself.
If you haven't moved yet, start with Migrating off Zeabur: hand this guide to your coding agent.
Per the shutdown announcement: from December 1, dedicated servers shut down on their own expiry dates; shared-cluster services are suspended from December 1, and you can still resume them manually to back up your data; on December 31 all services stop.
| Item | How the agent checks | Why it matters |
|---|---|---|
| Personal and team workspaces | zeabur workspace list | Services may live in a team; checking only your personal account misses them |
| Subscription plan | zeabur profile info, zeabur api graphql | A plan that still renews keeps charging you |
| Dedicated servers | zeabur server list, zeabur api graphql | Servers rented through Zeabur shut down and are deleted when they expire; their disks are not kept |
| Projects and services | zeabur project list, service list | Services still running on a shared cluster keep billing; export the data from services with databases or volumes first |
| Domains bought on Zeabur | zeabur domain list-registered | Transfer them to another registrar to keep using them after Zeabur shuts down |
zeabur email status and related commands | Sending domains, API keys and scheduled emails all need handling | |
| AI Hub | Asks whether you used it | The CLI can no longer read AI Hub settings; if you used it, the agent asks Support in the ticket to confirm auto-recharge is off |
| What still points at Zeabur | Searches your code, checks DNS | *.zeabur.app URLs, webhooks and OAuth callbacks stop working after the shutdown |
It ends with three lists:
Things the agent can't reach, or shouldn't decide for you:
A Zeabur token currently has full access to your account. Let the agent use the CLI already logged in on your computer: run npx zeabur@latest auth login in your terminal first, with the account that owns these services.
Once "still billing" is empty, the agent drafts the ticket: your account, a request for an account balance refund, what you've stopped, and anything still open that doesn't block the refund. It contains no passwords, tokens or amounts.
Open a ticket at Zeabur Support, paste the draft and send it. Support confirms the refund amount and decides the refund method in that ticket, and replies there with progress.
Go through the table above in the dashboard, item by item. Then open a ticket at Zeabur Support with your account, a request for an account balance refund, and what you've stopped.