> ## 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 Core Features in Octave?

> Core Features are the distinctly-named pieces of an offering — nameable, often marketed as their own thing, but not their own go-to-market motion.

## What is a Core Feature?

A Core Feature is a distinctly-named piece of one offering — "Agent Builder", "Deal Rooms", "Autopilot". It's the kind of capability that has its own name, its own page on your website, maybe even its own line item on an order — but it is *not* its own offering, because it doesn't carry its own go-to-market motion.

That distinction is the most consequential structural decision in the [Library](/concepts/library). An item earns its own [Offering](/concepts/offerings) only if it stands alone as a sales motion: its own quota, a distinct buyer, a sales conversation you could book separately. Being nameable or marketed as its own thing does **not** clear that bar. If you'd sell two things in the same meeting to the same buyer, that's one offering with Core Features — not two offerings. Getting this wrong fragments everything downstream: a workspace with eight "products" that are really one platform ends up with eight [Motions](/concepts/motions), eight thin ICP matrices, and agents wired to the wrong things.

## What a Core Feature contains

Each Core Feature belongs to exactly one offering and carries four narrative fields that give agents its full story:

| Field           | Question it answers                        |
| --------------- | ------------------------------------------ |
| Why this exists | What gap or demand led to building it      |
| What it does    | The capability, in buyer terms             |
| How it works    | The mechanism, for technical conversations |
| What it impacts | The outcomes it moves                      |

The feature's customer outcomes stay modeled as [Use Cases](/concepts/use-cases) linked to the parent offering — the Core Feature holds the feature-specific narrative, and the offering keeps one clean Motion matrix.

## How agents use Core Features

Feature-level specifics earn their place in later-stage conversations: technical evaluations, comparison requests, and the "can it actually do X?" moments. Agents cite a product's Core Features when the context calls for concrete capability detail — and because each feature is anchored to one offering, they never attribute a capability to the wrong product.

## Managing Core Features via API

* `GET /api/v2/core-feature/list` — list features, filterable by offering
* `GET /api/v2/core-feature/get` — get a specific feature
* `POST /api/v2/core-feature/create` — create a feature on an offering
* `POST /api/v2/core-feature/update` — update a feature
* `POST /api/v2/core-feature/generate` — generate features for an offering from its existing context
* `DELETE /api/v2/core-feature/delete` — delete a feature