Repository navigation
docs(gaps): document recent API, SDK and CLI changes - #1755
Open
mintlify[bot] wants to merge 2 commits into
Open
mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
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
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.
Rolling PR for API, SDK and CLI changes that shipped without docs. #1754 already lists eight source PRs, so new gaps start here.
sdks/go.mdx: the Go batch scrape section did not show failed URLs. It now coversjob.ID,job.Errorsandjob.RobotsBlockedfromBatchScrape, and the newGetBatchScrapeErrorsmethod. Based on feat(go-sdk): expose batch scrape errors and job ID from BatchScrape, @Chadha93.billing.mdx: the page said refused requests return 402 but not how to tell a short team balance from a per-key spend limit. It now documents thecodefield (insufficient_creditswith an example body,api_key_spend_limitwith itslimitobject, and a one-line mention ofmcp_credits_exhausted). Based on fix(api): name the limit that refused a request in the 402 body, @Chadha93.Needs a human look: the
errorstring in theinsufficient_creditsexample is shortened with "..." because the full message was not visible in the source diff.