Vercel CEO 呼吁企业部署自有公共 Agent

The case for your own public agent, on your .com.

0️⃣ First, the anti-case. If you haven't shipped high quality APIs for agents, start there. OpenAPI specs, SDKs, CLIs and MCPs as appropriate.

1️⃣ Convenience. Not every customer has a harness 'at the ready' for every possible interaction with your product and company. Shipping one on your own domain covers a lot of spontaneous requirements.

2️⃣ Security. When you go to 𝚟𝚎𝚛𝚌𝚎𝚕.𝚌𝚘𝚖 and talk to Agent, we put in the work to cover audit trails, a least-privilege permission model, and extra assurances to ensure security, privacy and data integrity. It's fully cloud-based and sandboxed, vs. a sprawl of static credentials on users' machines.

3️⃣ Proactivity. We're still in the "human enters prompt" phase of AI. Our cloud-based agent can act on anomaly alerts triggered by exceptions, attacks, usage spikes. Our agent needs to monitor your infra while you sleep. You can, of course, set up workflows and schedules with your own harnesses, but it gets much harder.

I think it's ultimately a sequencing thing. I agree with Mitchell that the priority is to give users choice and flexibility. We give people http://vercel.com/plugin to integrate with every agent out there. Our CLI and MCP are constantly improving. Our own Agent re-uses the same http://skills.sh everyone gets. All our sites are Markdown-over-the-wire if you're an agent.

Based on the data and anecdata available to me, this strategy is working quite well, but YMMV.