An app on ElliSekiz is an account plus the tokens and routing rules attached to it. There is no separate app registration step and no OAuth client to configure — you sign in, fund a balance, and mint a token.
Sign in at ellisekiz.ai/login with Google, Apple, Microsoft or GitHub. There is no password to manage and no separate developer account: the same identity owns the dashboard, the balance and the API.
Generations are prepaid. Add funds on the billing page — one-off top-ups or a monthly plan that credits your balance on each renewal. One dollar of balance is one dollar of provider spend; there is no markup and no credit abstraction.
402 with the shortfall, so a low-balance alarm is one status code away.Under account → routing you decide who picks the provider for a request that does not name one:
Any request may still override the account policy with a provider field. See routing and BYOK.
If you already have a fal.ai, Replicate, Atlas Cloud or OpenRouter key, store it under account → provider keys. Requests that can use your key are billed to your upstream account instead of your ElliSekiz balance — currently with no platform fee. Keys are encrypted at rest and never returned by the API.
curl https://ellisekiz.ai/api/v1/models \ -H "Authorization: Bearer esk_..."
Token creation is covered on the next page. One token per app or environment is a good habit: revoking a leaked staging token then costs you nothing in production.