Document reading ISP proxy static IP via ip_address - #499
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 95ec24e. Configure here.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
Stale comment
Risk assessment: Very Low
Verdict: Prior approval retained (no re-approval; risk did not increase)
Re-evaluation after synchronize
This PR was previously approved by this automation at commit
95ec24e. It has since been updated to3d88d589(absolute URLs for API reference links). Re-assessed the full diff againstmain.What changed
- Single file:
proxies/isp.mdx(+36 / −0)- Adds a documentation section on reading an ISP proxy’s static exit IP via
ip_address- Includes TypeScript, Python, and Go example snippets and links to existing API reference pages
Why Very Low
- Documentation-only change on a Mintlify docs page; no application, API, or infrastructure code modified
- No auth, permissions, billing, schema, or shared-service impact
- Small, easy-to-reason-about surface area with no production behavior change
- Follow-up commit only adjusts link form (absolute URLs); does not expand blast radius
- No CODEOWNERS requirement detected
Approval handling
- Risk remains Very Low after the update — approval is not dismissed
- PR is already approved by this automation — not re-approving
- Risk derived from the diff contents, not from PR description claims
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low
Verdict: Prior approval retained (no re-approval; risk did not increase)
Re-evaluation after synchronize
This PR was previously approved by this automation at commit 95ec24e. Head is now 96a9502 (merge of main into the feature branch). Re-assessed the full diff against main.
What changed (vs main)
- Single file:
proxies/isp.mdx(+36 / −0) - Adds a documentation section on reading an ISP proxy’s static exit IP via
ip_address - Includes TypeScript, Python, and Go example snippets and absolute links to existing API reference pages
Why Very Low
- Documentation-only change on a Mintlify docs page; no application, API, or infrastructure code modified
- No auth, permissions, billing, schema, or shared-service impact
- Small, easy-to-reason-about surface area with no production behavior change
- Merge-from-main update does not expand this PR’s blast radius relative to
main(still the same docs-only diff) - No CODEOWNERS requirement detected
Approval handling
- Risk remains Very Low after the update — approval is not dismissed
- PR is already approved by this automation — not re-approving
- Risk derived from the diff contents, not from PR description claims
Sent by Cursor Automation: Assign PR reviewers



Summary
Adds a "Getting the static IP address" section at the bottom of the ISP proxies guide explaining how to read the static exit IP from the proxy API.
ip_addressin the response to creating a proxy and getting a proxy by ID.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only change to
proxies/isp.mdxwith no runtime or API behavior changes.Overview
Adds a Getting the static IP address section to the ISP proxies guide, placed after the bypass-hosts content.
It explains that ISP proxies expose a stable exit IP via the
ip_addressfield on create-proxy and get-proxy-by-id responses, with links to those API reference pages and a short allowlist use case. TypeScript, Python, and Go snippets show how to read that field after creating a proxy.Reviewed by Cursor Bugbot for commit 96a9502. Bugbot is set up for automated code reviews on this repo. Configure here.