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 is a Service?
A Service is an offering type that represents the consulting, implementation, advisory, managed, or professional services your company sells. Services sit alongside Products and Solutions as one of the three offering types in the Octave 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, 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 graph:- Personas — who buys and benefits from the service
- Use Cases — problems the service addresses
- Motions — strategies built around the service
- References — customer success stories
- Competitors — other firms competing on the same engagement
- Alternatives — in-house delivery, “do nothing”, manual processes
- Proof Points — outcome metrics from past engagements
- Buying Triggers — events that drive service demand
Managing Services via API
GET /api/v2/service/list— list servicesGET /api/v2/service/get— get a servicePOST /api/v2/service/create— create a servicePOST /api/v2/service/generate— AI-generate a service definition from your site or descriptionPOST /api/v2/service/update— update a servicePOST /api/v2/service/delete— delete a service