<aside> 🧭

</aside>

User Guides

Connecting MCP Client to Cashmere MCP Server

How to access Wiley Content in Perplexity

How to get a Content License

Publisher Guides

Creating Omnipub Collections

Preparing Structured Data for Ingestion

Types of License Rights

Uploading New Content via the website

Developer Guides

API Docs

Cashmere Link Guide (OAuth) Overview

Third-Party OAuth Integration Guide for Publishers (BYOL / Short Link)

Connecting Wiley with Perplexity | DEPRECATED

Cashmere MCP Tools

Creating Collections

Collections are groupings of Omnipubs that you, as a publisher, make available for licensing to applications. Collections define how your content is organized, priced, discovered, and accessed. You may create collections for specific products (e.g., a book series), for themed bundles, for licensing tiers, or for internal testing.

This page explains each field and setting available when creating a collection.

Basic Information

Name

The display name of the collection. This is how the collection will appear throughout your Cashmere account and within licensing workflows. Choose something recognizable for both you and the licensees who will encounter it.

Description

A short internal description to help you remember the purpose, scope, or contents of the collection. This is visible only to you and your team; it is not shown to licensees unless you make a collection public (below).

MPT Rate ($)

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

• A “token” roughly corresponds to a word.
• 1 MPT ≈ 800,000–1,000,000 words.
• You can set this rate to any dollar amount, including 0.0 for free access.

The MPT rate determines how much a licensee pays when their RAG application consumes content from this collection.

(See the MPT Pricing documentation for more detail.)

Subdomain

Currently unused. We recommend leaving this field blank unless instructed by Cashmere support.

Collection Settings

Publicly Visible

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

• Enabled (Public):

  The collection appears in Cashmere’s public “License Content” directory. Any user may find it and request a license.

• Disabled (Private):

  The collection is visible only within your own account. No user can discover or request access unless you explicitly grant a license.

Private collections are useful for:

• internal teams,
• controlled pilots,
• partner-only licensing flows,
• content under review.

Auto Approve

Available only when Publicly Visible is enabled.

If Auto Approve is turned on:

• Any user who requests a license will be automatically approved and granted access to the collection.

If turned off:

• Users may still apply for a license, but you must manually approve or reject each request.

This allows you to control onboarding friction based on your business goals.

View Source Actions

When a user views source content returned from a RAG workflow, Cashmere determines where to send them based on the action order you define.

This is a prioritized sequence:

Cashmere attempts the first action; if it is not available for a given Omnipub, it falls back to the next one.

Available Actions

View on Cashmere

This directs the user to view the content on Cashmere.

The actual user experience depends on their license rights (see: Types of License Rights for more information):

• With READ_RAG_SOURCE, the user may view the full source section.
• Without it, the user will see only the landing page, which includes:
  • the snippet,
  • a time-limited link,
  • the publisher-controlled redirect.

“View on Cashmere” is always available and is used whenever no other valid destination is found.

Publisher Source URL

Each Omnipub can optionally include a “canonical” URL defined by the publisher. This may be:

• a purchase page,
• a subscription portal,
• a publisher’s reading platform,
• documentation or product pages,
• any external landing experience.

If Publisher Source URL is placed first in the action order:

• Users will be sent directly to the publisher’s canonical destination.
• Cashmere’s landing page may be completely bypassed.

If an Omnipub does not specify a publisher source URL:

• Cashmere falls back to View on Cashmere.

This system ensures predictable user routing while respecting publisher preferences.

Manage Omnipubs

A collection can be built in two ways: Manual or Dynamic.

Manual Collections

A manual collection is static.

You explicitly choose which Omnipubs belong in the collection.

Key properties:

• Content remains fixed unless you manually add or remove items.
• Best used for curated bundles, premium product offerings, or controlled licensing units.

Manual collections are simple, predictable, and provide full control over scope.

Dynamic Collections

A dynamic collection automatically updates based on:

1. Tags,
2. Other collections (manual only).

You define the tags and collections that should feed into the dynamic collection, and Cashmere continuously maintains the membership.

Example:

Suppose you have several Omnipubs tagged with “Machine Learning.”

You create a dynamic collection based on the

Anytime new Omnipubs are ingested and tagged with “Machine Learning,” they automatically appear in this collection without any manual work.

Dynamic collections are ideal for:

• keeping topic-based bundles automatically up to date,
• building licensing tiers grouped by content categories,
• maintaining large or frequently changing corpora.

Important Restrictions

• Dynamic collections cannot include other dynamic collections.
• This ensures predictable content sets and prevents recursive or inconsistent dependency chains.

Summary

| --- | --- |