Resource limits
To keep the database responsive for everyone, each connection has a small budget of work per 30-minute window. Normal browsing and lookups never come close; the budgets only stop sustained automated abuse. When a budget is used up, requests are declined until the window resets.
How many brand-new numbers you have added to the database this window. A huge run of these is the usual sign of abuse. Factors you report for numbers that already exist, and the terms the server computes while extending a sequence, are NOT counted here; only genuinely new numbers are.
Total time the server spent on your requests this window. A few very expensive requests (huge factorizations, deep sequences) use this up faster than many cheap ones.
Volume of data the server has sent you this window. Downloading many large factorizations, full decimal expansions or sequences adds up here.
Server time spent on primality proofs you queued for large numbers. Proving a big number by an N-1 / N+1 / combined test runs in the background, and its cost is charged here rather than to your processing time.
Budgets reset in 29 min 34 s.
From the command linefdb · curl
fdb quota
curl -s 'https://factordb.com:4059/rpc' -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"quota_status","params":{}}'