Collections

A Collection (合集) is a container that groups related resources — documents, images, videos, and audio — into one organized place. Instead of leaving everything flat in your Library, a collection gives a set of files a name, a type, and (optionally) episodes.

Collections are the evolution of the older Knowledge Base: a knowledge base is now simply one type of collection (knowledge_base). Everything you could do with a KB still works — plus you can now create photo albums, podcasts, comic series, TV series, and custom containers.

What a collection holds

Every collection has:

• A type (collectionType) — e.g. knowledge_base, photo_album, tv_series. Fixed at creation (see Collection types).
• Allowed resource types (allowedResourceTypes) — which of doc / image / video / audio may be added. Each type has a sensible default; you can add more later but never remove one.
• Resources — the files themselves, added directly or grouped into episodes.
• Episodes (optional) — numbered partitions like “Season 1 · Episode 3”, each holding its own assets. See Episodes.

Collection  ("My Podcast", type: audio_drama)
├─ Episode 1  → audio + show-notes doc
├─ Episode 2  → audio + show-notes doc
└─ …

Collections without episodes behave like a flat folder (this is the classic knowledge-base flow — docs and images grouped by topic).

Resource types

Four resource types can live in a collection:

Resource	What it is
doc	Documents (Markdown .md / Typst .typ)
image	Images (PNG / JPG / WebP …)
video	Video files
audio	Audio files (MP3 / WAV / FLAC …)

A collection’s allowedResourceTypes gates what you can add. For example a photo_album allows only image; a tv_series allows video, audio, and doc (episodes + subtitles/scripts). Trying to add a resource whose type isn’t allowed is rejected — expand the collection’s allowed types first.

Note

allowedResourceTypes is expand-only. You can widen ['image'] → ['image', 'video'], but you can’t shrink it back. The collectionType itself is immutable once the collection is created — pick the right type up front.

Create & use a collection

In the dashboard at center.picora.me/collections:

1. Click New collection, choose a type, and give it a name.
2. Upload resources — the upload panel lets you assign an image (and, going forward, other media) straight into a collection.
3. For series-style content, open the collection and add episodes, then attach assets to each episode.

The list page groups collections by type (a tab appears for each type you’ve used), and the detail page shows episodes, resource counts, and lets you manage everything.

Quotas

Collections and episodes are metered per plan:

Limit	Trial	Pro	Pro+
Collections	5	50	500
Episodes per collection	50	500	2,000
Custom collection types	—	—	10

Without an active plan the limits are 0 (activate a plan to start creating collections). Hitting a limit returns a clear COLLECTION_LIMIT_REACHED / EPISODE_LIMIT_REACHED error. Custom types are Pro+ only — see Collection types.

Next

• Collection types — the 9 built-in types + creating your own (Pro+).
• Episodes — structure a collection into numbered episodes and attach assets.
• AI Video Sync — push AI-generated media into episodes from ComfyUI / Replicate / Sora with idempotency + dedup + audit.
• For developers — the collections API is fully browsable in the API playground (collection.read / collection.write / collection.delete / episode.write scopes).