Look up every limit in one place — what uses credits and roughly how many, what is free, and the caps on cloud time, previews, Workers, public Experts, uploads and Publish.

On this page

This page lists what uses credits and every limit you can reach, with the default values. Use it to estimate a job before you start, or to understand why something stopped. Prices of plans and credit packs are on Plans and billing; how the balance works is on Credits and usage.

How credits are priced#

Credits pay for what the work actually uses: the AI models it calls, and time on a cloud machine. 100 credits = $1. Work is never charged for a failed machine start, and things marked Free below never use credits.

What uses credits#

Work What you pay for Typical amount
An answer in Ask The model's reading and writing. Depends on the question and the sources read; a Quick answer uses fewer, a deep dive more.
A Code thread on your computer The model only. Your computer does the running. Depends on the size of the change.
A Code thread in Ysra's cloud The model, plus the cloud machine while it runs. Machine: about 41 credits an hour (standard), about 67 an hour (large).
A Mayz review The model reading and checking the code. Usually 100–300 credits; a review on its own stops at 300.
A check inside a Code thread The same, as part of the thread. Counted in the thread's credits.
A Worker run The model, and any tools it uses. Capped at 200 credits a run (see Workers).
A public Expert's answer The model, paid by the Expert's owner. Depends on the question; capped by the Expert's limits.
Voice The model listening and speaking. About 12 credits a minute (4 with the economy voice).
Dictation (speech to text in the message box) Transcription. Under 1 credit a minute.
Images made in a Code task The image model. Up to 6 images per task.

See it before it runs

Paid work in a Code thread shows its plan first; Mayz and voice say what they usually cost before they start. After a run, the Usage page shows what each thread, Worker and Expert used.

Free#

What Limit
Set up with Ysra 3 setups a day
Help questions (the ? in the app) 20 a day
Trial credits for a new account 500 credits, once, when you confirm your email
Publishing and deploying No fee of their own: only the model and machine time behind them

When credits run out#

What happens Detail
New paid work doesn't start The message is "The credits ran out. Add credits, or wait for the plan's monthly refill."
A Code task already running pauses Before its next paid step. Its changes and what it checked are kept: add credits, then tell Ysra to continue.
A public Expert rests Visitors see that it is resting until credits come back.
Low-credit warning When 10% of the plan's credits or less are left.
YOUR WORK YOUR CREDITS Work uses credits threads, Workers, Machines, Ask Credits run low a warning at 10% or less left Credits run out Ysra pauses before its next step your changes are saved Credits are added plan refill, a credit pack, or an automatic top-up You say continue the work picks up where it paused 1 2 3 4 5
Running work pauses before its next paid step; nothing done is lost.

Cloud machines#

Limit Starter Pro Max Team (per seat)
Machine sizes Standard Standard, Large Standard, Large Standard, Large
Cloud threads running at once 1 2 4 2
Longest single task 1 hour 2 hours 4 hours 2 hours
Cloud hours a month 20 80 250 40
Machine starts an hour 6 15 30 15
Machine Size
Standard 4 vCPU, 8 GB memory
Large 8 vCPU, 8 GB memory
Rule Value
Internet access from the machine Only your code host and the package registries the project uses (npm, PyPI, Go, crates, RubyGems, Packagist, Maven)
A paused machine Deleted after 24 hours once its tasks have ended; the saved files stay, and the next turn starts a fresh machine
When the cloud is busy The thread waits for a machine, and says so if none frees up
Each thread, each day Daily limits on machine time and cloud compute, counted over the last 24 hours. A thread that reaches one stops and says so; see Daily limits per thread
When your credit runs out Running cloud work stops, keeping the work and the saved files

Code threads#

Limit Value
Longest a task runs 4 hours (less on cloud plans: see above)
Code threads you can start 30 an hour

Previews#

Limit Value
A preview stops when nobody looks at it After 15 minutes
Longest a preview stays up The plan's longest task (at least 10 minutes)

Workers#

Limit Value
Most often a Worker can run Every minute (every 5 minutes when made from Ask)
Spend per run 200 credits
Spend per Worker per day 1,000 credits (midnight UTC)
An approval waits 7 days, then it expires
Retries after a failed run None: Run now tries again
Time zone The one chosen on the Worker; UTC if none

Public Experts#

Limit Default Can be set to
Questions per visitor per hour 10 1 to 60
Questions per day, all visitors 200 1 to 5,000
Credits per month No ceiling Any ceiling
Files it may read — Up to 50
Websites it may sit on — Up to 10
Length of a question 2,000 characters —
Conversation kept The last 60 turns —

When a limit is reached, or the owner is out of credits, visitors see that the Expert is resting. Ysra can also switch a link off for misuse; only Ysra support can turn it back on.

Ask#

A Quick answer reads a few sources; a Thorough answer or a deep dive reads many more, and uses more credits. When the speed is Auto, a question that needs more than a Quick answer gets a Thorough one. See Auto, Quick or Thorough.

Uploads and the Library#

Limit Value
One file 100 MB
File types PDF, Word (.docx), Markdown, text, Excel (.xlsx), CSV/TSV, PowerPoint (.pptx), HTML, JSON, RTF; images PNG, JPG, WebP, GIF
Older Office files (.doc, .xls, .ppt) Refused: save them in the newer format first
Pages in one PDF 2,000 (300 scanned)
Scanned pages and pictures read 3,000 a day per person

Publish#

Limit Value
Size of one site 50 MB
Published sites per person 10
Files Pages, styles, scripts, images, fonts, video, PDF. Server code is refused: it needs Deploy.
YsraDocs