> ## Documentation Index
> Fetch the complete documentation index at: https://docs.octavehq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What are Services in Octave?

> Services are an offering type for everything you sell that isn't a product — consulting, implementation, managed services, advisory work.

## What is a Service?

A Service is an [offering](/concepts/offerings) type that represents the consulting, implementation, advisory, managed, or professional services your company sells. Services sit alongside [Products](/concepts/offerings) and [Solutions](/concepts/solutions) as one of the three offering types in the [Octave Library](/concepts/library). Where a Product captures features and capabilities, a Service captures deliverables, competencies, and the comparative advantage of *how* you deliver — the dimensions that actually matter when agents position services-based revenue.

Every persona, use case, [motion](/concepts/motions), and qualifying question can attach to a Service exactly like it can to a Product. The downstream library structure is identical; only the offering's shape differs.

## What a Service contains

| Field                 | Purpose                                       |
| --------------------- | --------------------------------------------- |
| Name                  | External-facing service name                  |
| Internal name         | Internal alias used by your team              |
| Description           | What the service does and who it's for        |
| Primary URL           | Service page link                             |
| Summary               | One-paragraph overview                        |
| Deliverables          | What the customer actually receives           |
| Competencies          | Skills and expertise required to deliver it   |
| Comparative advantage | Why your delivery beats the alternatives      |
| Likely alternative    | What prospects fall back on if they don't buy |
| Challenges addressed  | The problems this service solves              |
| Customer benefits     | What changes for the customer after delivery  |
| Qualifying questions  | Questions to assess service fit               |

## How Services connect to other entities

Services play the same role as Products in the [Library](/concepts/library) graph:

* **[Personas](/concepts/personas)** — who buys and benefits from the service
* **[Use Cases](/concepts/use-cases)** — problems the service addresses
* **[Motions](/concepts/motions)** — strategies built around the service
* **[References](/concepts/references)** — customer success stories
* **[Competitors](/concepts/competitors)** — other firms competing on the same engagement
* **[Alternatives](/concepts/alternatives)** — in-house delivery, "do nothing", manual processes
* **[Proof Points](/concepts/proof-points)** — outcome metrics from past engagements
* **[Buying Triggers](/concepts/buying-triggers)** — events that drive service demand

## Managing Services via API

* `GET /api/v2/service/list` — list services
* `GET /api/v2/service/get` — get a service
* `POST /api/v2/service/create` — create a service
* `POST /api/v2/service/generate` — AI-generate a service definition from your site or description
* `POST /api/v2/service/update` — update a service
* `POST /api/v2/service/delete` — delete a service