nowfound

Alternatives

Products that do what Backproto – network backpressure routing applied to AI agent payments does

I’ve been applying backpressure routing (Tassiulas-Ephremides, 1992) to payment flows between AI agents. Streaming payment protocols let agents pay each other in real time, but there's no congestion control. When a downstream agent hits capacity, money keeps arriving. No reroute, no throttle, no feedback signal. TCP solved this for data networks. Agent payment networks haven’t. Backproto makes receiver-side capacity a protocol primitive. Agents stake tokens to declare capacity (concave sqrt cap makes Sybil splitting unprofitable), dual-signed completion receipts track actual performance, and…

  1. 1

    Money movement for AI agents

    Jul 2026 · home.getsequence.io

  2. 2

    Give AI agents spending power without giving up control

    Apr 2026

  3. 3

    New technology to maximize transaction approvals

    2023

  4. 4
    pay.sh347

    Discover, access, and pay for any API autonomously

    May 2026 · pay.sh

  5. 5

    Open-source unified interface for agent harnesses

    21d ago · harnessrouter.ai

  6. 6
    Fewsats159

    The payment infrastructure for AI agents

    2025

  7. 7SM

    We built a model router that plugs into coding agents (e.g. Claude Code, Codex, Cursor, etc.) and intelligently sends requests to the best model to serve them. Here's a quick demo of running it locally: https://www.youtube.com/watch?v=isKhAyivtfM. At Weave, we write most of our code with AI, and it's been getting more expensive. This came to a head when Opus 4.7 was released and, thanks to its tokenizer changes, our costs shot up. We knew we didn't need Opus for everything but we didn't want to lose out on the intelligence for the cases where you really need it. So we decided…

    Jun 2026 · github.com

  8. 8

    Trajectory-aware LLM routing that cuts agent cost

    10d ago · iq-routing.com

  9. 9TB

    Hi HN, My team and I are building Tabstack to handle the "web layer" for AI agents. Launch Post: https://tabstack.ai/blog/intro-browsing-infrastructure-ai-ag... Maintaining a complex infrastructure stack for web browsing is one of the biggest bottlenecks in building reliable agents. You start with a simple fetch, but quickly end up managing a complex stack of proxies, handling client-side hydration, and debugging brittle selectors. and writing custom parsing logic for every site. Tabstack is an API that abstracts that infrastructure. You send a URL and an intent; we…

    Jan 2026

  10. 10

    The internet-native payment standard for AI agents

    Mar 2026

  11. 11

    Open protocol for AI agents to share memory, not tokens

    Mar 2026

  12. 12
    Web Speed118

    Kill the 'Token Tax.' 90% cheaper agents.

    May 2026 · getwebspeed.io

  13. 13
    Agihalo68

    LLM Router for A.I Agent & Saas with x402

    Jan 2026

  14. 14AP

    Hey all! I recently gave a workshop talk at PyCon Greece 2025 about building production-ready agent systems. To check the workshop, I put together a demo repo: (I will add the slides too soon in my blog: https://www.petrostechchronicles.com/) https://github.com/Aherontas/Pycon_Greece_2025_Presentation_... The idea was to show how multiple AI agents can collaborate using FastAPI + Pydantic-AI, with protocols like MCP (Model Context Protocol) and A2A (Agent-to-Agent) for safe communication and orchestration. Features: - Multiple agents running in containers -…

    Sep 2025 · github.com

  15. 15

    Lossless token compression reduces costs by 50%‑90%.

    12d ago · 154.12.86.206

  16. 16RF

    I've been building https://routing24.com for a while, a free route optimization and planning app for businesses. One of the things that bothered me for quite a time is inability of browser agents to work with Routing24. We have tons of natural tasks for AI: - data ingestion, to figure out data coming from user's side (csv and Excel); - geocoding quality validation (to explain user what they need to correct and their addresses and how); - steep learning curve for business users (who have sense of what they want from route optimization, but setting up the model takes significant time…

    Jul 2026 · github.com

  17. 17

    x402 commerce layer for AI agents — beyond raw HTTP payments

    May 2026

  18. 18

    ask an agent to buy something, and it hits a wall. Why?

    Mar 2026

  19. 19

    An agent-to-agent protocol built for harness engineering

    Jul 2026 · cosmonapse.com

  20. 20

    Hey HN! We are building HarnessRouter, a canonical API for running Codex, Claude Code, Hermes, and other managed agent harnesses as your product backend. Before building HarnessRouter, I used to build our own agent harness for our products. I tried LangGraph, agent SDKs from different vendors, pydantic, LLM tool use / function call, and so on. It's a very heavy lifting engineering effort, and I am disappointed about the agent deliveries compared to what Codex, CC can deliver. That changed my mindset. The frontier labs and famous open source communities are already putting so much…

    20d ago · github.com

  21. 21

    Self-hosted AI proxy. Your data never leaves your network.

    Jul 2026 · tokenveil.eu

  22. 22

    Give your AI agents a payment gateway. No signup, no KYB

    Jun 2026 · payram.com

  23. 23RR

    Hi HN, I’m one of the builders of Rayline. Rayline is a Claude Code compatible LLM gateway. It intercepts and overrides claude code’s internal routing and lets you route subagent calls to different models instead. For example, you can run the main agent on Opus, some subagents on cloud-hosted open models, and other subagents on-device. We’ve seen others implement routing for claude code as tools the agent can invoke. In our experience, that doesn’t work well because it requires the main agent to use tokens to think about + call the tools, and LLMs are generally a very inefficient way to make…

    Jun 2026 · rayline.ai

  24. 24
    Relay1

    agent payments infra: wallets, balances, billing and top-ups

    Mar 2026

Ranked by how close each launch is in meaning, then by votes. Refine with a description →