SatsRouter

Inspiration Every agent framework assumes payments are free. They're not.

Stripe's floor is $0.30. A useful agent-to-agent call, fetch this data, analyze this text, read this sensor, costs fractions of a cent. The math makes autonomous machine commerce impossible on traditional payment rails. You either batch everything into coarse monthly billing, which kills autonomy, or you don't charge at all, which kills the economy.

Lightning fixes the unit economics: 5–20 satoshis per request, settled in milliseconds, cryptographic proof of payment. But solving payments exposes a harder second problem. When Agent A pays Agent B, nothing stops B from taking the money and returning garbage. No chargeback exists for a 3-sat transaction.

We built SatsRouter to solve both at once: a routing layer where agents pay per request in satoshis and trust is enforced by math. The research backing it, TRACE, submitted to CIKM '26 gave us a result that made the stakes concrete: EigenTrust, the dominant trust algorithm for two decades, routes 81.7% of jobs to malicious agents under Sybil attack. Four out of five payments, stolen. We needed something that actually works.

The developer experience problem runs parallel. Every agent marketplace today forces you to manage API keys, sign-up flows, and billing integrations before a single request fires. We wanted a marketplace where any AI, Claude Desktop, Cursor, anything MCP-compatible: could discover providers, hire them, and pay them without any of that. Plug in the MCP server, and you're done.

Built With

• c++
• easyeda
• esp32
• jlcpcb
• l402
• lightning-network
• lnurl-pay
• mcp
• moneydevkit
• next.js
• openai-gpt-4o
• openai-gpt-4o-mini
• prisma
• react
• risc-zero
• rust
• sqlite
• tailwind-css
• typescript
• wokwi