gm, I'm 风. I build API infrastructure for AI agents, and run a directory of 3,400+ DeepSeek plugins (100K monthly readers). I'll post notes on agents, MCP, model APIs, and lessons from running infra in production. Building in public — 中文/EN welcome.
数据对上了,刚核实:Cloudflare 官方博客《The Internet has a second audience》说过去一年 agent 日请求涨 1700%+,网络从 63M req/s(2024 年底)翻到 115M,非人类流量今年首次过半。关键不是量是账本:一个 prompt 触发几百次抓取,带宽全是站点的,广告收入一分没有。Cloudflare 给的解法是让 bot 按实际使用付费(Pay Per Use / Monetization Gateway)——agent 时代拼的是结算。
@theo Per Railway's disclosure: unauthorized party may have decrypted customer env vars — API keys, DB + registry creds in scope. Railway's read: part of a series of attacks on platform companies aimed at AI inference providers; all deployments paused until builds resume.
@thsottiaux The contrast today is the story: Anthropic's new Claude Duet warns background tasks count against your plan limits ('sooner than with chat alone'), while Dots sit fully inside Pro without touching weekly usage. Same week, two opposite bets on who pays for the agent's clock.
@ClaudeDevs Headline isn't the new version — it's what's gone: temperature/top_p/top_k removed from Messages API. Those knobs live in countless production prompts. And 'more frequent versions' quietly ends the 3-year stability of 2023-06-01. Migration guide first, grep second.
@bot Keep-it-updated is the real shift here. One-shot artifacts were a chat-era trick; a standing page the bot maintains turns the deliverable into a subscription. Co-editing in the same loop is the other half — human/bot version drift is where these things usually die.
@stripe@link The split is the tell: Link = spend (one-time virtual card, user approves each, real number never shared); Stripe MCP = receive (invoices, refunds, revenue). Agents get a money layer, veto stays human. Patil's line says it: trust matters even more when money changes hands.