docs: fix integration examples, billing guidance, and stale AI exports - #261
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
1 issue found and verified against the latest diff
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="docs/cloud/guides/concurrency.mdx">
<violation number="1" location="docs/cloud/guides/concurrency.mdx:26">
P2: The field table documents `apiKeyId`, `concurrentSessionLimit`, and `activeSessionCount` on `GET /api/v2/billing/account`, but the checked-in `AccountView` schema in `cloud/openapi/v2.json` does not define any of those fields (only `projectId`, `totalCreditsBalanceUsd`, `rateLimit`, `planInfo`, and a few others). If the deployed response matches the spec, readers will look for fields that never appear. Verify these fields against the real endpoint and either confirm they exist or correct the table; if they are not yet deployed, do not document them as present.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Fix all with cubic | Re-trigger cubic
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.
Fix the n8n authentication/header and V3 event examples, the Grow Therapy cache markers and cost claims, and webhook verification against the deployed Python signer. Remove the incompatible JavaScript verifier and provide a tested Python/FastAPI receiver with the exact serialization contract.
Add concurrency and billing guides covering preserved maximum legacy/spend-tier grants, project capacity, polling, queues, browser cleanup, PAYG/BYOK costs, credits, auto recharge, and soft spending caps. Remove subscription-only BYOK wording.
Replace six stale checked-in AI bundles with Mintlify-managed
llms.txtandllms-full.txt. Put shared guidance inmarkdown.instructions, update recommended links, turn the former scoped exports into small compatibility indexes, and redirect retired Bux routes. Most deleted lines are duplicated generated bundles; the source pages remain.Validation: Mintlify build and broken-links checks passed; 13 changed Python/JSON snippets parse; the actual initial/rerun task expressions produce the same cache template. The documented webhook verifier passes synthetic fixtures generated by the deployed sender at
fdcfb4204e8e4bc58dff8870c2f230ffcedd07a9, including Unicode, numeric keys/floats, tampering, and malformed headers. No billable agent runs were needed. Mintlify preview verified automatic root exports and the new guide content. Its static asset handler bypasses page redirects for.txt, so scoped URLs use compatibility indexes instead. Public exports, pointers, and Bux redirects will also be checked after deployment.The cache marker correction overlaps the tutorial portion of #157; that older PR also contains SDK changes and was not merged wholesale. Production API schema refresh is separate.