Window

fastCRW cloud uses a per 60-second sliding window for API-key rate limiting. The window slides continuously — it counts requests in the last 60 seconds from the current moment, not fixed calendar minutes.

That means a burst at 12:00:20 still affects what you can send at 12:01:00. Think in rolling windows, not top-of-minute resets.

Current per-plan limits

Plan	Requests / minute
FREE	10
HOBBY	30
STANDARD	200
GROWTH	400
SCALE	600

Headers

Retry-After
X-RateLimit-Limit
X-RateLimit-Remaining

When you receive a 429, back off for the number of seconds specified in Retry-After before retrying. Sending requests during the backoff period will not reset the window but will be rejected.

Practical Client Behavior

A well-behaved client should:

read X-RateLimit-Remaining on every response,
reduce concurrency before it reaches zero,
and honor Retry-After exactly when a 429 arrives.

If you are running many workers in parallel, centralize throttling instead of letting each worker discover the limit independently.

Rate Limits vs Target Limits

The fastCRW API rate limit is separate from the target website's own rate limit.

fastCRW may return 429 because your API key exceeded plan limits,
or the target site may return 429, which appears in metadata.statusCode or as a warning.

Those are different problems and should be handled differently.