grepticon/

Limits

Plan quotas and read rate limits — what the free and Pro plans allow, and how 429s work.

Grepticon enforces two kinds of limit: quotas (how much you can store) and rate limits (how fast you can read). Quotas are checked when you create a workspace or upload a file — never on the read path — so reads stay fast and predictable. Rate limits guard the read path.

Plan quotas

LimitFreePro
Workspaces per account3100
Account storage500 MiB5 GiB
Max file size50 MiB50 MiB
Files per workspace25,00025,000

Exceeding a quota fails the write with an actionable message (for example, creating a 4th workspace on the free plan), never a silent drop. The free plan needs no card and is enough to build and evaluate against the hosted stack.

Read rate limits

Reads are rate-limited on two windows at once — per credential and per account:

WindowFreePro
Reads per credential60 / minute600 / minute
Reads per account300 / minute3,000 / minute

The per-credential window keeps a single runaway agent from starving the rest; the per-account window is the aggregate ceiling across every credential you hold.

When you cross a window, the request returns 429 Too Many Requests with a Retry-After header naming how long to wait. The SDK handles this for you: it retries a 429 up to twice, honoring Retry-After (bounded to a sane 1–10 second wait) before surfacing the error. Bursty agent traffic mostly rides through without your code doing anything.

Only the four read tools (ls / find / cat / grep) count against these windows. Management operations — creating workspaces, uploading files, minting tokens — are not on the read path.

Upgrading

Higher quotas and rate limits come with the Pro plan. Manage your plan and billing in the console under Billing — upgrading lifts the caps on your existing account without any migration.

Where to go next

  • Quickstart — everything below runs comfortably on the free plan.
  • Support — need a limit raised beyond Pro, or hit something unexpected? Get in touch.

On this page