​
Manage artifacts

The dashboard is the primary place to view, search, and manage your artifacts. You can also use the API for automation.

​
Artifact lifecycle

An artifact moves through the following states:
  • pending: metadata exists but the upload has not been confirmed.
  • ready: the file is uploaded and the checksum matches.
Visibility is separate from status:
VisibilityWho can downloadSet by
privateMembers of your organizationUpload or dashboard
publicAny customerDashboard

​
Viewing artifacts

In the dashboard at kvcachestore.com/app, the app page lists:
  • Your organization’s private artifacts.
  • Public artifacts from the community.
  • Storage usage and quota for the active organization.

​
Searching and filtering

Use the search bar to filter by name, model, or description. Public artifacts are included in the community catalog once their status is ready and visibility is public.

​
Visibility

Visibility controls who can see and download an artifact.
VisibilityWho can downloadSet by
privateMembers of your organizationUpload or dashboard
publicAnyone with the public CDN URLDashboard
To make an artifact public:
  1. Open the artifact in the dashboard.
  2. Click Set visibility to public.
To make a public artifact private, use the same control. There is no administrator approval step in the current implementation.

​
Download and consume an artifact

​
Private artifacts

Members of the owning organization can request a time-limited presigned download URL from the portal: 
curl -X POST \
  -H "Authorization: Bearer $API_KEY" \
  https://api.kvcachestore.com/api/v1/artifacts/{artifact_id}/download-url

​
Public artifacts

Public artifacts are served directly from the CDN. The dashboard shows the public URL: 
https://x.kvcdn.io/{org_slug}/{project_slug}/{artifact_id}
Fetch it with a plain GET: 
curl -L -o context.kv https://x.kvcdn.io/{org_slug}/{project_slug}/{artifact_id}

​
Load the KV cache

The downloaded .kv file contains safetensors tensors and a JSON sidecar. Load the tensors into the corresponding layer positions of the same model that produced them, then run generation starting from token position num_tokens. The model reuses the cached context instead of prefill.

​
Deleting artifacts

Deleting an artifact removes its metadata from the portal. The underlying object in storage may remain until a garbage-collection run. Storage usage is updated immediately.

​
Storage usage

The dashboard shows used_bytes and quota_bytes for the active organization.

​
Audit logging

The portal records audit logs for artifact creation, upload confirmation, visibility changes, API key management, and billing events. Administrators can view these logs in the admin dashboard.