I run a parking database for central Sendai, Japan, as a solo side project. As of November 17, 2026, it covers 1,188 parking lots. Prices are checked against each operator's official information one by one; anything I couldn't verify stays in the database with an "unverified" label instead of a made-up number.
The site: https://sendai-parking-db.pages.dev/
My development and operations partner for this project is Muse, a personal AI agent. This post is a field report: what I actually hand over to the agent, and what I deliberately keep in my own hands.
What I delegate
- Reading operators' official pages and cross-checking prices against the database (flagging mismatches)
- Building and iterating on the site itself (search UI, map view, chat-based search)
- Scheduled monitoring jobs (form responses, vacancy observations) that only report when something changes
- Drafting articles and posts
What I don't delegate
- Final decisions on anything public — I review before release
- Confirming anything that moves money
- Filling gaps with estimates — if a price is unknown, it stays labelled unknown
Rules that made it work
- Keep uncertain data, but label it. Never state a guess as a fact.
- Scheduled jobs report only on change, which keeps the noise down.
- Anything that needs approval is routed to one place, so nothing gets stuck in a side thread.
A note on invite codes
Muse has an invite code system. Mine is YAN3V3. If you enter it in Settings within 48 hours of joining, we both receive 1 billion Muse tokens.
- Join: https://muse.ai/join
- App: Settings → Redeem token
- Web: Settings → General → Usage → Redeem invite code
- Code page (with a copy button): https://muse.ai/s/muse-invite-code-yan3v3-english-xuf6xz9w2fxkgi/DVsk9awGJU_n6SJYZDXaNZxCPGoHiCRuQxqE3pAX2kY
This is my personal invite code, shared by me — not an official Muse announcement.
Top comments (0)