Usage limits

• Daily AI request count.
• Daily credit allowance.
• Weekly credit allowance.
• Monthly credit allowance.
• Workspace count, per plan.
• Provider-side quotas that are outside OpenbirdAI's control.

The usage summary in the plans area and the error returned with a refused request both name the limit. The most common cases are the daily request count at the start of heavy use and the monthly credit allowance late in a period.

Connected providers impose their own quotas. A provider quota can block a request that OpenbirdAI would otherwise allow, and no OpenbirdAI plan change removes it. When that happens, the error identifies the provider.

• Batch related questions into fewer, broader prompts when the breadth is genuinely useful.
• Use a new conversation instead of a long one to reduce context cost.
• Schedule heavy analysis rather than running it repeatedly.
• Check the usage summary before starting an expensive Deep Strategy run.

Upgrading takes effect for subsequent requests; it does not retroactively refund credits already consumed. Downgrading restores Free behaviour, which can immediately make a previously available tier unavailable.

• A Deep Strategy run in progress finishes under the tier it started with.
• A request that needs a tier your new plan excludes is refused, not silently downgraded.
• Usage history remains readable either way, so reconciliation is unaffected.

Two different counters can stop you: how many requests you made, and how many credits they cost. A plan that raises one may not raise the other.

• Daily request count caps how often you can ask at all.
• Daily and monthly credits cap how much work those requests can do.
• A single expensive request can be refused while your balance still looks healthy.