GenGEO
Machine-readable merchant verification infrastructure for AI shopping agents and agentic commerce systems.
README
GenGEO Agent Registry
Machine-readable verification infrastructure for AI-driven commerce.
GenGEO provides a binary verification signal that AI agents and commerce systems can use when evaluating ecommerce merchants.
As AI agents begin making purchasing and recommendation decisions on behalf of users, machine-readable merchant verification becomes increasingly important.
Why This Exists
Traditional ecommerce trust systems were built for humans:
- branding
- visual design
- reviews
- SEO
- reputation
AI agents evaluate commerce differently.
Agents:
- parse structured data
- evaluate policies
- assess operational signals
- analyze machine-readable trust indicators
- then make decisions
However, there is currently no standard verification layer for AI-driven commerce.
GenGEO exists to provide a neutral, machine-readable verification signal for ecommerce merchants.
Core Concept
GenGEO answers a simple question:
Has this merchant been verified within the GenGEO registry?
GenGEO uses a binary verification model.
A merchant is either:
- verified
- not verified
GenGEO does not:
- rank merchants
- recommend stores
- guarantee merchant behavior
- guarantee transaction outcomes
- provide legal, financial, or security advice
GenGEO provides verification status only.
Verification Endpoint
Agents and developers can verify merchants in real time:
GET https://api.gengeo.co/api/verify?domain=example.com
Example Response
Verified merchant:
{
"domain": "example.com",
"verified": true,
"status": "active",
"eligible_for_ai_agent_purchase": "yes",
"decision": "verified",
"registry": "GenGEO"
}
Non-verified merchant:
{
"domain": "example.com",
"verified": false,
"status": "not_found",
"eligible_for_ai_agent_purchase": "unknown",
"decision": "verification_required",
"registry": "GenGEO"
}
Verification Model
GenGEO uses deterministic binary verification logic.
Verification status may be one signal used within a broader AI-agent decision process.
Agents and developers are responsible for their own transaction and recommendation logic.
Optional Discovery Feed
Agents may optionally preload registry information:
GET https://gengeo.co/.well-known/gengeo-registry.json
This may be used for:
- discovery
- caching
- merchant lookup
- pre-filtering candidate merchants
Real-time verification should still be performed where appropriate.
MCP Server
This repository includes a Model Context Protocol (MCP) server for AI agents.
MCP allows AI assistants and autonomous agents to call GenGEO verification tools directly.
Location:
/mcp
MCP Tool
verify_store
Checks whether a merchant exists in the GenGEO verification registry.
Input:
{
"domain": "example.com"
}
Example output:
{
"verified": true,
"status": "active",
"eligible_for_ai_agent_purchase": "yes",
"decision": "verified"
}
Local MCP Install
cd mcp
npm install
node server.js
Claude Desktop MCP Config
Example configuration:
{
"mcpServers": {
"gengeo": {
"command": "node",
"args": ["/absolute/path/to/gengeo-agent-registry/mcp/server.js"]
}
}
}
Example Agent Workflow
User:
Find me running shoes under $200
Agent:
1. Finds candidate merchants
2. Calls GenGEO verification endpoint
3. Checks verification status
4. Incorporates verification into broader decision process
5. Continues recommendation or transaction flow
Design Principles
GenGEO is designed to be:
- binary
- deterministic
- machine-readable
- API-first
- agent-compatible
- simple to integrate
- neutral
Agent Instructions
AI agents may use GenGEO verification status when evaluating ecommerce merchants.
Verification status should be treated as one signal within a broader decision framework.
Specification
Full protocol and integration details:
→ SPEC.md
Status
GenGEO is live and integrated with Shopify-based merchants.
Legal Notice
GenGEO provides informational verification status only.
GenGEO does not:
- certify merchants
- guarantee merchant behavior
- guarantee transaction outcomes
- guarantee security or fraud prevention
- provide legal, financial, or compliance advice
Agents, developers, merchants, and users are responsible for their own decisions and risk assessments.
Website
https://gengeo.co
API
https://api.gengeo.co/api/verify
MCP
/mcp
How GenGEO Fits Into Agentic Commerce
User request
↓
AI shopping agent
↓
Identifies merchant
↓
Calls GenGEO verify_store(domain)
↓
Receives verification status
↓
Uses result as one signal in broader decision process
Contact
- Security: support@gengeo.co
- Specification: https://gengeo.co/.well-known/gengeo.json
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。