AI plans per member
With AI plans, each member of the organization gets a plan with a fixed monthly price and their own API key. The key works in any OpenAI-compatible client, such as the official SDK and opencode, with every model in the catalog and no per-token charges.
If you would rather pay for the tokens you use, with no monthly fee, use on-demand AI.
Plans and prices
| Plan | Price per member | Usage |
|---|---|---|
| Lite | R$ 20.00/month | Usage that resets every 5 hours and every week |
| Standard (recommended) | R$ 71.90/month | 4x the usage of Lite, reset every 5 hours and every week |
| Premium | R$ 323.90/month | No 5-hour limit: 5x the usage of Standard, reset every week |
Every plan includes:
- every model in the Zenifra catalog;
- the member's own API key;
- compatibility with the OpenAI SDK and tools like opencode;
- a fixed price in reais, with no per-token charges;
- tracking of each member's usage and the request history of the last 30 days;
- changing plans at any time.
How the limits work
Each plan has two usage windows:
- 5-hour window: resets at fixed times of the day. A full 5-hour window is worth a quarter of the week, so four full windows use the whole week.
- Weekly window: resets once a week.
Premium has no 5-hour window: the whole week can be used at any pace.
The console shows the usage of each window as a percentage and when it resets, for example "42.5% used · resets at 2:30 PM". When a window reaches 100%, the key pauses until it resets, with no extra charges. Meanwhile, requests answer with status 429.
Assign a plan to a member
Plans are assigned by the organization owner or by a member with the Manage AI seats permission.
- In the console, open AI Models and, under Plans, the Seats tab.
- Click Assign on the plan card (for example, Assign Standard) or Assign seat.
- Select the member and confirm.
Each member can have one plan per organization. The same person can have plans in different organizations; each organization pays for its own. An organization with a pending payment cannot assign plans or upgrade until it settles.
Use the plan key
The member sees their own plan in AI Models > Plans > My plan:
- Show key and Hide key show and hide the key in its field, which stays masked with asterisks while hidden;
- Copy key copies the key without showing it;
- the base URL is
https://ai.zenifra.com/v1; - the request example is available in curl, Node.js, Python, Go and PHP, with a Copy code button.
The key starts with zai_ and belongs to the member alone. Treat it like a password: every use made with it counts toward the plan.
curl https://ai.zenifra.com/v1/chat/completions \
-H "Authorization: Bearer $ZENIFRA_AI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "zenifra/qwen3.8-flash", "messages": [{"role": "user", "content": "Hello!"}]}'To use it in OpenCode, see Use Zenifra AI in OpenCode.
Generate a new key
In My plan, Generate new key replaces the plan key. The current key stops working right away, so replace it in the tools that use it. Window usage and request history carry on: a new key never resets the limits.
Track usage and requests
In My plan, the member sees:
- the usage of each window and when it resets;
- the last use of the key: when, from which IP and from which client;
- Recent requests: the requests of the last 30 days, newest first, 30 at a time. Load more brings the older ones.
In the Seats tab, whoever manages the plans sees each member's usage and last use and opens each member's request history.
Each request records when it happened, the method, the route, the model, the status, the duration, the IP, the client and the input and output tokens. The content of messages and responses is never stored. Records are kept for 6 months, as required by Brazil's Marco Civil da Internet; the console shows the last 30 days.
Billing
The plan goes on the organization's cycle invoice, the same one as hosting. Nothing is charged when a plan is assigned or changed: everything shows on the invoice when the cycle closes. Amounts are prorated by time and exact, never rounded up.
Subscribing mid-cycle
You pay only for the time left until the cycle closes: plan price × time left ÷ cycle length. From the next cycle on, the price is full.
Example: the cycle runs from Nov 5 to Dec 5 (30 days) and a Standard plan (R$ 71.90) is assigned on Nov 20. With 15 days left, the first cycle charges 71.90 × 15/30 = R$ 35.95.
Upgrade
The pricier plan takes effect right away, with its limits. On the invoice, each stretch of the cycle pays the plan in effect during it.
Example, in the same 30-day cycle, upgrading from Standard to Premium on Nov 20:
| Stretch | Plan | Amount |
|---|---|---|
| Nov 5 to Nov 20 (15 days) | Standard | 71.90 × 15/30 = R$ 35.95 |
| Nov 20 to Dec 5 (15 days) | Premium | 323.90 × 15/30 = R$ 161.95 |
| Cycle total | R$ 197.90 |
Downgrade
A cheaper plan only takes effect from the next billing. Until then, the current plan and its limits stay, and the cycle is billed at the current plan. The console warns before confirming and shows both plans until the cycle turns, for example "Standard until the next billing. From 12/05/2026: Lite.". Choosing the current plan again cancels the change.
Yearly plan
When assigning a plan, choose Monthly or Yearly. On the yearly plan you pay 11 months and use 12: Lite R$ 220.00, Standard R$ 790.90 and Premium R$ 3,562.90 per year. Usage limits are the same as the monthly plan.
The whole year goes at once on the organization's next invoice, like projects on a yearly contract, and lasts 12 months from the assignment. At renewal, a year later, the next year goes on the invoice the same way. In the Seats tab, the console shows when each yearly plan renews.
- Upgrade: takes effect right away and bills the difference in the yearly price prorated to the rest of the year. Example: a yearly Standard upgraded to Premium halfway through the year pays (R$ 3,562.90 − R$ 790.90) × 1/2 = R$ 1,386.00.
- Downgrade: the current plan stays until the yearly renewal, and the next year is billed at the cheaper plan.
- Removal: the key stops working right away, with no refund of the paid year.
Remove a plan
The key stops working right away. The current cycle is billed to its end, with no refund.
If the same member gets a plan again in the same cycle, it starts a new plan with its usage windows reset. That is why both plans are billed for the stretch where they overlap.
Plans or on-demand AI
| AI plans | On-demand AI | |
|---|---|---|
| Price | Fixed per member, per month | Per million tokens used |
| Key | One per member, tied to the plan | Organization keys, as many as you need |
| Limit | 5-hour and weekly windows (Premium weekly only) | Daily and monthly quotas you set per key |
| Payment | Organization cycle invoice | Organization credit, via PIX or boleto |
Plans suit people who use AI every day, as in coding tools. On-demand AI suits integrations in applications, where volume varies.
Last updated on
AI on Zenifra
Zenifra AI: OpenAI-compatible API, public model catalog with BRL prices, keys with daily and monthly quotas, prepaid credit and usage tracking in the console.
Use Zenifra AI in OpenCode
Use Zenifra AI in OpenCode with the official plugin: install it, connect your plan or on-demand key, pick a model and learn how the key usage limits work.