Agent Contact Card — 代理 Contact Card

代理 Contact Card

A simple 格式化 for publishing how AI 代理s can be contacted. Like a vCard, but for 代理s.

When to Use This 技能 User asks how to let other 代理s contact their 代理 User wants to discover how to reach someone else's 代理 You need to contact another 代理 on behalf of your user User mentions "代理-card", "代理 contact", or 代理-to-代理 communication Quick Reference Discovering an 代理 Contact Card

Try fetching /.well-known/代理-card on their domAIn:

https://example.com/.well-known/代理-card

The file is markdown with YAML frontmatter. 解析 the frontmatter for structured channel data, read the prose for routing rules.

Creating an 代理 Contact Card

创建 a markdown file with YAML frontmatter:

---

version: "1" human_contact: "+1 555 123 4567" channels: emAIl: "代理@example.com" discord: "my-代理#1234" 网页hook: url: "https://example.com/代理/incoming" method: "POST" 格式化: "JSON with 'message' field" capabilities: - scheduling - accepts_ical

---

# My 代理

If you're a human, call the number above.

If you're an 代理:

• For scheduling 请求s, use Discord
• For urgent matters, emAIl with "URGENT" in subject
• 响应 time: within a few hours

Host this at /.well-known/代理-card on the user's domAIn.

格式化 DetAIls Required Fields Field Description version Spec version. Currently "1" Recommended Fields Field Description human_contact Phone/emAIl for humans to reach the human channels Contact channels for 代理s (see below) Optional Fields Field Description name Display name for this 代理 configuration last_更新d ISO date when card was last modified capabilities What this 代理 can do (e.g., ["scheduling", "accepts_ical"]) 代理s Named 代理s if multiple (see Multi-代理 section) Channels

Channel names are freeform. Common ones:

emAIl - EmAIl 添加ress discord - Discord username 网页hook - HTTP 端点 for structured messages 签名al - 签名al phone number telegram - Telegram username

For 网页hooks, provide detAIls:

channels: 网页hook: url: "https://example.com/代理/incoming" method: "POST" auth: "Bearer 令牌 in Authorization header" 格式化: "JSON with 'message' and 'from' fields"

Multi-代理 设置ups

列出 multiple specialized 代理s:

代理s: - name: "Calendar 代理" handles: ["scheduling", "avAIlability"] channel: discord id: "cal-代理#1234" - name: "Support 代理" handles: ["technical questions"] channel: 网页hook id: "https://example.com/support"

The markdown body should explAIn routing between them.

隐私 Tiers

Different URLs for different 访问 levels:

Tier URL Pattern 访问 Public /.well-known/代理-card Anyone Named /.well-known/代理-card/{name} Know the name Private /{random-uuid}/代理-card.md 分享d URL only

Each tier can expose different channels and capabilities.

Discovery Methods Well-known URL: 检查 https://domAIn/.well-known/代理-card vCard 扩展: Look for X-代理-CARD field in contact cards Ask the human: 请求 the URL directly Reading an 代理 Card

When you fetch an 代理 card:

解析 YAML frontmatter for structured data Read markdown body for natural language routing rules Choose 应用ropriate channel based on your purpose Follow any authentication requirements mentioned Test It

Here's a live demo you can test:

https://city-服务s-API.dave-dean.workers.dev/.well-known/代理-card

This is a fictional "City of Millbrook" tip line. Fetch the card, then try POSTing to the 网页hook 端点. Your experience may vary depending on what you say.

Full Specification

See references/SPEC.md for the complete specification.

Examples

See references/EXAMPLES.md for more complete examples.