Aavegotchi Petter
Scheduled on-chain automation service — the first piece of infrastructure that became the agent stack.
- Year
- 2025
- Role
- Solo build — backend, scheduler, admin dashboard
- Discipline
- AI Tooling
The problem
Some on-chain actions have to happen on a fixed cadence or the asset degrades. Doing that by hand does not scale past a handful of assets, and doing it from a script on a laptop fails the first time the laptop sleeps.
The approach
A Node and TypeScript backend owns the transaction logic and exposes it over a REST API, with a cron layer driving execution on schedule and Upstash KV holding state between runs so restarts are safe. A separate Nuxt admin dashboard handles configuration and monitoring, keeping the operator interface out of the service that signs transactions.
Outcome
Reliable unattended on-chain automation running against Base. The scheduling, key-handling, and operator-interface patterns here are what the later agent orchestration work was built on.
Details
- Node + TypeScript service with a REST API and cron-driven execution
- Upstash KV for restart-safe state
- Nuxt admin dashboard kept separate from the signing service
Built with
- Node.js
- TypeScript
- Nuxt
- Vue
- REST API
- Upstash
- Base
Links
Need something like this? AI Tooling & Developer Infrastructure is what I do.
Related work
abracadabra
2026Biometric-gated secrets vault that lets AI agents fetch credentials without a human in the loop.
AI Toolingcron402
2026Cron-as-a-service for AI agents, billed per run in USDC over the x402 protocol — no accounts, no API keys.
AI Tooling
Last updated .