Creating and Configuring Collections

Collections are groupings of Omnipubs that you make available for licensing to applications. They define how your content is organized, priced, discovered, and accessed — making them one of the most important building blocks in your Cashmere account.

This guide walks through creating a collection step by step, explains every field and setting, and covers how to delete a collection when you no longer need it.

---

Creating a Collection (Step by Step)

1. Log in to the Console at cashmere.io/accounts/login.
2. Navigate to cashmere.io/collections.
3. Click Create Collection.
4. Fill in the fields described below.
5. Click Save (or Create) to create the collection.

Your collection is now available in your account. You can add Omnipubs to it immediately via the Console upload flow or the API.

---

Field Reference

Basic Information

Name

The display name of your collection. It appears throughout your Cashmere account and in any licensing workflows where a licensee encounters it.

Use: Choose a name that is recognizable to both your own team and to the licensees who will apply for access — something that clearly signals the scope or purpose of the content inside.

---

Description

A short internal note about the collection's purpose, scope, or contents.

This field is visible only to you and your team. It is not shown to licensees unless the collection is made publicly visible.

Use: Write something that helps your team remember why the collection exists and what belongs in it — especially useful when managing many collections or onboarding new teammates.

---

MPT Rate ($)

The consumption rate for this collection, billed per Million Premium Tokens (MPT).

• One token roughly corresponds to one word.
• 1 MPT ≈ 800,000–1,000,000 words.
• You can set this to any dollar amount, including $0.00 for free access.

This rate determines how much a licensee is charged when their RAG application consumes content from this collection.

Use: Set a rate that reflects the value and exclusivity of the content. Use $0.00 for internal testing, development API keys, or content you want to distribute freely.

See also: MPT Pricing documentation for full detail on how token consumption is calculated.

---

Subdomain

Currently unused. Leave this field blank unless Cashmere support instructs you otherwise.

---

Collection Settings

Publicly Visible

Controls whether other users can discover your collection and apply to license it.

Setting	Behavior
Enabled (Public)	The collection appears in Cashmere's "License Content" directory. Any user can find it and request a license.
Disabled (Private)	The collection is only visible inside your own account. No one can discover or request access unless you explicitly grant a license to them.

Use Public when: You want open or semi-open discovery — for example, a commercial product offering you want partners and developers to find and license.

Use Private when:

• Running a controlled pilot or beta
• Working with a specific named partner only
• The content is still under review or not ready for general licensing
• Managing an internal team's access

---

Auto Approve

Only available when Publicly Visible is enabled.

Setting	Behavior
On	Any user who requests a license is automatically approved and granted access immediately.
Off	Users can still apply, but each request requires manual approval or rejection from you.

Use Auto Approve when: You want zero onboarding friction — for example, a free or open collection where any requester should be let in automatically.

Turn it off when: You want to vet who accesses your content, enforce agreements or terms, or manage a limited rollout where you approve licensees one by one.

---

View Source Actions

When a user's application surfaces a result from your content in a RAG workflow, Cashmere needs to know where to send them when they click through to the source. This setting defines that routing as an ordered list of actions. Cashmere tries the first action; if it isn't available for a given Omnipub, it falls back to the next one.

View on Cashmere

Sends the user to view the content on Cashmere directly. The experience depends on the user's license rights:

• With READ_RAG_SOURCE rights: the user can view the full source section.
• Without it: the user sees a landing page with the snippet, a time-limited link, and any publisher-configured redirect.

"View on Cashmere" is always available as a fallback — it will be used whenever no other valid destination exists.

Publisher Source URL

Each Omnipub can optionally have a canonical URL defined by you as the publisher — a purchase page, subscription portal, your own reading platform, or any external landing experience.

If Publisher Source URL is placed first in the action order, users are sent directly to that destination and Cashmere's landing page is bypassed entirely. If a given Omnipub has no publisher source URL set, Cashmere automatically falls back to "View on Cashmere."

Use Publisher Source URL first when: You want to drive users back to your own platform — for purchase, sign-up, or reading within your own product.

Use View on Cashmere first when: You don't have (or don't need) a destination URL for each Omnipub, or you're comfortable with users landing on Cashmere's native reading experience.

---

Manage Omnipubs

This is where you define which Omnipubs belong to the collection. There are two approaches: Manual and Dynamic.

Manual Collections

A manual collection is static — you explicitly choose which Omnipubs belong to it, and the contents stay fixed until you change them.

Use when:

• Building a curated bundle (e.g., a specific series or a premium product tier)
• You want full, predictable control over exactly what is licensed
• The collection is small or won't change frequently

Dynamic Collections

A dynamic collection updates automatically based on rules you define — either tags or other manual collections. As new Omnipubs are tagged appropriately, they appear in the dynamic collection without any manual work.

Use when:

• You have a large or frequently changing corpus
• You want topic-based bundles to stay up to date automatically
• You're managing content at scale and manual curation isn't practical

Important: Dynamic collections can only reference manual collections as inputs — not other dynamic collections. This prevents recursive dependencies and keeps your content sets predictable.

---

Deleting a Collection

Note: Deleting a collection is permanent. Any active licenses tied to that collection will lose access to its content. Make sure no active licensees depend on the collection before deleting it.

Via the Console

1. Navigate to cashmere.io/collections.
2. Open the collection you want to delete.
3. Look for the Delete option in the collection's settings or action menu.
4. Confirm the deletion when prompted.

Via the API

Send a DELETE request to the collections endpoint. You must be the owner of the collection.

DELETE /api/v2/collections/{collection_id}

A successful deletion returns 204 No Content. If the collection is not found or you are not the owner, a 404 is returned.

See the full API reference for authentication requirements.

---

Quick Reference

Field	What it does	When to use
Name	Display name throughout Cashmere and licensing UI	Always — choose something clear for you and your licensees
Description	Internal note on purpose/scope	Recommended; required if managing many collections
MPT Rate	Consumption billing rate per million tokens	Set to reflect content value; use $0 for free/test access
Subdomain	Reserved for future use	Leave blank unless instructed
Publicly Visible	Controls discoverability in the license directory	Public for open licensing; Private for controlled access
Auto Approve	Auto-grants licenses on request	On for frictionless access; Off to vet licensees manually
View Source Actions	Where users go when clicking through from RAG results	Order actions by your preferred destination priority
Manual / Dynamic	How Omnipub membership is managed	Manual for curated, fixed sets; Dynamic for tag-driven, auto-updating sets