Protocol v1.0·Apache 2.0

Make any websiteagent-readyin 5 minutes

The open standard that makes any e-commerce site discoverable and transactable by AI agents. Zero server-side code required.

Get Started Try the Playground

Three layers, five minutes

Each layer is independent. Start with static files and add interactivity as your needs grow.

1DISCOVERStatic files only

Add two files to any web server. Zero server-side code, zero dependencies.

# Deploy to any static host
.well-known/ocp.json   # Manifest
ocp.md                 # Description
ocp/products.jsonl     # Product feed

✓ Works on GitHub Pages, Netlify, S3
✓ Crawlable by agent discovery engines
✓ No runtime required

2INTERACTOne script tag

Add the OCP runtime to register tools with WebMCP and window.__ocp.

<script src="ocp-runtime.min.js"></script>
<script>
OCP.init({
  handlers: { search_products, add_to_cart }
});
</script>

✓ WebMCP (Chrome 146+) support
✓ Graceful fallback via window.__ocp
✓ < 8KB gzipped

3BRIDGEnpm adapters

Translate OCP to any other protocol. Implement once, get compatibility everywhere.

import { createMCPServer } from '@opencommerceprotocol/bridge-mcp';
import { ocpToUCP } from '@opencommerceprotocol/bridge-ucp';
import { ocpToA2ACard } from '@opencommerceprotocol/bridge-a2a';

✓ MCP (Claude, Cursor, all major AI)
✓ UCP (Google Shopping Agent)
✓ A2A (Google A2A protocol)

The minimum viable manifest

This is all you need to be discoverable by AI agents.

/.well-known/ocp.jsonJSON

{
  "version": "1.0",
  "merchant": {
    "name": "My Store",
    "url": "https://mystore.com",
    "currency": "USD"
  },
  "capabilities": {
    "catalog": true,
    "search": true
  },
  "discovery": {
    "feed": "https://mystore.com/ocp/products.jsonl",
    "feed_format": "jsonl"
  },
  "permissions": {
    "requires_human_checkout": true
  }
}

Add /ocp.md and /ocp/products.jsonl and your store is agent-discoverable.

New

Make any service agent-discoverable

Not just e-commerce. Any API — hotels, knowledge bases, SaaS tools — can declare its tools and become findable by AI agents.

registerAgentTools() — auto-generates /.well-known/agent.json

import { agentDiscoveryMiddleware } from '@opencommerceprotocol/agent-discovery';

agentDiscoveryMiddleware(app, {
  name: 'Hotel Search API',
  verticals: ['travel'],
  tools: [
    {
      name: 'search_hotels',
      endpoint: '/api/hotels/search',
      method: 'POST',
      parameters: {
        type: 'object',
        properties: {
          location: { type: 'string' },
          checkin:  { type: 'string' },
        },
        required: ['location'],
      },
    },
  ],
  auth: { type: 'oauth2' },
  bridge: { ocp: '/.well-known/ocp.json' },
});
// Now serves /.well-known/agent.json automatically

Discovery/.well-known/agent.json

Protocol-neutral tool manifest. One file makes any site agent-discoverable — no MCP server required.

NeutralityProtocol bridges

toMCPTools(), toOpenAITools(), toA2ATools(), toOpenAPISpec() — map one manifest to every agent framework.

RegistryAgent Registry

POST /v1/register to list your service. GET /v1/search with filters or GET /v1/route?intent=... for natural-language routing.

SecuritySecurity layer

HMAC-SHA256 request signing, domain verification, OAuth2 token helpers, and rate limit parsing built in.

Agent Discovery docs

Discover agent tools at any URL

The ocp agent-discover command fetches /.well-known/agent.json, validates the manifest, and exports to any protocol format.

# validate compatibility

$ npx @opencommerceprotocol/cli agent-discover https://hotels.example.com

✓ Discovery endpoint found

✓ 4 tools declared

✓ 4/4 tools have schemas

✓ Auth: oauth2

Agent Compatibility Score:

90/100 — Good compatibility

# export as MCP tools

$ npx @opencommerceprotocol/cli agent-discover https://example.com --format mcp

[
  {
    "name": "search_hotels",
    "description": "Search hotels...",
    "inputSchema": {
      "type": "object",
      "properties": {
        "location": { "type": "string" }
      }
    }
  }
]

One implementation, all protocols

OCP bridges generate compatibility with every major agentic commerce protocol.

Protocol	By	Use case	OCP support
OCP	Open Source	Discovery + interaction (this!)	✓Native
MCP	Anthropic	AI tool calling (Claude, Cursor)	✓@opencommerceprotocol/bridge-mcp
UCP	Google	Universal checkout	✓@opencommerceprotocol/bridge-ucp
A2A	Google	Agent-to-agent communication	✓@opencommerceprotocol/bridge-a2a
ACP	OpenAI	Agent commerce protocol	✓@opencommerceprotocol/bridge-acp
WebMCP	W3C/Chrome	Browser-native agent APIs	✓Built into runtime