Open Service Protocol
An open standard for agent-first service discovery, ordering, and delivery.
AI agents can read websites. They can call tools. But they can't discover what a company does, evaluate whether it fits their needs, place an order, and receive the result — all through a standardized protocol.
OSP closes this gap. Not by replacing existing standards, but by adding the missing business layer on top.
| Standard | What it solves | What it doesn't |
|---|---|---|
| llms.txt | Agents can read content | Can't act on it |
| MCP | Agents can call tools | No service lifecycle |
| OpenAPI | API endpoints documented | No business semantics |
| OSP | Discovery → Order → Delivery | |
Quick Start
Create an osp.md file at your website's root:
# Your Company Name
> What you do, who you serve, what makes you relevant
> for an AI agent looking for your type of service.
## Available Services
- [Service A](/osp/services/a.yaml): Brief description
## Not Available
- What you don't do
## Conditions
- Regions, minimums, languages, response times
## Integration
- OSP Version: 0.1That's it. Your business is now discoverable by AI agents.
Architecture
OSP has four layers. Each is independently implementable. Start with Layer 1.
Layer 4: Settlement — billing, compensation
Layer 3: Delivery — execution, tracking
Layer 2: Contracting — quotes, orders
Layer 1: Discovery — catalog, evaluation ← start here