How I Built an Autonomous AI Agent That Earns USDC While I Sleep By a developer who prefers shipping code to chasing hype.
Why an “earning‑while‑sleeping” agent?
Autonomous agents are usually discussed in the context of research prototypes or toy demos.
In practice, the biggest blocker to putting an LLM‑driven process into production is the cost‑revenue loop: you spend on inference, storage, and networking, but you rarely see a direct financial return unless you wrap the agent in a paid API or a subscription model.
I wanted to test whether a minimal, self‑contained agent could receive micro‑payments for each useful action it performs, settle those payments in a stablecoin (USDC) on a low‑fee L2 (Base), and keep running without manual intervention.
The goal wasn’t to build a “money‑making bot” but to explore the engineering trade‑offs of payment‑driven autonomy.
High‑level Architecture Task Queue – A simple HTTP server that exposes x402-paid endpoints.
Each endpoint declares a price in USDC (e.g., $0.01 per call).
The caller must attach a valid x402 payment proof before the request is processed.
Agent Core – An asyncio‑driven loop that pulls pending tasks from the queue, runs a lightweight LLM (via a local llama.cpp server or a hosted API), executes any needed side‑effects (e.g., data lookup, simple computation), and returns a result.
Payment Handler – Verifies the x402 proof, mints a receipt, and, if the proof is valid, initiates a USDC transfer on Base to the agent’s wallet.
State Store – SQLite (or PostgreSQL) for persisting task IDs, payment nonces, and agent memory.
Observability – Structured logging (JSON) plus Prometheus metrics for latency, success/failure rates, and USDC balance.
The whole system runs as a single Docker container (≈150 MB) on a cheap VPS; the only external dependency is a Base RPC endpoint (e.g., Infura or Alchemy) and, optionally, a USDC‑issuer API for fiat‑on‑ramp if you need to top‑up the wallet.
Technical Details & Code Snippets Below are the essential parts of the implementation.
I kept them deliberately minimal so you can copy‑paste them into a repo and iterate.
- x402 Payment Verifier The x402 spec defines a header containing a JSON‑Web‑Token‑like payload: .
We verify the signature against the caller’s Ethereum address and check that the matches the endpoint’s price.
2.
Agent Core – Task Loop The core pulls tasks from an in‑memory queue (you could swap this for Redis or a DB table).
Each task includes the HTTP method, path, and any payload sent by the caller.
3.
Payment Handler – USDC Transfer on Base We use to send a simple ERC‑20 transfer.
The agent must hold enough USDC in its wallet; you can top‑up via a fiat‑on‑ramp or by receiving payments from other agents.