| name | appnz-provider-netwrck |
| description | Use this skill when the user asks to use Netwrck, provider netwrck, or any netwrck model through app.nz; covers model selection when present, BYOK setup, OpenAI-compatible routing, provider-specific endpoints, aliases, and debugging gateway headers. |
Netwrck on app.nz
Route Netwrck through app.nz with one app.nz key. Use this skill when a user asks for Netwrck, netwrck, one of its model ids, aliases, product integrations, or BYOK setup for this provider.
Workflow
- Use
/api/gateway/models?provider=netwrck to confirm the current public model list if exact availability matters.
- Call app.nz at
https://app.nz/v1 with Authorization: Bearer pk_live_...; do not call https://netwrck.com directly unless the user explicitly asks to bypass app.nz.
- Store a user-owned upstream key with
POST /api/gateway/provider-keys using provider netwrck when BYOK is required. The upstream secret is never returned by app.nz.
- Prefer a model matching the task modality. If unsure, start with
ra1 or app/auto.
- Read
X-Gateway-Provider and X-Gateway-Model response headers when debugging routing.
BYOK
curl -sX POST https://app.nz/api/gateway/provider-keys \
-H "Authorization: Bearer pk_live_..." \
-H "Content-Type: application/json" \
-d '{"provider":"netwrck","api_key":"REDACTED_UPSTREAM_KEY"}'
Chat Example
curl -s https://app.nz/v1/chat/completions \
-H "Authorization: Bearer pk_live_..." \
-H "Content-Type: application/json" \
-d '{"model":"ra1","messages":[{"role":"user","content":"Give me one practical idea."}]}'
Models
| Model | Modality | Aliases | Caps |
|---|
| ltx-2 | video | netwrck-ltx2, ltx2 | - |
| ltx-video | video | ltx-video-v097, netwrck-ltx | - |
| ra1 | image | netwrck-image, netwrck-art | - |
| ra2v | video | netwrck-video, smart-video | - |
| wan | video | netwrck-wan, wan-video | - |
| zimage | image | netwrck-anime, anime-image | - |
