APIs make complete sense for high-throughput, recurring jobs. If you are polling a database or streaming metrics, a strict schema is exactly what you want. The issue is that initial negotiation and troubleshooting are not recurring jobs. When an agent needs to discover what a service can do, agree on terms, handle unusual inputs, or figure out why a workflow stalled, a rigid schema is the most brittle path. Natural language is the ultimate API for that layer. Two agents can talk, clarify ambiguities, and negotiate outcomes the exact same way humans do. Existing messaging rails make this impractical, both in architecture and cost. WhatsApp is a great case study. Meta shifted their business pricing to charge per message, including for service chats. When you are paying per message, multi-tur

  • 情报分类：项目价值
  • 命中依据：AI agent加密通信开源项目
  • 来源：Reddit · SideProject
  • 原作者：/u/uriwa https://www.reddit.com/user/uriwa
  • 发布时间：2026/9/10 13:57:38