Kontainer
Manage assets and products
- Category
- Content & Design
- Primary Subcategory
- Digital Asset & Media Management
Integration details
Description
Kontainer connects ChatGPT to your organization’s DAM and PIM workspace. Find and inspect images, videos, and documents; organize folders and collections; manage asset metadata and CDN delivery; maintain product records and channel data; administer workspace users and permissions; and review usage statistics. Actions run within the authenticated Kontainer tenant and follow the user’s Kontainer permissions.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Digital Asset & Media Management
- Secondary Subcategories
- None listed
- Brand
- Kontainer
- Access
- Account required
- First tracked
- 2026-08-28
- Tool count
- 102
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
ChatGPT Plugin Discovery Score
ChatGPT Plugin discovery is coming soon
ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.
No spam. Unsubscribe any time.
What discovery looks like

Competing in ChatGPT Digital Asset & Media Management
View Category102 tools agents can invoke
Delete many PIM category items in one call — use this instead of calling delete-category-item once per item. Pass `items` as an array; each entry is a single delete-category-item request: { category_id, item_id }. Items are deleted independently — a failure on one is reported in `failed` and the rest still delete. Confirm with the user before calling.
bulk-delete-category-item
Delete many PIM channel items in one call — use this instead of calling delete-channel-item once per item. Pass `items` as an array; each entry is a single delete-channel-item request: { channel_id, item_id }. Items are deleted independently — a failure on one is reported in `failed` and the rest still delete. Confirm with the user before calling.
bulk-delete-channel-item
Delete (move to trash) many files in one call — use this instead of calling delete-file once per file. Pass `file_ids` as an array of file IDs. Items are deleted independently — a failure on one file is reported in `failed` and the rest still delete. Each file must not be trashed and requires delete permission. Confirm with the user before calling.
bulk-delete-file
Delete many folders in one call — use this instead of calling delete-folder once per folder. Pass `folder_ids` as an array of folder IDs. Items are deleted independently — a failure on one is reported in `failed` and the rest still delete. Each folder must not be trashed/locked, contain subfolders, or hold files with external references. To delete a whole tree, order `folder_ids` deepest-first (children before parents) so parents are empty by the time they are processed; each `failed` entry explains how to clear its block. Confirm with the user before calling.
bulk-delete-folder
Attach or update custom-field metadata on many files in one call — use this instead of calling manage-custom-fields once per file. Pass `items` as an array; each entry is a single manage-custom-fields request: { action, file_id, category_id (attach), category_item_id (update), values }. To set the same values on many files, repeat the same category_id + values across entries, varying only file_id. Discover field save_names and the category id exactly as for manage-custom-fields. Items are applied independently — a failure on one file is reported in `failed` and the rest still apply.
bulk-manage-custom-fields
Update or revoke many user-groups' folder access in one call — use this instead of calling manage-folder-group-permission once per group. Pass `items` as an array; each entry is a single manage-folder-group-permission request: { action ('update' or 'remove'), folder_id, user_group_id, permission (for 'update') }. Every entry affects every member of that group and takes effect immediately — confirm the intended groups and scope before calling. Items are applied independently — a failure on one is reported in `failed` and the rest still apply. Requires administrator privileges.
bulk-manage-folder-group-permission
Update or revoke many users' folder access in one call — use this instead of calling manage-folder-user-permission once per user. Pass `items` as an array; each entry is a single manage-folder-user-permission request: { action ('update' or 'remove'), folder_id, user_id, permission (for 'update') }. Every entry takes effect immediately — confirm the intended users and scope before calling. Items are applied independently — a failure on one is reported in `failed` and the rest still apply. Requires administrator privileges.
bulk-manage-folder-user-permission
Update element attributes on many PIM category items in one call — use this instead of calling update-category-item once per item. Pass `items` as an array; each entry is a single update-category-item request: { category_id, item_id, attributes }. Items are applied independently — a failure on one is reported in `failed` and the rest still apply.
bulk-update-category-item
Update element attributes on many PIM channel items in one call — use this instead of calling update-channel-item once per item. Pass `items` as an array; each entry is a single update-channel-item request: { channel_id, item_id, attributes }. Items are applied independently — a failure on one is reported in `failed` and the rest still apply.
bulk-update-channel-item
Rename or update metadata for many files in one call — use this instead of calling update-file once per file. Pass `files` as an array; each entry is a single update-file request: { file_id, folder_id, name }. Items are applied independently — a failure on one file is reported in `failed` and the rest still apply.
bulk-update-file
Update many folders in one call — use this instead of calling update-folder once per folder. Pass `folders` as an array; each entry is a single update-folder request: { folder, name, description, ... }. Items are applied independently — a failure on one is reported in `failed` and the rest still apply.
bulk-update-folder
Update many users in one call — use this instead of calling update-user once per user. Pass `users` as an array; each entry is a single update-user request: { user_id, name, email, active, ... }. Items are applied independently — a failure on one is reported in `failed` and the rest still apply.
bulk-update-user
Move or copy files and/or folders into a destination folder. Actions: 'move' relocates items (originals disappear from their source); 'copy' duplicates them; 'archive-move' moves items across the archive boundary — use when the user asks to archive assets (destination is an archived folder) or restore them from archive (sources are archived, destination is not). Archive moves are destructive: they strip album/collection references and other runtime links. Every source must be on the same side of the archive boundary (all archived, or all not archived). Requires the Archive feature to be enabled on the client. Handle name collisions with file_conflict_resolution: 'rename' (default — keep both), 'skip', or 'overwrite'. Only file and folder resource types are accepted in `sources`.
transfer-to-folder
Create a new album (a.k.a. collection) — a curated selection of files drawn from any folders in the DAM, without moving the originals. Use when the user asks to "make a collection", "build a selection for the press release", "group these photos for a campaign", or "share a curated set". Add files afterwards with `manage-album-files`.
create-album
Create a new item within a specific variation of a PIM category — this is where a product record lives (name + description at creation time; fill fields via element options afterwards). Use when the user asks to "add a product", "create a new SKU", or "register a new item". Requires both category_id and variation_id; call `get-category-structure` first if you don't know the variation. After creation, populate element values and sync to channels with `create-channel-item`.
create-category-item
Create a variation of an existing category item with its own attribute values — used for SKU-level variants (size/colour/market/language) that diverge from the parent. Use when the user asks to "add a size variant", "create the blue version", or "make a localized copy". Pass `attributes` keyed by element code with a `value` property; only variation-enabled elements are accepted. See `create-item-variation` for the alternate cloning flow.
create-category-variation-item
Publish (create) an item in a PIM channel — the channel-specific projection of a catalog item (e.g., the webshop copy, translated title, channel-specific images). Use when the user asks to "send this product to a channel", "push to the webshop", or "localize for the French store". Pass `attributes` keyed by element code with a `value` property; only channel-mapped elements are accepted. Requires channel_id and variation_id; the parent item is derived from the variation.
create-channel-item
Create a variation of an existing channel item with its own attribute values — used when a published product needs channel-level variants (e.g., size/colour entries for a marketplace that expects one listing per SKU). Use when the user asks to "add the size variants to the webshop" or "publish all colourways". Pass `attributes` keyed by element code with a `value` property.
create-channel-variation-item
Enable CDN streaming for a video file — triggers transcoding to streaming-friendly formats and makes the file embeddable via `get-cdn-video-embed-settings`. Use when the user asks to "make this video streamable", "enable CDN for playback", or "get an embed code for a video". Set allow_download=true if the public viewer should be able to download the original. Requires the CDN feature.
create-file-cdn-video
Create a new folder (or sub-folder) in the asset library — for a campaign, project, brand, partner, etc. Requires a parent folder and a unique name within that parent. Optional: description, layout flags (show_large_folder_name, hide_folder_name, thumbs_scale_to_fit, apply_folder_image_hue), thumbnail file.
create-folder
Create an additional variation of an existing category item — used when the same product needs market-, language-, or attribute-specific versions (e.g., EU vs US copy, color variants). Use when the user asks to "add a variant", "create a localized version", or "duplicate for another market". Supply variation_data describing the variation's attribute overrides. Use `create-category-variation-item` when starting from a fresh item rather than cloning.
create-item-variation
Create a mirror folder under a parent folder. Required: source_folder_id. Optional attributes: name, description, show_large_folder_name, hide_folder_name, thumbs_scale_to_fit, apply_folder_image_hue, is_synced_mirror, mirror_design.
create-mirror-folder
Create a new PIM resource — a reusable data record (e.g., brand, manufacturer, material) that items can reference via a resource-typed element instead of inlining the same data repeatedly. Use when the user asks to "add a brand", "register a supplier", or "define a new material" for the catalog. Pass `attributes` keyed by element code with a `value` property. Resources are scoped to one category.
create-pim-resource
Create a new user account in the Kontainer workspace. Use when an admin asks to "add a user", "invite a teammate", or "onboard a colleague". Email must be unique within the client. Set sendInvite=true to email the new user a link to set their password (recommended for most flows). After creation, assign group membership with `manage-user-group-membership` and folder access with `manage-folder-user-permission`. Requires administrator privileges.
create-user
Create a new user group. Groups are the recommended way to manage folder permissions at scale — grant access to a group once, then add/remove members. Use when the user asks to "create a team", "add a department", or "set up a new client group". Optional flags control per-group capabilities: folder sharing, internal sharing, CDN activation with download. After creation, add members with `manage-user-group-membership` and grant folder access with `manage-folder-group-permission`. Requires administrator privileges.
create-user-group
Permanently delete a PIM category item (product). Irreversible — ask the user to confirm before calling. Fails if the item is referenced as a resource in other items. Deleting also removes any variations of this item and its channel-item counterparts across all channels. Call `list-external-references` or inspect `channel_items` via `get-category-item` first to see downstream impact.
delete-category-item
Remove an item from a PIM channel (unpublishes it from that channel only — the underlying category item stays intact). Irreversible — ask the user to confirm before calling. Fails if this channel item is referenced as a resource in other items. Use when the user asks to "unpublish this from the webshop", "remove from the French store", or "pull this listing".
delete-channel-item
Move a file to trash (soft delete). The file must not already be trashed and the user needs delete access on the original folder. Before deleting, consider calling `list-file-deletion-warnings` to see any broken external references the delete would cause. To restore, use `list-files-by-state` with state="trashed".
delete-file
Disable CDN streaming for a video file — removes the transcoded renditions and breaks any existing embed codes. Irreversible — ask the user to confirm before calling, especially if the embed might be live on a public page. The underlying source video remains untouched and can be re-enabled later with `create-file-cdn-video`.
delete-file-cdn-video
Delete an empty folder. Fails if the folder has sub-folders, files with external references, is locked, or already in the trash. Requires delete access. Check `list-file-deletion-warnings` / `list-folder-deletion-warnings` first if the user is about to delete something that might break downstream references.
delete-folder
Remove a file's custom thumbnail and fall back to the auto-generated preview. Use when the user asks to "reset the thumbnail", "revert to the default preview", or "remove the custom thumbnail". The underlying file is not affected; only the custom preview image is deleted. Re-upload a replacement anytime with `upload-thumbnail`.
delete-thumbnail
Permanently delete a regular (single) user account. Does NOT work on shared users or administrators — those return "resource not found"; tell the user shared/admin accounts can't be deleted here. Irreversible. Removes the user's group memberships and folder permissions; historical activity (uploads, operation logs) is preserved under the deleted user's name. To revoke access temporarily instead, call `update-user` with active=false. Requires administrator privileges.
delete-user
Permanently delete a user group. Irreversible — ask the user to confirm before calling. Deleting a group revokes every folder permission granted via it; members themselves are not deleted but lose the group's access. Call `get-user-group` with includes=users first to see who is affected. Requires administrator privileges.
delete-user-group
Find files whose content is identical (matched by hash). Use when the user asks about "duplicate photos", "the same image uploaded twice", "storage cleanup", or "which files can I remove". Omit file_id to list every duplicate group in the DAM; pass a file_id to get the duplicates of that specific file.
find-file-duplicates
Retrieve CDN usage statistics — bandwidth, request counts, and top assets served via the public CDN. Use when the user asks about "CDN bandwidth", "our most-viewed public images", "embed traffic", or campaign reach via public links. Supports filter (by file, date range), pagination, and sort.
get-cdn-statistics
Retrieve embed settings and HTML code for embedding a CDN video with customizable player options.
get-cdn-video-embed-settings
Fetch a single PIM category item by ID — all element values (fields), variation data, channel sync state, and related resources. Use when the user asks about a specific product, or you need the item record before updating it or syncing to a channel. Relationships/includes: category, variations, channel_items, resources.
get-category-item
Fetch the full structure of a PIM category — the ordered list of elements (fields), their types, option sets, and variation configuration. Use before creating/updating items so you know which attributes are valid, required, or variation-specific. Pair with `list-elements` or `list-element-resource-options` for deeper field/option details.
get-category-structure
Fetch a single channel item by ID — the channel-specific attribute values for a published product. Use when the user asks about a specific product on a specific channel ("show me how this product looks in the French webshop"), or before updating/deleting its channel presence.
get-channel-item
Retrieve download statistics — which files have been downloaded, by whom, when, via which template. Use when the user asks "what are our most-downloaded assets", "did anyone grab that campaign photo", "download activity by department", or for usage reporting. Supports filter (by user, file, date range, template), pagination, and sort.
get-download-statistics
Fetch a single file by ID — name, attributes, folder, albums, tags, custom fields, CDN status, video CDN, focal point, face detection. Use whenever the user asks about one specific asset in detail, or you need the file record before a downstream action. Relationships/includes: folder, albums, mirror_folders, smart_folders, tags, cdn, custom_fields, created_by, video_cdn, focal_point, faces. When includes resolve, the response contains a `file.relationships` object with the included records inlined — e.g. `includes='custom_fields'` surfaces `file.relationships.custom_fields[*].attributes` (current values) and `file.relationships.custom_fields[*].id` (the category_item_id needed for manage-custom-fields action='update').
get-file
Fetch CDN video details for a file — transcoding status, available renditions, streaming URL, and allow_download flag. Use when checking whether a video is ready to stream/embed, or as a lookup before updating its settings. For the HTML embed snippet and player options use `get-cdn-video-embed-settings` instead.
get-file-cdn-video
Fetch a single folder by ID — name, description, hierarchy, flags and related folders. Use when the user asks about a specific folder (details, parent, source) or you need the folder record before another operation. Supports include/relationships: parent_folder, source_folder.
get-folder
Fetch a single global variable by ID — a workspace-wide key/value setting used in templates, CDN embeds, branding, etc. Use when the user asks about a specific variable's value or needs the record before reporting a configuration.
get-global-variable
Retrieve login statistics — who logged in, when, and how often. Use when the user asks "who's been active", "who hasn't logged in recently", "login activity for last month", or for license/seat audits. Supports filter (by user, date range), pagination, and sort.
get-login-statistics
Fetch Kontainer system meta — configured languages, enabled features, current client info, and workspace-level settings that other tools rely on. Useful as a first orientation call (or when the user asks "what languages do we support", "which features are enabled", "who am I logged in as").
get-meta
Fetch a single PIM category by ID — name, description, variation configuration, and counts. Use when the user asks about a specific product category or you need the category record before creating/listing items. For the full element schema (fields, types, options) use `get-category-structure` instead.
get-pim-category
Fetch a single PIM channel by ID — name, configuration, source category, element mapping, and connected variation(s). Use when the user asks about a specific channel, or before creating/listing items in it.
get-channel
Fetch a single PIM element (field) by ID — its code, label, type (string, number, reference, asset, etc.), validation rules, and whether it's required/variation-enabled. Use when you need to understand one field before setting a value or when translating element labels. For the full list of elements in a category use `list-elements` or `get-category-structure`.
get-element
Retrieve upload statistics — files uploaded to the DAM by whom, when, how much. Use when the user asks "how much has the team uploaded this month", "storage growth over time", or "which users are adding the most content". Supports filter (by user, date range, folder), pagination, and sort.
get-upload-statistics
How do I improve a ChatGPT Plugin's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Kontainer alternatives on ChatGPT?
As of 2026-08-28, Kontainer competes with CI HUB, Jackpot, Partoska, Tolstoy Library, withPICA in ChatGPT Digital Asset & Media Management, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.