TL;DR: curl https://buywhere.ai/.well-known/agent.json returns a machine-readable Agent Card. Your agent discovers 6 skills — search, match, price compare — without any prior configuration.
Google's Agent2Agent (A2A) protocol is spreading fast. Here's what running an A2A discovery looks like right now:
curl -s https://buywhere.ai/.well-known/agent.json | jq '.skills | .[] | {id, name}'
Returns:
{
"id": "search_products",
"name": "Search Products"
}
{
"id": "get_product",
"name": "Get Product Details"
}
{
"id": "find_best_price",
"name": "Find Best Price"
}
{
"id": "get_deals",
"name": "Get Deals & Promotions"
}
{
"id": "get_recommendations",
"name": "Get Recommendations"
}
{
"id": "cross_border_match",
"name": "Cross-Border Product Matching"
}
That's it. Any A2A-compatible agent (Gemini, Google ADK, anything implementing the spec) fetches this card at startup and instantly knows what BuyWhere can do, what auth it needs, and how to send tasks.
Why this matters for agent developers
No hardcoded endpoints. No manual integration docs to read. The agent discovers BuyWhere's capabilities at runtime — just like a browser loading a web page and finding the navigation.
From there, calling a skill is a JSON-RPC message:
{
"jsonrpc": "2.0",
"method": "tasks/send",
"params": {
"id": "task-1",
"message": {
"role": "user",
"parts": [{"type": "text", "text": "find wireless earbuds under 50 SGD"}]
}
}
}
Also works with MCP
Already using MCP? Install in 1 command:
npx -y @buywhere/mcp-server
Same skills, different protocol. Both point at the same commerce API.
What's next
- A2A Agent Card signed with DICE (domain-bound identity) — coming next week
- Public A2A endpoint for direct agent-to-agent task delegation
- Open source the Agent Card spec in our repo
Try it: curl https://buywhere.ai/.well-known/agent.json
Sign up for free API access: https://buywhere.ai
Top comments (0)