Documentation Index
Fetch the complete documentation index at: https://zite.com/llms.txt
Use this file to discover all available pages before exploring further.
What uses credits
Credits power the usage-based features in your Zite workspace: building and modifying apps with AI, the database agent, AI fields in databases, and sending emails from your apps.| Feature | Credit usage |
|---|---|
| Building with AI in Chat, Plan, or Build mode | Varies by request complexity |
| Using the Database Agent | Varies by request complexity |
| AI fields in databases | Varies by generation |
| Apps using AI with the Zite API key | Varies by AI usage |
| Sending emails from your published apps | 1 credit per email |
| Generating documents | Coming soon: 5 credits per document |
Database syncs and app agents may use credits in the future. We will update this guide before those features start consuming credits.
What does not use credits
Some actions do not consume credits:- Manual edits, such as changing text, colors, spacing, or layout directly
- Applying a theme from the design panel
- Zite Database storage and standard database operations
- Users visiting your published apps
- Workflows and emails run from the editor
- Fixing app errors with
Fix it for me
How building uses credits
When you build with AI, the number of credits used depends on how much work Zite needs to do. Simple edits usually use fewer credits, while broad changes, new screens, databases, workflows, or advanced logic use more. Credit usage can depend on:- The complexity of your prompt
- The model used
- The size of your app
- How many files, screens, or database tables Zite needs to inspect
- How many changes Zite needs to make
| Sample request | What it does | Credit estimate |
|---|---|---|
| Edit colors, spacing, or font | Small visual or style updates | 0.5 - 0.7 |
| Reposition elements | Moves or resizes components within a screen | 0.6 - 1.0 |
| Change navigation or page branching | Updates flow between screens | 1.0 - 1.5 |
| Add a new page or view | Creates a new screen with elements | 1.5 - 2.25 |
| Modify app layout | Updates structure across a screen | 1.5 - 2.5 |
| Create a database | Sets up a database with tables and fields | 2.0 - 3.0 |
| Change design from an uploaded photo | Analyzes a photo and updates app styling | 2.0 - 3.5 |
| Add user authentication | Creates flows, logic, and UI | 2.5 - 3.5 |
Check credit usage
You can check how many credits a request used by clicking on a message.
View app usage underneath the message details.
How credits reset
Credits reset at the start of each billing cycle. Unused monthly credits do not roll over. If you upgrade to a higher plan during a billing cycle, your total credit limit is set to the new plan’s limit for that cycle.Workflow runs are tracked separately
Running workflows from your published apps—to read and write data, connect to integrations, and call third-party APIs—is metered through workflow runs, not credits. Each plan includes a monthly workflow run allowance alongside its credit allowance. Learn more in Workflow runs and your monthly limit.Add more credits
If you need more credits, you can upgrade your Apps plan. Higher plans include higher monthly credit limits.Free plan limits
The Free plan includes a monthly credit allowance and a daily message limit. Paid plans include higher monthly credit limits and unlimited daily messages.Downgrading after deployment
If you upgrade to a paid plan to create an app and then downgrade after your app is fully built and published:- Zite will continue to host your app on the Free plan as long as you’re not using a custom domain.
- The app creator and app users can still access the app free of charge.
- Zite branding will reappear if you go back to the Free Zite plan.