appnz-provider-cursor

name	appnz-provider-cursor
description	Use this skill when the user asks to use Cursor, provider cursor, or any cursor model through app.nz; covers model selection when present, BYOK setup, OpenAI-compatible routing, provider-specific endpoints, aliases, and debugging gateway headers.

Cursor on app.nz

Route Cursor through app.nz with one app.nz key. Use this skill when a user asks for Cursor, cursor, one of its model ids, aliases, product integrations, or BYOK setup for this provider.

Workflow

1. Use /api/gateway/models?provider=cursor to confirm the current public model list if exact availability matters.
2. Call app.nz at https://app.nz/v1 with Authorization: Bearer pk_live_...; do not call https://api.cursor.com directly unless the user explicitly asks to bypass app.nz.
3. Store a user-owned upstream key with POST /api/gateway/provider-keys using provider cursor when BYOK is required. The upstream secret is never returned by app.nz.
4. Prefer a model matching the task modality. If unsure, start with composer-2.5 or app/auto.
5. 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":"cursor","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":"composer-2.5","messages":[{"role":"user","content":"Give me one practical idea."}]}'

Models

Model	Modality	Aliases	Caps
composer-2.5	chat	cursor-composer-2.5, composer-2.5@cursor, composer-2-5, composer-2.5-standard	stream
composer-2.5-fast	chat	cursor-composer-2.5-fast, composer-2.5-fast@cursor, composer-2-5-fast	stream