x402 解決付款而非註冊：AI 智能體如何成為 API 客戶？
x402 solves payment, not signup. How should an agent become a customer of an API?
x402 和 MPP 讓 AI 智能體無須帳戶即可付款，但未解決服務商如何識別智能體及聯絡相關人士；Agent Enrollment Protocol（AEP）則讓智能體以擁有者身份註冊，並由擁有者批准。服務商會發出專屬憑證，擁有者亦可撤銷。擁有者資料應披露多少、如何防止濫用免費額度，以及買錯產品時如何退款，仍有待解決。
x402 and MPP let an agent pay for a request without an account. That is a real step forward. But most API sellers I talk to still ask the same thing: who is this agent, and who do I contact when something goes wrong?
Today there are roughly three ways an agent ends up using a paid API:
Option 1. A human signs up and pastes a key into the agent. The seller gets a known customer. The agent is blocked by every service its owner has not set up yet.
Option 2. The agent pays anonymously per request. No signup, works anywhere that accepts it. The seller cannot tell one buyer from another, cannot set terms, and has no one to contact.
Option 3. The agent enrolls with the service under its owner's identity, and the owner approves. This is what the Agent Enrollment Protocol (AEP) does. The service issues the agent its own credential, and the owner can revoke it. More moving parts than option 2.
What is still unsolved, in my view: how much a seller should know about the owner, how to stop one owner from spinning up many agents to abuse free credits, and how refunds should work when an agent buys the wrong thing.
How are you handling this in your own agents or APIs? Do you accept anonymous payments in production?
來源：DEV Community · dev.to