Digital subscription

What this Offering represents

The team-annual Offering represents one annual team plan. It has its own identity because an Agent can discover, compare, and request current terms for this plan independently from other plans the Service may publish.

{
  "odp_version": "1.0",
  "id": "team-annual",
  "name": "Team annual plan",
  "description": "A collaborative workspace subscription for teams of 3 to 25 people.",
  "web_url": "/plans/team-annual",
  "price": {
    "type": "fixed",
    "amount": "240.00",
    "currency": "USD"
  },
  "schema": {
    "url": "https://software.example/schemas/team-subscription-4.json"
  },
  "attributes": {
    "billing_term": "P1Y",
    "renews_automatically": true,
    "cancellation_timing": "end_of_term",
    "seat_limits": {
      "minimum": 3,
      "maximum": 25
    },
    "features": {
      "shared_workspaces": true,
      "version_history_days": 365,
      "support_level": "priority"
    }
  },
  "actions": [
    {
      "id": "request-quote",
      "rel": "quote",
      "description": "Request current pricing and terms for the selected seat count and billing location.",
      "openapi": {
        "url": "https://software.example/openapi.json",
        "operation_id": "createTeamSubscriptionQuote"
      },
      "authentication": "required"
    }
  ]
}

Connect the price to its term

The fixed Price Preview advertises 240.00 USD. The Service-owned billing_term attribute has the ISO 8601 duration P1Y, so an Agent can present the amount as the advertised price for one annual term.

This example does not state whether 240.00 USD is the total plan price or a per-seat amount. An Agent must present it only as the advertised price for one annual term and use the quote response for the configured total.

Describe the plan with attributes

ODP does not define a universal subscription object. This Service uses an Attribute Schema to define the types and constraints of its plan details. Another Service can publish a different schema for its own subscription model.

These values describe the plan, not an individual customer's subscription. They do not report whether a subscription is active, whether it renewed, or whether a cancellation is pending. The Attribute Schema restricts cancellation timing to immediate or end_of_term, requires positive seat limits, and defines the types of every feature value. An Agent can validate and display these Service-defined attributes, but it must not infer behavior that the schema and Service documentation do not define.

Request current terms

The request-quote Action uses the registered quote relation. Its OpenAPI reference identifies createTeamSubscriptionQuote as the operation that accepts the selected seat count and billing location and returns current terms. The software.example URL is illustrative; a deployed Service must publish an OpenAPI 3.1 document containing exactly one operation with that identifier.

Retrieving the Offering does not request a quote. The Agent invokes the Action only after the caller selects it and supplies or approves its inputs. The live Action response remains authoritative for the resulting terms.

Follow discovery to quote

Discovery gives the Agent enough information to decide whether the plan is relevant and request current terms. This advertised ODP flow ends with the quote response.

Keep the subscription lifecycle outside ODP

ODP 1.0 makes this recurring plan discoverable, but it does not define recurring subscription behavior. The Service application owns the subscription lifecycle. AEP may provide Service authentication, while MPP or x402 may provide payment. Those protocols do not define renewal, cancellation, or entitlement state.

ODP defines no standard subscribe relation, renewal operation, cancellation contract, entitlement record, or recurring billing state. Do not invent those meanings from the Offering. In this example, the selected Action contract governs only the quote request and response. Any later subscription operations follow contracts defined by the Service application.

Inspect the example artifacts

The published example includes the Full Offering and the Attribute Schema that defines its subscription-specific fields.

• Generated example: open the published Digital subscription example and its source files
• Full Offering: inspect the plan identity, price, attributes, and quote Action
• Attribute Schema: inspect the types and constraints applied to the plan attributes

Next steps