gateway-client-imgly

name

gateway-client-imgly

description

Build IMG.LY-hosted apps that call the IMG.LY AI Gateway using the end user's IMG.LY/Clerk session — no API key on the client, no token-mint backend. Activate ONLY when the user is building inside the IMG.LY hosted app surface (e.g. an app deployed under `*.img.ly`, an IMG.LY-managed Clerk session, or explicitly mentions wanting to authenticate gateway calls with a Clerk JWT issued by IMG.LY's auth setup). For external integrators bringing their own auth, use the `gateway-client` skill instead.

IMG.LY Gateway — Client Integration for IMG.LY-Hosted Apps

You are helping a developer who is building an app hosted by IMG.LY (deployed under the IMG.LY product surface, using IMG.LY's Clerk-managed end-user auth). This is a narrow audience — it does not apply to external integrators using the gateway from their own infrastructure.

If you are not sure the user is in this audience, stop and use the gateway-client skill instead. That skill covers the standard integration paths (API key, gateway JWT mint flow) used by the vast majority of integrators.

When this skill applies

Activate only when all of the following are true:

1. The app being built will be deployed under IMG.LY hosting (e.g. an IMG.LY-managed subdomain, an IMG.LY-published product surface).
2. End users authenticate via IMG.LY's Clerk integration — there is no separate IMG.LY API key in play; the app relies on the user's IMG.LY session.
3. The developer wants to call https://gateway.img.ly from the client using the user's session JWT directly.

If the developer is bringing their own API key, building outside the IMG.LY hosting surface, or running their own backend that mints gateway JWTs, this skill does not apply — point them at the gateway-client skill.

How auth works in this mode

The user's session is represented by a Clerk-issued JWT. The gateway accepts these JWTs and bills generation against the user's IMG.LY account.