Skip to main content

​
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:
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: 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:
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 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, 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.