Partners and white-label

Every signed-in user can open Partner. You get a referral link, referred-user analytics, and optional white-label child accounts.

Child accounts have their own API keys. Token usage is billed to the parent. Usage logs stay on the child. After the first lookup the auth cache stores bill_to_user_id, so streaming TTFT is not hurt by the extra hop.

Endpoints (JWT)

Method	Path	Description
GET	`/api/partner`	Profile, referral links, children, own usage
POST	`/api/partner/codes`	Create a referral code
POST	`/api/partner/codes/{id}/primary`	Set primary code
POST	`/api/partner/children`	Create a child user
POST	`/api/partner/children/{id}/keys`	Mint a child key, billed to you

Create a child

curl https://api.proxy.gonka.gg/api/partner/children \
  -H "Authorization: Bearer <jwt-token>" \
  -H "Content-Type: application/json" \
  -d '{"email":"customer@example.com","password":"optional-password"}'

Create a child key

curl https://api.proxy.gonka.gg/api/partner/children/<child-user-id>/keys \
  -H "Authorization: Bearer <jwt-token>" \
  -H "Content-Type: application/json" \
  -d '{"name":"Production key"}'

Child keys call the normal /v1/chat/completions endpoint.

Referral links

Share https://proxy.gonka.gg/register?ref=YOUR_CODE or the short /r/YOUR_CODE. Attribution is first-touch. See Marketing.