ai
3 мин
7 сентября 2026 г.
Источник: Dev.to AI Feed

How I Built an Autonomous AI Agent That Earns USDC While I Sleep

Nikhil Ranka
Nikhil Ranka
RSS AI Ingest
How I Built an Autonomous AI Agent That Earns USDC While I Sleep

How I Built an Autonomous AI Agent That Earns USDC While I Sleep Target audience: developers interested in creating self‑sustaining AI services that receive micropayments in USDC. The goal was to run an always‑on agent that performs a nar...

How I Built an Autonomous AI Agent That Earns USDC While I Sleep Target audience: developers interested in creating self‑sustaining AI services that receive micropayments in USDC. Overview The goal was to run an always‑on agent that performs a narrow, well‑defined task (text summarization) and gets paid per invocation in USDC on the Base blockchain. The agent does not “learn” while it sleeps; it simply waits for requests, validates a payment, runs a model, and returns the result. The architecture is deliberately minimal to keep operational complexity low and to make trade‑offs explicit. Core components Component Responsibility Chosen tech Why Request handling & payment verification Accept HTTP POST, check x402 payment header, reject if insufficient Cloudflare Workers (JavaScript) Serverless, global edge, free tier sufficient for low traffic AI inference Run a summarization model on the input text HuggingFace transformers.js (distilbart‑cnn‑12‑6) Runs entirely in the Worker sandbox, no external API keys, modest size (~50 MB) Payment settlement Record earned USDC for later withdrawal Simple server‑side counter (KV store) + manual claim via a wallet Avoids integrating a full smart contract; x402 already guarantees payment off‑chain Observability Log requests, errors, and earnings Built‑in Worker logs + optional external logging service Minimal overhead, sufficient for debugging The flow for each request is: Client sends POST /summarize with JSON { "text": "…" } and an X-Payment header containing a signed x402 proof. Worker verifies the proof against the agent’s public key and the configured price (e.g., $0.02 USDC). If verification passes, the Worker runs the model, returns the summary, and increments an earnings counter. If verification fails, the Worker returns 402 Payment Required with a helpful error message. Payment verification with x402 x402 defines a HTTP‑based scheme for attaching a cryptographic proof of payment to a request. The proof consists of: payload: the request method, path, and body hash. signature: an ECDSA signature over the payload using the payer’s private key. paywall: the price in USDC (encoded as a 64‑bit integer with 6 decimals). The worker needs the agent’s public key to verify the signature. Below is a stripped‑down verification function using the ethers library (available via CDN in Workers). // x402Verify.js import { ethers } from "https://cdn.jsdelivr.net/npm/ethers@6.7.0/dist/ethers.min.js"; const AGENT_PUBLIC_KEY = "0xA1b2C3d4E5f67890..."; // replace with your agent's address export async function verifyX402(request, expectedPriceMicroUSDC) { const payloadHeader = request.headers.get("X-Payload"); const sigHeader = request.headers.get("X-Signature"); const paywallHeader = request.headers.get("X-Paywall"); if (!payloadHeader || !sigHeader || !paywallHeader) { throw new Error("Missing x402 headers"); } // Reconstruct the payload that was signed const payload = JSON.parse(atob(payloadHeader)); // Expected shape: { method, path, bodyHash } const { method, path, bodyHash } = payload; // Verify paywall amount (USDC with 6 decimals) const price = BigInt(paywallHeader); if (price env.EARNINGS.add("usdc", PRICE_MICRO_USDC)) ); // 5️⃣ Return result return new Response(JSON.stringify({ summary }), { headers: { "Content-Type": "application/json" }, }); }, }; Explanation of the snippet The Worker checks the HTTP method and path early to avoid unnecessary work. Payment verification is performed before any model inference, guaranteeing that we never spend compute on unpaid requests. Earnings are aggregated in a KV store (EARNINGS) using ctx.waitUntil so the response isn’t delayed by the write. All heavy lifting (model load, inference) stays inside the Worker; no external API keys are required, reducing attack surface. Operational considerations & honest trade‑offs Aspect What we chose Pros Cons / Limitations Compute Serverless Worker + WASM model No server management, automatic scaling, free tier covers low traffic Cold start latency, limited CPU (no GPU), model size constrained by Worker memory (~128 MB) Payment x402 off

Хотите внедрить ИИ в ваш бренд?

Спроектируем и развернем автономных агентов и современный цифровой стек под ваши задачи.

Рассчитать проект