Frequently Asked Questions
Professional guidance on models, credits, quality, privacy, and delivery workflows.
Getting Started
What can I create on AIBase?
AIBase provides image and video generation in one workspace. You can create visuals from text, transform existing images, and produce short-form AI videos with selected production-grade models.
Do I need design or prompt-engineering experience?
No. Beginners can start with plain-language prompts, while advanced users can add style, camera, and composition instructions for tighter control.
How do I choose the right model?
Use faster models for ideation and iteration, then switch to higher-quality models for final delivery. This workflow usually gives the best speed-to-quality ratio.
Credits and Billing
How are credits consumed?
Credits are deducted per generation task based on model and mode. More advanced models and longer video durations generally consume more credits.
What happens if a task fails?
If a task fails before valid output is produced, the platform follows model-provider billing rules and returns status details for troubleshooting.
Can teams manage usage predictably?
Yes. A common practice is to set internal generation guidelines by use case (draft, review, final) and assign model tiers per stage to control monthly spend.
Quality and Reliability
How can I improve output quality?
Use specific prompts with clear subject, scene, style, and constraints. For image-to-image, upload clean references and align aspect ratio with your target output.
Why does output differ from my expectation?
Model generation is probabilistic. Ambiguous prompts, conflicting instructions, or weak references can reduce consistency. Refine one variable at a time for stable improvements.
How long are generation links available?
Temporary provider links may expire. AIBase is designed to persist generated assets through configured storage workflows, so production teams can keep deliverables accessible.
Security and Data
Are my prompts and files protected?
AIBase uses authenticated API routes and server-side provider calls, which helps avoid exposing provider keys in the browser.
Where are generated assets stored?
Generated outputs can be stored in your configured object storage (for example Cloudflare R2), enabling persistent links and controlled delivery.