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 22 min 25 s.
Rules for automated requests
- Keep to a few requests per second and at most 3 at the same time. On a refusal (
429), pause before retrying; repeated refusals block your address for an hour. - Don't spread requests over many addresses or accounts to stay under the limits. Such traffic is blocked without notice.
- Use the RPC endpoint if possible (
https://factordb.com:4059/rpc, see the API page, or thefdbcommand-line tool). The web pages wrap the same data in HTML and cost more. The oldreportfactor.phpandapi.phpkeep working. - Don't walk through ids or pages one by one. For lists of composites, PRPs or cofactors, use the Download page or the
downloadRPC. - Use your tool's own User-Agent (e.g.
mytool/1.0). Requests posing as a browser are refused. - New numbers: only numbers others may look up as well. Every id is stored permanently. Not wanted: bulk runs such as b^n-k for every k. Your current budget is shown above.
- Factors for existing numbers and sequence extensions are always welcome and don't count toward the new-number budget (processing time still does). Small factors are found automatically.
- Need higher limits? Email me with your account name and what it's for. Your script then sends its API token in the
X-Fdb-User-Tokenheader (over HTTPS) so the higher limits apply.
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":{}}'