Skip to content

Handle social research rate limits

Distinguish account request limits from source availability and collection credit, and recover without duplicate work or uncontrolled retries.

Guides

Should you wait, narrow the task or stop?

A rate limit is not the same as an empty source, exhausted collection budget or failed authentication. Each state calls for a different recovery path. Read the actual response before retrying, and keep the same task boundaries so a temporary limit does not produce a larger or less trustworthy dataset.

Bounded recovery prompt
If this research is rate limited, report the returned retry guidance and wait accordingly. Preserve request keys and cursors, inspect pending work before repeating effects, and distinguish request limits from collection credit or unavailable sources. Do not loop indefinitely or change plans.
01 / Guides

Classify the returned condition

Check the documented error and response metadata. A rate_limited response concerns the account's request allowance; source_unavailable means availability could not be established. Authentication failures need the client's supported sign-in recovery. Do not treat every error as a reason to retry immediately or substitute another data source without disclosing the change.

02 / Guides

Honor the returned retry guidance

For a rate-limited response, wait for the supplied Retry-After interval rather than launching parallel retries. The account allowance is shared across agents, keys and the app, so another window is not a separate quota. A bounded retry policy should stop and report a persistent failure instead of consuming repeated calls indefinitely.

03 / Guides

Preserve operation and result identity

When retrying a supported write, keep the original request key so one intended effect is not started twice. For result continuation, use the returned cursor with its original query rather than restarting discovery. Unknown or pending outcomes need status inspection before another effect. Do not interpret a delayed response as proof that nothing happened.

04 / Guides

Separate credit from request pacing

Inspect workspace budget and plan information before choosing more collection. Waiting does not replenish paid collection credit, and remaining credit does not remove a per-minute request limit. Report the actual blocker with any useful partial evidence retained. Never enable automatic recharge, change plans or broaden the task as an invisible recovery step.

Keep the boundaries clear.

  • Account request allowance is shared by its connected clients.
  • Request pacing and collection credit are different constraints.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage