📄 中文摘要
速率限制不仅仅是API问题，更是代理群体架构问题。当单个代理运行时，速率限制只是一个不便；但在运行多个代理进行网站审计、内容发布、监控和数据提取时，速率限制会导致可靠性故障，影响所有依赖任务。通过分享代理面向API的AN评分数据，真实的代理群体运营者反馈表明，真正的问题在于失败行为而非能力。因此，设计代理群体时应围绕速率限制进行规划，而不是与之对抗。理解速率限制的质量层次对于构建有效的代理架构至关重要。
设计能够应对速率限制的代理群体：生产架构指南
📄 English Summary
Designing Agent Fleets That Survive Rate Limits: A Production Architecture Guide
Rate limits are not merely API issues; they represent architectural challenges for agent fleets. While a single agent may find rate limits inconvenient, a fleet of agents performing tasks like site auditing, content publishing, monitoring, and data extraction can face reliability failures that cascade across dependent tasks. Feedback from real fleet operators indicates that the critical issue lies not in capability but in failure behavior. Designing fleets with an understanding of rate limits, rather than against them, is essential. Recognizing the hierarchy of rate limit quality is crucial for building effective agent architectures.