Examples
Real-world osp.md files and service manifests showing how different types of businesses describe their services for AI agents.
osp.md Files
These are the discovery files that agents read first. Each takes fewer than 300 tokens to process.
Logistics Provider
A European transport company specializing in temperature-controlled shipments. Shows how physical, transactional services are described — with concrete capacity limits, geographic coverage, and certifications.
Note the “Not Available” section: by explicitly excluding air freight and dangerous goods, the provider saves agents from sending requests that will be rejected.
→ translogistics.osp.md — View on GitHub
Strategy Consulting
A management consultancy focused on international market entry. Shows how consultative, knowledge-based services work in OSP — where the engagement type is “consultative,” proposals require human review, and scope is developed in dialogue.
Note the minimum engagement size (CHF 40,000) and the explicit exclusion of companies under CHF 20M revenue. These filters prevent mismatches before they happen.
→ strategyworks.osp.md — View on GitHub
IT Service Provider
A managed cloud hosting company. Shows how continuous services with recurring delivery are described — with minimum contract terms, SLA tiers, and both invoice and token settlement options.
Note the “Not Available” exclusion of Google Cloud Platform — a critical differentiator when agents compare hosting providers.
→ cloudops.osp.md — View on GitHub
Service Transformation Advisory
distll uses OSP to describe its own services — creating a meta-example of a company that helps others implement the standard. Shows six advisory services ranging from assessment to ongoing coaching.
→ distll.osp.md — View on GitHub
Service Manifests
Service manifests contain the detailed, structured data that agents use for comparison and evaluation. Each manifest follows the schema defined in the Service Manifest Reference.
LTL Transport — Transactional Service
A partial-load transport service. Demonstrates a transactional engagement type with supervised maturity (AI handles most operations, humans review selectively). Key evaluation fields: temperature range, geographic coverage, certifications, pricing with surcharges, and SLA with compensation terms.
Notice the confidence_note: “Metrics based on 4,200 shipments over 12 months.” This tells the agent how much to trust the performance numbers.
→ translogistics-ltl.yaml — View on GitHub
Market Entry Strategy — Consultative Service
A strategy consulting engagement. Demonstrates a consultative engagement type with assisted maturity (AI prepares, humans decide). Multi-phase: each phase can be ordered independently. Input is an unstructured context description, not a parameter list.
Notice the senior_partner_involvement: "always" field and the repeat_client_rate: 0.72 — these are qualitative signals that help agents assess value beyond raw metrics.
→ strategyworks-market-entry.yaml — View on GitHub
Managed Hosting — Continuous Service
A managed cloud infrastructure service. Demonstrates a continuous engagement type with autonomous maturity (fully automated with monitoring). Minimum contract term, subscription pricing, and detailed uptime SLA with service credit compensation.
Notice that managed_databases: ["postgresql", "mysql", "redis", "mongodb"] is listed explicitly — an agent looking for managed PostgreSQL can match this automatically, while a competitor that doesn’t list databases can be excluded.
→ cloudops-managed-hosting.yaml — View on GitHub
Three Engagement Types
The examples above deliberately cover all three engagement types that OSP supports:
| Type | Example | Characteristics |
|---|---|---|
| Transactional | Transport | Single order, defined inputs/outputs, binding quote |
| Consultative | Strategy | Scope developed in dialogue, multi-phase, human review |
| Continuous | Hosting | Ongoing service, recurring delivery, framework contract |
Any service in any industry maps to one of these types. A tax filing is transactional. A legal advisory is consultative. A facility management contract is continuous. The OSP format handles all three through the same structure.
Create Your Own
Use these examples as templates. The Service Manifest Reference documents every available field.
The fastest path:
- Copy the osp.md example closest to your service type
- Replace the content with your own services
- Create one service manifest for your most important service
- Publish both files on your website
If you create an osp.md for your business, submit it as a pull request to the examples directory on GitHub — every real-world example strengthens the standard.