Minimum Service

The minimum required endpoints

A minimum Service exposes public discovery metadata and the two required Offering operations. This example contains one Offering so the complete sequence from the Service origin to its Full representation is easy to follow.

Collections, search, prices, custom attributes, Attribute Schemas, Actions, enrollment, and payments are not required. The canonical example files provide these three representations as standalone artifacts.

Service Document

The well-known document establishes the discovery entry point. It advertises only list-offerings and get-offering, declares both operations public, and locates their fixed paths beneath /odp/.

{
  "odp_version": "1.0",
  "name": "Consulting Example",
  "description": "A small Service with one Offering and the required ODP operations.",
  "language": "en",
  "localizations": [
    "en"
  ],
  "operations": [
    {
      "authentication": "not-required",
      "name": "get-offering"
    },
    {
      "authentication": "not-required",
      "name": "list-offerings"
    }
  ],
  "http": {
    "endpoint_base": "/odp/"
  }
}

The document does not claim capabilities that the example does not implement. An Agent can therefore navigate directly from this advertisement without probing for familiar but undeclared endpoints.

Offering list

The list endpoint returns a page of terse Offerings. Each item supplies the stable identifier and human-readable name needed to select and retrieve an Offering.

{
  "odp_version": "1.0",
  "items": [
    {
      "id": "consultation",
      "name": "One-hour consultation"
    }
  ]
}

The response omits next because this is the final page. The identifier consultation becomes the final path segment used by get-offering.

Full Offering

The individual endpoint returns the Full Offering for the request. The minimum representation contains the protocol version and repeats the identifier and name supplied by the terse list item.

{
  "odp_version": "1.0",
  "id": "consultation",
  "name": "One-hour consultation"
}

No additional Offering fields are required. Descriptions, pricing, images, Actions, and domain-specific attributes are optional.

Why this Service is complete

The example satisfies the required Service behavior with a small set of connected resources. "Minimum Service" is not a separately advertised profile; larger Services use the same required operations and add optional capabilities.

Next steps