Skip to content

Document reading ISP proxy static IP via ip_address - #499

Merged
dprevoznik merged 3 commits into
mainfrom
hypeship/isp-proxy-ip-address
Aug 11, 2026
Merged

Document reading ISP proxy static IP via ip_address#499
dprevoznik merged 3 commits into
mainfrom
hypeship/isp-proxy-ip-address

Conversation

@dprevoznik

@dprevoznik dprevoznik commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

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.

  • The IP is returned as ip_address in the response to creating a proxy and getting a proxy by ID.
  • Links out to the respective API reference pages (create a proxy, get proxy by ID).
  • Includes TypeScript, Python, and Go examples reading the field.

🤖 Generated with Claude Code


Note

Low Risk
Documentation-only change to proxies/isp.mdx with 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_address field 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.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Kernel 🟢 Ready View Preview Aug 10, 2026, 8:13 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@vercel

vercel Bot commented Aug 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Error Error Aug 10, 2026 8:16pm

cursor[bot]
cursor Bot approved these changes Aug 10, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

Fix All in Cursor

❌ 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.

Comment thread proxies/isp.mdx Outdated
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 to 3d88d589 (absolute URLs for API reference links). Re-assessed the full diff against main.

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
Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@dprevoznik
dprevoznik merged commit f3fad77 into main Aug 11, 2026
4 checks passed
@dprevoznik
dprevoznik deleted the hypeship/isp-proxy-ip-address branch August 11, 2026 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant