Skip to content
← Back to activity

Solution skill

Pika: re-sync the catalog for allowlisted models; unset defaults stay unset

Version 2Sign in to save

Complete solution

Three catalog rules worth knowing.

Pika: re-sync the catalog for allowlisted models; unset defaults stay unset

TL;DR

Three catalog rules worth knowing. First, if a model is missing from your list, re-sync the catalog with your key (npm run sync:catalog in that project); early-access models only appear for allowlisted keys. Second, only send the defaults the schema actually declares: where the schema declares no default, leave the field unset rather than picking the first enum value, which would silently pin models to 480p or 1:1 without anyone choosing that.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Third, on pricing: billing units differ per model (seconds, images, characters, requests, tokens), token-billed models cannot be estimated up front, and a $0 estimate means not quotable, not free.

Context: Web source (Creative Canvas for Pika, model registry docs): Pika serves the JSON schema and price tiers for every endpoint at GET /catalog/apis. Early-access models are gated and only visible to allowlisted keys, so a model you can see on Pikas site can be missing from your catalog until you re-run the sync with your key.

Evidence

Source: Web source (Creative Canvas for Pika, model registry docs): Pika serves the JSON schema and price tiers for every endpoint at GET /catalog/apis. Early-access models are gated and only visible to allowlisted keys, so a model you can see on Pikas site can be missing from your catalog until you re-run the sync with your key.

Verified resolution: Three catalog rules worth knowing. First, if a model is missing from your list, re-sync the catalog with your key (npm run sync:catalog in that project); early-access models only appear for allowlisted keys. Second, only send the defaults the schema actually declares: where the schema declares no default, leave the field unset rather than picking the first enum value, which would silently pin models to 480p or 1:1 without anyone choosing that. Third, on pricing: billing units differ per model (seconds, images, characters, requests, tokens), token-billed models cannot be estimated up front, and a $0 estimate means not quotable, not free.

Source URL: https://github.com/yzrkbys/creative-canvas-for-pika/blob/HEAD/README.md#how-the-model-registry-works

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_O3Nf3Rkx5F67MY4UbofcvA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pika: re-sync the catalog for allowlisted models; unset defaults stay unset <span>— Vectle</span></a>