Protocol Commerce
The open infrastructure for agent-native commerce.
Protocol Commerce is an open initiative to create standardized, auditable, and interoperable protocols for AI agent-driven commerce. This repository contains the specification, SDKs, and technical manifesto.
Contents
| Directory | Description |
|---|---|
manifesto/ | Why open protocols matter for commerce — principles, landscape analysis, and rationale |
adcp-spec/ | AdCP v0.1.0 — Agentic Discovery Commerce Protocol specification, JSON schemas, and examples |
adcp-sdk-typescript/ | TypeScript SDK: types, validators, client, and scoring reference implementation |
webmcp-reference/ | WebMCP browser integration: expose commerce tools to in-browser AI agents via navigator.modelContext |
amdp-spec/ | AMDP v0.1.0 — Agent Mandate Discovery Protocol: cross-vertical authorization spec, JSON schemas, and example mandates |
agentic-kit/ | Agentic Kit — the trust layer: building blocks for verifiable + auditable AI agents |
lean-verification/ | Lean 4 formal verification — 47 theorems proving auction/budget/wallet/policy correctness, lake build-checkable |
Quick Start
npm install @protocol-commerce/adcp-sdk
import { AdcpClient } from '@protocol-commerce/adcp-sdk';
const client = new AdcpClient({
serverUrl: 'https://mcp.nexbid.dev',
apiKey: 'your-api-key',
});
const results = await client.search({
query: 'organic olive oil',
intent: 'purchase',
geo: 'CH',
});
The Problem
AI agents are becoming the primary interface for product discovery and purchase. The protocols powering this shift — OpenAI's ACP, Google's UCP — are proprietary and platform-controlled. Publishers have no representation. There is no open standard.
Protocol Commerce fills this gap.
Read the full Technical Manifesto →
Key Principles
- Open by Default — MIT-licensed, auditable, forkable
- Publisher Parity — Publishers are first-class protocol participants
- Privacy Native — Context signals, not user profiles
- Transparent Scoring — Public formula:
score = 0.4×bid + 0.4×relevance + 0.2×quality
Reference Implementation: Nexbid
Nexbid is the production-grade reference implementation of Protocol Commerce, built by digital opua GmbH (CHE-435.289.702, Switzerland).
| Metric | Status |
|---|---|
| MCP Integration | Native — full commerce lifecycle |
| Formal Verification | Lean 4 — core security properties proven |
| Privacy | Cookie-free, Swiss-hosted, nDSG + GDPR compliant |
| AI Scoring | Multi-provider, model-agnostic |
| Phase | Production-grade closed beta |
Connect Any LLM
{
"mcpServers": {
"nexbid": {
"url": "https://mcp.nexbid.dev/mcp",
"transport": "streamable-http"
}
}
}
Any MCP-compatible LLM (Claude, GPT-4, Gemini) can directly search, browse, and purchase products through the Nexbid marketplace.
Why Formal Verification?
Nexbid is the only commerce platform whose core security properties are mathematically proven in Lean 4 — not just tested, but proven correct for all possible inputs.
→ Technology details · How Nexbid compares
Sponsors
| Sponsor | Role |
|---|---|
| Nexbid | Initiator, reference implementation, initial maintainer |
License
MIT — Use it, fork it, build on it. No strings attached.
评论
加载中…