AgentRemit

AgentRemit is an autonomous remittance agent for the Lagos corridor. Set a target NGN/USDC rate, deploy your agent, and it watches 24/7 executing the swap via Uniswap, guaranteeing delivery through KeeperHub, and storing a tamper-proof receipt on 0G Storage the moment your rate hits. No banks. No middlemen. No missed rates.

AgentRemit is an autonomous remittance agent for the Lagos corridor built on Next.js 15, TypeScript, and four sponsor integrations. A sender connects a wallet via RainbowKit + Wagmi, sets a recipient address, USDC amount, and target NGN rate then deploys a server-side agent job that watches exchange rates and executes automatically when the target is reached. How the pieces fit together: The agent is a durable server-side job, not a client-side loop. In production it uses Upstash Redis + QStash for scheduling QStash calls /api/agent/worker every minute since Vercel Hobby cron is too infrequent for real-time rate watching. Without Redis, the app rejects job creation unless AGENTREMIT_ALLOW_MEMORY_JOBS=true is explicitly set, preventing silent degradation. Every major state transition created, watching, rate hit, quote received, execution submitted, confirmed, receipt saved is written to 0G Storage memory so the full lifecycle is inspectable onchain. The Uniswap integration uses the Trading API /quote endpoint when UNISWAP_API_KEY is configured, with Uniswap v3 SDK contract quoting as a local fallback. The worker fetches a quote when the live rate crosses the configured target, then submits execution through KeeperHub's Direct Execution API but only if live execution is explicitly enabled via AGENTREMIT_ENABLE_LIVE_EXECUTION=true, capped by AGENTREMIT_MAX_LIVE_USDC, and the owner wallet is on an allowlist. The execution path fails closed by default. Receipts include the Uniswap quote snapshot, KeeperHub job ID, transaction hash, and 0G receipt root hash. ENS resolution is wired via @ensdomains/ensjs on Sepolia recipients can enter .eth names and the UI resolves them to addresses in real time. The notably hacky part: @0glabs/[email protected] uses the old Flow submit(Submission) ABI, but the Galileo testnet (chainId: 16602) expects the newer wrapped shape: submit({ data, submitter }). Every upload was silently reverting at gas estimation with require(false) on the flow contract 0x22E03a6A89B950F1c82ec5e74F8eCa321a105296 no documentation, no error message, no SDK changelog entry. The fix required manually constructing the on-chain Flow transaction with the correct Galileo ABI, computing storage fees directly from pricePerSector, then handing back to the SDK's segment upload layer. Uploads serialize in process to prevent nonce collisions when multiple state transitions fire in rapid succession. Three seed receipts confirmed on Galileo with root hashes committed to scripts/seed-output.json. A /api/readiness endpoint surfaces all configuration gaps missing Redis, fallback FX data, disabled KeeperHub execution, incomplete 0G configuration as visible dashboard banners instead of silent failures. The app shows exactly what it can and cannot do at runtime, which made debugging across four integrations significantly faster.