Choose the AI route that fits your ideas.
Two ways to reach AI
Where supported by your application, you can use your own external provider API key or choose Anumys (credits). A plugin licence, an external API account and an Anumys credit balance serve different purposes.
- Your own provider key: create an API account with a provider supported by your application, enable its API billing as required, and enter its key in the application's API settings. That provider bills the requests.
- Anumys credits: Anumys handles the configured AI providers. Your application uses an Anumys API key and the approved machine's credentials, and requests spend credits from your account.
Use only models offered by your current application's provider list. Anumys's available models, effort levels and credit prices come from the service catalogue; they are not a fixed list in this guide.
Set up Anumys credits
You need an Anumys account to use credits - but no product licence. Credits belong to the account of the e-mail address used at payment, and every Anumys application with Anumys AI can spend them. If you bought credits without registering, the account already exists for that e-mail but has no password yet: open Set or reset password?, enter the e-mail you paid with and set a password. Until then the credits cannot be used. Always sign in with the same e-mail you paid with.
- Purchase a credit package for the required category. Once processed, it adds credits to that category's existing account balance.
- In a compatible application, open its Anumys AI settings and identify your Anumys account: sign in with your e-mail and password, use the Google / X / Amazon / GitHub buttons if your account has no password, or let an activated product licence identify it.
- Register the computer. When you are signed in in the application or identified by your licence, the computer is approved automatically. If it still waits for approval, open Account, select AI credits & history and compare the machine ID and key fingerprint with the application before approving it.
- Create an API key for that approved machine and the chosen credit category. Compatible clients can create it from the application; the account page also offers key creation.
- Select Anumys as the AI provider, then choose an available model and effort level. Check the displayed cost and balance before sending.
A key is bound to one approved machine and one credit category. Copying the API key to another computer is not sufficient to use it: the registered machine's private key is also required. Create and approve that computer separately.
Usage or Usage + Limitless?
| Category | What it provides |
|---|---|
| Usage | Pays for AI requests. The application's free-mode limits still apply unless you also have its licence. |
| Usage + Limitless | Pays for AI requests and supplies a verifiable entitlement for the resulting output. A compatible client can treat those results as exempt from its relevant free-mode limits. |
Limitless is not an unlimited balance or a permanent licence for every product. The application must support the entitlement; other operations and ordinary free-mode output can still be limited. The two categories have separate balances and pricing.
Pick a model for the job
| Your goal | A useful starting point |
|---|---|
| Quick ideas and lightweight helper tasks | A fast, lower-cost model with Low effort. Try a short, clearly described request first. |
| A more developed idea | A capable general-purpose model with Middle effort, then refine the result. |
| Complex structure or several constraints | A stronger reasoning model or High effort when the current model supports it and the added time and cost are worthwhile. |
These are starting points, not guarantees of musical quality. Clear instructions and checking the result matter. MidAI distinguishes a main generation model from a fast helper model where that provider configuration offers both.
With a direct provider key, greater reasoning effort can increase token use and latency. With Anumys, each model/category/effort combination has its own listed credit price. Refresh the catalogue rather than assuming a provider's token price equals an Anumys credit price. Background checks and enhancements can be additional requests.
Read more: OpenAI reasoning guidance and Anthropic model selection.
Credit prices can change. The number of Anumys credits required per request is not fixed and may increase or decrease when AI providers change their prices or models. Buying a credit pack does not lock in per-request prices or guarantee a fixed number of generations. Check the latest model and effort pricing before submitting a request.
Follow your balance and protect your keys
Credits are reserved while a request is being processed and charged on a successful answer. Failed requests release their reservation; pending or uncertain requests can need time to settle. A successful answer that does not suit your taste is still a successful AI response.
Account > AI credits & history shows requests, models and costs. Stored question/answer content is retained for up to 30 days; the usage and accounting history is separate. Revoke a lost machine or leaked Anumys key in your account. Revoke an external key at its provider. Never paste passwords, API keys or licence keys into support chat.