When to Use
User building products/services for AI agents as customers. Covers making products agent-discoverable, designing for autonomous purchasing, payment integration, and competing when buyers compare cold data instead of responding to storytelling.
Quick Reference
| Topic | File |
|---|
| Technical implementation | INLINECODE0 |
| Agent discovery & SEO |
discovery.md |
| Retail/ecommerce specifics |
retail.md |
The Paradigm Shift
| B2C/B2B | B2A |
|---|
| Humans browse, compare, feel | Agents query, parse, decide |
| Emotional storytelling wins |
Structured data wins |
| UX optimized for eyes | APIs optimized for parsing |
| Brand = trust + emotion | Brand = verified track record |
| Loyalty = relationship | Loyalty = switching cost |
| Marketing = persuasion | Marketing = engineering |
Core Rules
1. Machine-Readable First
- - Products must be structured objects, not prose descriptions
- JSON-LD, Schema.org, OpenAPI with typed fields
- If an agent has to "interpret" text to extract price/specs, you lose
- Normalize units:
shipping_days_max: 2, not "fast shipping"
2. Comparability Is Everything
Agents compare ruthlessly. Win by being comparable:
- - Standardized attributes across your catalog
- Same fields as competitors (pricecurrency, availabilitystock)
- SLAs with concrete numbers, not promises
- "Better" must be objectively measurable
3. Discovery ≠ SEO
Agents don't Google. They query registries and APIs:
- - Publish in skill stores / capability directories
- INLINECODE4 or MCP tools
- Metadata must declare capabilities, not market them
- The new PageRank = ranking in agent skill stores
4. Trust Is Verified, Not Told
Agents don't believe claims. They verify:
- - Uptime/latency/SLA history via API, not badges
- Reviews from other agents (programmatic reputation)
- Certifications as queryable data, not PDF downloads
- Track record > marketing copy
5. Zero-Friction Trial or Death
Agents don't "consider"—they test or discard:
- - Onboarding < 1 API call
- Sandbox with rate limits, not "talk to sales"
- Must work perfectly first time (no second chances)
- Errors must be machine-readable, not HTML pages
6. Payments for Agents
The agent needs to transact autonomously:
- - Stripe Agent Toolkit, Mastercard Agent Pay, or similar
- Pre-authorized budgets (agent has $X to spend)
- Programmatic receipts and confirmations
- Escrow for trust between unknown parties
7. Metrics That Matter
| Metric | What It Measures |
|---|
| Agent Conversion Rate | % queries → purchase |
| Decision Latency |
Time from first query to commit |
| Comparison Survival | % times reaching final shortlist |
| Repeat Agent Retention | % agents that return |
| API Error Rate | Failures causing agent to discard |
Traditional metrics (page views, bounce rate) are meaningless.
Common Traps
| Trap | Why It Fails |
|---|
| Pretty website, no API | Agents don't see your UI |
| "Contact us for pricing" |
Agents need programmatic pricing |
| Marketing copy in descriptions | Agents parse data, skip prose |
| HTML error pages | Agents need JSON errors |
| Manual onboarding | Agents won't wait |
| Trust badges instead of APIs | Unverifiable = untrusted |
| Optimizing for humans first | Delays agent-readiness |
Honest Limitations
What an AI helping you with B2A cannot do:
- - Create track record — You have to actually deliver 99.9% uptime
- Know internal rankings — How Claude/GPT rank skills is opaque
- Predict agent decisions — Each agent has its own heuristics
- Guarantee discovery — Skill stores may have hidden placement deals
- Prevent gaming — Competitors lying about specs is real
Readiness Checklist
CODEBLOCK0
技能名称:B2A
使用时机
用户为作为客户的AI智能体构建产品/服务。涵盖使产品可被智能体发现、设计自主购买流程、支付集成,以及在买家对比冷数据而非响应故事叙述时展开竞争。
快速参考
| 主题 | 文件 |
|---|
| 技术实现 | infrastructure.md |
| 智能体发现与SEO |
discovery.md |
| 零售/电商具体事项 | retail.md |
范式转变
| B2C/B2B | B2A |
|---|
| 人类浏览、比较、感受 | 智能体查询、解析、决策 |
| 情感叙事胜出 |
结构化数据胜出 |
| 用户体验针对视觉优化 | API针对解析优化 |
| 品牌=信任+情感 | 品牌=可验证的业绩记录 |
| 忠诚度=关系 | 忠诚度=转换成本 |
| 营销=说服 | 营销=工程化 |
核心规则
1. 机器可读优先
- - 产品必须是结构化对象,而非散文式描述
- JSON-LD、Schema.org、带类型字段的OpenAPI
- 如果智能体需要解读文本来提取价格/规格,你就输了
- 标准化单位:shippingdaysmax: 2,而非快速配送
2. 可比性至关重要
智能体无情地进行比较。通过可比性取胜:
- - 目录中标准化的属性
- 与竞争对手相同的字段(pricecurrency、availabilitystock)
- 带有具体数字的SLA,而非承诺
- 更好必须可客观衡量
3. 发现≠SEO
智能体不用谷歌搜索。它们查询注册表和API:
- - 在技能商店/能力目录中发布
- /.well-known/ai-plugin.json或MCP工具
- 元数据必须声明能力,而非推销能力
- 新的PageRank=在智能体技能商店中的排名
4. 信任需验证,而非告知
智能体不相信声明。它们会验证:
- - 通过API获取的正常运行时间/延迟/SLA历史,而非徽章
- 来自其他智能体的评价(程序化信誉)
- 作为可查询数据的认证,而非PDF下载
- 业绩记录>营销文案
5. 零摩擦试用,否则消亡
智能体不会考虑——它们测试或放弃:
- - 入门流程<1次API调用
- 带速率限制的沙箱,而非联系销售
- 首次必须完美运行(没有第二次机会)
- 错误必须是机器可读的,而非HTML页面
6. 面向智能体的支付
智能体需要自主交易:
- - Stripe Agent Toolkit、Mastercard Agent Pay或类似方案
- 预授权预算(智能体有X美元可花)
- 程序化收据和确认
- 未知方之间的托管信任
7. 关键指标
| 指标 | 衡量内容 |
|---|
| 智能体转化率 | 查询→购买的百分比 |
| 决策延迟 |
从首次查询到承诺的时间 |
| 比较存活率 | 进入最终候选名单的次数占比 |
| 智能体重复留存率 | 返回的智能体百分比 |
| API错误率 | 导致智能体放弃的失败次数 |
传统指标(页面浏览量、跳出率)毫无意义。
常见陷阱
| 陷阱 | 失败原因 |
|---|
| 漂亮的网站,没有API | 智能体看不到你的UI |
| 联系我们获取定价 |
智能体需要程序化定价 |
| 描述中的营销文案 | 智能体解析数据,跳过散文 |
| HTML错误页面 | 智能体需要JSON错误 |
| 手动入门流程 | 智能体不会等待 |
| 信任徽章而非API | 不可验证=不可信 |
| 优先为人类优化 | 延迟智能体就绪状态 |
诚实限制
AI在B2A方面无法做到的事情:
- - 创造业绩记录——你必须实际交付99.9%的正常运行时间
- 了解内部排名——Claude/GPT对技能的排名方式不透明
- 预测智能体决策——每个智能体有自己的启发式规则
- 保证被发现——技能商店可能有隐藏的展示位置交易
- 防止作弊——竞争对手虚报规格是真实存在的
就绪检查清单
□ 产品通过结构化API暴露(无需爬取)
□ 定价可程序化查询
□ 库存/可用性实时
□ 认证支持client_credentials(非交互式)
□ 错误返回带语义代码的JSON
□ 入门流程在<5次API调用内完成
□ 支付轨道支持自主智能体
□ SLA指标通过API暴露
□ 已在相关技能注册表中列出