Document API rate limits on Pricing & Limits page#315
Open
ulziibay-kernel wants to merge 1 commit intomainfrom
Open
Document API rate limits on Pricing & Limits page#315ulziibay-kernel wants to merge 1 commit intomainfrom
ulziibay-kernel wants to merge 1 commit intomainfrom
Conversation
Document per-plan rate limits (burst and sustained), list of rate-limited endpoints, and token bucket behavior. Made-with: Cursor
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Risk assessment: Very Low.
I based this on the actual diff only:
- Change scope is limited to a single docs page:
info/pricing.mdx - Edits are documentation content additions (rate limit table, endpoint list, explanatory text)
- No application/runtime code, configuration, infrastructure, auth, or permission logic changes
- Blast radius is limited to documentation rendering and reader guidance
Given the low complexity and non-executable surface area, this is safe to approve.
Sent by Cursor Automation: Assign PR reviewers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Companion to https://github.com/kernel/kernel/pull/1630 which adds rate limiting to process exec and invocation endpoints.
Test plan
Made with Cursor
Note
Low Risk
Low risk documentation-only change that adds clarity around rate limits without modifying runtime behavior.
Overview
Expands the Rate limiting section on the
Pricing & Limitspage to document per-plan API request limits, including burst vs sustained throughput (token bucket behavior).Adds a list of the specific rate-limited endpoints (browser creation, invocations, process exec/spawn, and Playwright execute) and clarifies expected
429handling/response headers.Written by Cursor Bugbot for commit 002e7c5. This will update automatically on new commits. Configure here.