> ## 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.

# Downloading your Library

> Export your whole Octave Library — or any subset of entity types — as Markdown or JSON files, from the app or the API.

## What you get

A Library download is a ZIP archive with one folder per entity type and one file per entity. Folder and file names are the entity type and entity name, so the archive reads like a table of contents:

```
libraries/
├── company/
│   └── Acme.md
├── products/
│   └── Acme Platform.md
├── personas/
│   ├── VP of Sales.md
│   └── GTM Engineer.md
├── segments/
├── use-cases/
├── proof-points/
├── competitors/
├── alternatives/
├── buying-triggers/
├── objections/
├── references/
├── playbooks/
├── solutions/
├── services/
├── writing-styles/
└── brand-voices/
```

If your selection resolves to a single entity, you get that file directly instead of an archive.

Each file is a complete, self-contained rendering of the entity. Some types carry more than their own fields:

| Entity type                   | What the file includes                                                                                                                                                                                                                                |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Products, Services, Solutions | The offering, its [Core Features](/concepts/core-features), and the personas, use cases, references, and segments linked to it. Core features have no folder of their own — each belongs to exactly one offering, and that is where you will find it. |
| Competitors                   | The competitor, its battlecard brief (executive summary, momentum, how to respond, per-section assessments), and its active intel.                                                                                                                    |
| Segments                      | The segment and its active intel.                                                                                                                                                                                                                     |
| Company                       | Your workspace company profile and the market intel researched for it.                                                                                                                                                                                |
| Everything else               | The entity's fields as they appear in the app.                                                                                                                                                                                                        |

Intel sections only contain intel that is active and enabled in your Library Settings; archived, invalidated, and expired intel is left out. A competitor's battlecard appears once its first intel run has generated one.

## Formats

* **Markdown** (default) — headed sections, bullet lists, and tables, ready to paste into a doc, feed to an LLM, or check into a repo.
* **JSON** — the same entities as structured objects with every field, for programmatic use. Intel, battlecards, and core features are nested fields on their parent entity.

## From the app

1. Open **Library** in the left navigation.
2. Click the **⋯** menu in the page header and choose **Download Library**.
3. Pick what to include with the **None / Subset / All** control. In **Subset**, toggle individual entity types, or hover a row and click **Only** to narrow the export to that type.
4. Click **Download**.

Downloading requires the **Export entities** entitlement on your plan. If it is not included, the dialog will tell you before anything is exported.

## From the API

The same export is available as a single request:

```bash theme={null}
curl -X GET "https://api.octavehq.com/api/v2/library/download?entityTypes=Persona,Segment,Competitor&format=MARKDOWN" \
  -H "api_key: YOUR_API_KEY" \
  --output library.zip
```

| Query parameter | Description                                                                  |
| --------------- | ---------------------------------------------------------------------------- |
| `entityTypes`   | Comma-separated list of entity types to include. Omit for the whole library. |
| `format`        | `MARKDOWN` (default) or `JSON`. Case-insensitive.                            |

Valid `entityTypes` values:

`WorkspaceCompany`, `Product`, `Service`, `Solution`, `Persona`, `UseCase`, `Segment`, `Reference`, `ProofPoint`, `Competitor`, `Alternative`, `BuyingTrigger`, `Objection`, `Playbook`, `WritingStyle`, `BrandVoice`

There is no `CoreFeature` value — core features come with their offering.

The response is the file itself. `Content-Type` is `application/zip` for a multi-file download, or `text/markdown` / `application/json` when a single entity is returned; the file name is in the `Content-Disposition` header. Unknown entity types or formats return `400`.

This endpoint is rate limited to 5 requests per minute per API key — it renders the full selection on every call, so export once and keep the file rather than polling it. See the [endpoint reference](/v2-api-reference/library/download-library) for the full schema.

## Where this is useful

* **Giving an AI assistant your whole GTM context.** A Markdown export is a ready-made context pack. If you use the [Octave MCP server](/mcp/overview), the assistant can query the Library live instead, but a static export is useful for tools that cannot connect.
* **Review and sign-off.** Send a subset — say personas and segments — to stakeholders who do not work in Octave.
* **Backups and version history.** Check a JSON export into a repository on a schedule to keep a diffable history of your positioning.
* **Migrating or syncing.** Load the JSON into another system; every entity carries its `oId`, so you can cross-reference it with the individual [entity endpoints](/v2-api-reference/persona/list-persona).