Skip to content

Sprites account and token ​

kaxa talks to Sprites with a bearer token. The token lives in the environment. kaxa does not read sprite login or ~/.sprites/sprites.json.

Create an account ​

Sprites uses a Fly.io account.

  1. Open sprites.dev and sign in with Fly.io, or use the Sprites signup.
  2. Finish account setup in the browser. A new organization can create sprites for testing.

The upstream sprite CLI is optional. Its login flow is documented in Sprites authentication. That login does not configure kaxa.

Create a token ​

  1. Open sprites.dev/account.
  2. Create an API token.
  3. Copy the value the page shows. Treat that string as a secret.

Do not commit the token, put it in a flag, or paste it into an issue or pull request.

Configure kaxa ​

bash
export KAXA_SPRITES_TOKEN='paste-the-dashboard-value'
export KAXA_DEFAULT_PROVIDER=sprites

KAXA_DEFAULT_PROVIDER is optional. You can pass --provider sprites on each command instead.

Check that the token works:

bash
kaxa list

An empty account prints no sandboxes created. A rejected token prints an error and does not create anything.

Command manuals are in the docs index.