AI model sync for every API user
Zywrap keeps the offline catalog SDK Enterprise-only, but every authenticated API user can safely fetch and sync the current AI model list. This keeps integrations updated when new models are added or old models are retired.
Normal API key access
Use the same Zywrap API key used for V2 runs. No Enterprise catalog permission is required.
Delta-friendly sync
Pass fromVersion to receive only changed models and deleted model codes.
Catalog remains protected
Runtime sync does not expose wrappers, use cases, prompts, schemas, or offline bundle data.
Runtime AI model endpoints
These endpoints are intentionally separate from the Enterprise Catalog SDK endpoints. They are safe for normal API users and should be used by apps that show a model picker, cache supported models, or validate model codes before calling POST /v2/runs.
/v1/sdk/runtime/statusCheck whether runtime sync is reachable with the current API key./v1/sdk/runtime/modelsFetch the current safe AI model list as a full snapshot./v1/sdk/runtime/models/syncFetch a full snapshot or a delta when fromVersion is provided./v1/sdk/runtime/syncAlias for runtime model sync. Useful for generic client code.Exposed metadata
- AI model code and display name
- Provider code and provider display name
- Model/provider active status
- Computed availability flag
- Ordering and updatedAt timestamp
- Deleted model codes for delta cleanup
Not exposed here
- Enterprise catalog ZIP or offline bundle
- Use cases, wrappers, prompt templates, or prompt logic
- Input schemas, wrapper profiles, or hidden business rules
- Billing logic, model routing rules, or provider credentials
Quick test with curl
Use the first request for a full list. Store newVersion, then pass it as fromVersion on future syncs.
Node.js runtime model sync example
This example keeps a local model cache fresh without downloading the Enterprise catalog bundle.
Response shape
A missing fromVersion returns a full snapshot. A valid fromVersion returns a delta update.
Ready to run workflows?
After syncing models, use the selected model code with live Zywrap runs. Execution, prompt logic, files, artifacts, and usage ledger still stay on Zywrap APIs.