🤓 Latest Submissions
Kynet AI
The Problem We built Kynet because we noticed a huge gap between AI demos and reality. In demos, agents are perfect. In the real world, they are incredibly fragile. An agent might be running a perfect workflow, but the moment it hits a CAPTCHA, a missing API key, or a website layout change, it crashes. It has no way to "unstuck" itself. Our Solution Kynet is a capability network that gives agents a way to pay their way out of problems. We call this the "Escalation Ladder." Streams: First, the agent tries to buy a pre-made Python tool from our marketplace using USDC. Genesis: If no tool exists, the agent uses Gemini to write, test, and deploy its own tool in real-time. Relay: If code fails (like a visual verification task), the agent pays a human via Telegram to solve it. How we built it We used Arc L1 for settlement because the fees ($0.001) make micropayments actually viable. For the agent's financial brain, we used Circle Developer-Controlled Wallets. This was critical because agents need to transact autonomously—they can't wait for a human to sign a transaction in a browser extension. Circle Product Feedback Products used: Circle Developer-Controlled Wallets, USDC, Arc L1 Testnet. Why we chose them: Our users are AI agents running on servers, so we needed a headless wallet setup with no browser pop-ups or manual signing. Circle’s Developer-Controlled Wallets let us execute transfers programmatically based purely on agent logic, which fit our use case perfectly. What worked well: Once set up, wallet-to-wallet transfers were smooth and reliable. Arc’s transaction speed was fast enough to avoid slowing down our agents, and settlement was consistent. What could be improved: The Entity Secret setup caused a lot of friction. We ended up abandoning a few accounts after misconfiguring it, since there was no clear way to reset the secret in the UI. Requiring local scripts for secret generation felt unnecessarily complex.
24 Jan 2026
