Skip to main content

Credits and Generation

Learn how credits work in SpAItial.

How Credits Work

SpAItial uses a shared credit balance for the web app and Developer API:

  • 1 credit = $0.01
  • Free users receive a one-time 1,600 credit starter balance, enough for 10 Echo 2 - Standard generations
  • App users may receive a daily app-only free credit refill when enabled
  • Included subscription credits are used before purchased credits
  • Purchased credits are self-serve, can be custom amounts, and are shared across app and API usage

Model Pricing

ModelBest forTypical timeCredits
Echo 2 - StandardFast, general-purpose world generation~8 minutes160
Echo 2 (HQ)Higher-detail, higher-resolution worlds~60 minutes800

Plans

PlanIncluded creditsEcho 2 - Standard generationsEcho 2 (HQ) generationsAvailable featuresPrice
Free1,600 starter credits once10 once2 onceCore creation features, downloads, standard exports, and world editing. Collider mesh export is not included.$0
Standard2,400 credits/month153Everything in Free, plus collider mesh export.$24/month
Pro4,800 credits/month306Everything in Standard, with more included monthly credits.$48/month
Custom/EnterpriseCustom volumeCustom volumeCustom volumeEverything in Pro, with custom volume and support.Contact us

What Uses Credits

ActionEcho 2 - StandardEcho 2 (HQ)
Text-to-World160 credits800 credits
Image-to-World160 credits800 credits
Panorama-to-World160 credits800 credits
Developer API world generation160 credits800 credits

What Doesn't Count

  • Viewing worlds
  • Editing world details (title, description)
  • Sharing worlds
  • Downloading and standard exports

Exporting collider meshes is available on paid plans.

When You Need More Credits

If your balance is too low to generate:

  • Purchase credits from billing; custom amounts are supported
  • Upgrade to Standard, Pro, or Custom/Enterprise for monthly included credits
  • Submit a manual free credit request if you need help getting started

Tips for Managing Credits

  • Plan your generations thoughtfully
  • Review prompts before generating
  • Use edits efficiently when available
  • Keep enough purchased credits for API workloads that may run outside your normal app usage