DEVELOPERS / API
YOUR CODE. YOUR CONNECTION.
Plan how proxy management fits into your software. Understand the connection, permissions and checks your workflow needs.
Public API not yet available
Explore this pageA management request and a proxy connection do different jobs.
THE WEBChoose an integration path
USM is planning a public proxy management API. The API, Claude / Codex Skills and MCP service are not available to install or connect yet. This page explains the intended workflow; it is not an executable API reference.
| Your workflow | Integration | Current availability |
|---|---|---|
| Your software queries or manages proxy resources | Management API | Not released |
| Claude or Codex follows a proxy workflow | Agent Skills | No public package |
| An MCP-capable agent discovers management tools | MCP server | No public service |
Query first. Then test the connection.
When an integration is released, begin with a read-only request and check that the returned resources belong to the intended account. Proxy connection credentials then need to be configured in the browser or application that actually opens web pages.
- Identify the account and the resources the task is allowed to use.
- Retrieve connection details using the documented authentication method.
- Configure the task’s browser or HTTP client with those details.
- Check the exit IP and requested country from that same tool, then test a real target page.
What to check in an API reference
Use only endpoints and operations listed in a released USM reference. No public base URL, authentication format, request limits or endpoint catalogue has been published yet.
| Operation group | Information to check before use |
|---|---|
| Products and availability | Location, product type, specifications and whether inventory is current |
| Existing proxies | Resource ownership, connection fields, expiry and pagination |
| Usage | Units, measurement period and update timing |
| Orders and service changes | Permissions, charges, confirmation and how to verify the result |
Handle uncertain results before retrying
A successful management request does not prove that a target website is reachable. Keep API errors separate from authentication failures, network timeouts and responses returned by the target website.
For a purchase, renewal or replacement that times out, check the recorded outcome before repeating the operation. Follow the released API’s retry and idempotency rules; do not assume duplicate requests are safe.
Keep proxy usage and tool costs separate
Datacenter and residential products are priced by IP count and term. Rotating residential products use a GB allowance for each 30-day period. AI models and other tools have their own fees.
API call limits and any integration-specific conditions will be documented with the release. A proxy plan does not imply unlimited API requests.
What to include in a technical enquiry
Include your runtime, operation, timestamp with timezone, error message and what you have already tried. Remove passwords, API keys and full proxy credentials from logs and screenshots.
Versioned authentication, revocation and migration instructions will accompany the public release.
A CONNECTION THAT FITS