Skip to content

Update from code changes: AI Collection Creator tier limits #397

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yash-pouranik merged 1 commit into from
Aug 23, 2026
Merged

Update from code changes: AI Collection Creator tier limits #397

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions mintlify/docs/guides/ai-byok.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,14 +28,18 @@ If a BYOK key is used, no urBackend-side session cap applies. Groq's own rate li

## Plan-tier behavior

| Plan | Personal Groq key allowed? | Platform-key AI sessions per month |
| :--- | :--- | :--- |
| Free | Yes | 5 |
| Pro | Yes | 20 |
The AI Query Builder and the AI Collection Creator (Schema Design) each have their own monthly counter on the platform key:

| Plan | Personal Groq key allowed? | Query Builder requests per month | Collection Creator schema designs per month |
| :--- | :--- | :--- | :--- |
| Free | Yes | 5 | 1 |
| Pro | Yes | 20 | 5 |

Monthly counters reset on the first of each calendar month (UTC).

The monthly counter resets on the first of each calendar month (UTC).
Collection Creator chat sessions that use the platform key are also capped at **20 iterations per session**. BYOK requests are not subject to this per-session cap.

Once your plan's platform-key cap is reached, further AI requests return `403 Forbidden` until either the counter resets or you configure a BYOK key.
Once your plan's platform-key cap (monthly or per-session) is reached, further AI requests return `403 Forbidden` until either the counter resets or you configure a BYOK key.

## Get a Groq API key

Expand Down
19 changes: 15 additions & 4 deletions mintlify/docs/limits-and-quotas.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,16 +33,27 @@ When your project approaches the database quota, writes may be rejected with `40

## AI session limits

AI features (like the AI Query Builder) that use urBackend's platform Groq key are capped per account, per calendar month:
AI features that use urBackend's platform Groq key are capped per account, per calendar month. The AI Query Builder and the AI Collection Creator (Schema Design) each have their own separate monthly counter.

| Plan | AI sessions per month (platform key) |
### AI Query Builder

| Plan | Query Builder requests per month (platform key) |
| :--- | :--- |
| Free | 5 |
| Pro | 20 |

Requests beyond the monthly cap return `403 Forbidden` until the counter resets on the first of the next calendar month (UTC).
### AI Collection Creator (Schema Design)

| Plan | Schema designs per month (platform key) |
| :--- | :--- |
| Free | 1 |
| Pro | 5 |

In addition to the monthly cap, each Collection Creator chat session using the platform key is limited to **20 iterations** (turns) before you must start a new session. This per-session cap protects platform resources against long, runaway conversations.

Requests beyond either the monthly cap or the per-session iteration cap return `403 Forbidden`. Monthly counters reset on the first of the next calendar month (UTC).

To bypass this cap, configure a personal Groq API key at the developer or project level. Requests that resolve to a BYOK key are not counted against the platform cap. See [BYOK for AI](/guides/ai-byok).
To bypass both the monthly cap and the per-session iteration cap, configure a personal Groq API key at the developer or project level. Requests that resolve to a BYOK key are not counted against any platform cap. See [BYOK for AI](/guides/ai-byok).

## HTTP status codes

Expand Down
Loading