Skip to content

Quotas, fair use and bot protection

What gets counted depends on whether you are signed in — and creating invoices is the exception: without signing in it is not counted at all.

Situation What counts
Anonymous a fair-use limit per client address: 20 operations per hour, 50 per day. Not tracked per tool — whoever alternates between validating and converting is doing the same thing as far as the same machine is concerned
With an account the tool quota of the plan, tracked per tool (Free: 50 per month and tool)
Create anonymously not counted at all; with an account it counts against the invoice quota (Free: 10 per month), not against the tool quota

It names the limit that was hit:

  • anonymous: the hourly or daily limit along with when it resets — “Things continue from the next full hour.” — and a pointer to the API
  • with an account: the monthly quota — “… it resets at the start of the month.”

Anonymously, a pointer to the API appears from the eighth operation within an hour. It blocks nothing.

None of this applies in an Enterprise installation

Section titled “None of this applies in an Enterprise installation”

There the plan limits do not apply at all. The counters keep running so that an administrator can see consumption — but they limit nothing.

A batch books its quota up front, and in full

Section titled “A batch books its quota up front, and in full”

Every file in a batch counts as one tool call against the monthly quota. If the whole batch no longer fits, it does not start at all — rather than running halfway and then aborting. See Batch processing.

Every tool form carries a hidden honeypot field and a signed timing trap with a minimum dwell time of one second. If it triggers, the answer reads: “The request could not be processed. Please try again.”

Invoices, tool calls, seats, formats, API keys and batch sizes per plan are under Plan, quotas and the format gate.