One proxy, every format.

curl

curl -x 'http://residential.ghostconnect.io:1080' -U 'rJxYKRe2U:Yxa5WGCUkvP9km_country-US' 'https://ifconfig.me'

# the same, with the credentials in the proxy URL
curl -x 'http://rJxYKRe2U:Yxa5WGCUkvP9km_country-US@residential.ghostconnect.io:1080' 'https://ifconfig.me'

Python requests

import requests

proxies = {
    'http':  'http://rJxYKRe2U:Yxa5WGCUkvP9km_country-US@residential.ghostconnect.io:1080',
    'https': 'http://rJxYKRe2U:Yxa5WGCUkvP9km_country-US@residential.ghostconnect.io:1080',
}
r = requests.get('https://ifconfig.me', proxies=proxies, timeout=30)
print(r.status_code, r.text)

Node 18+ fetch with undici

// Node 18+, npm install undici. ProxyAgent speaks HTTP proxies only.
import { fetch, ProxyAgent } from 'undici';

const dispatcher = new ProxyAgent({
  uri: 'http://residential.ghostconnect.io:1080',
  token: 'Basic ' + Buffer.from('rJxYKRe2U:Yxa5WGCUkvP9km_country-US').toString('base64'),
});
const res = await fetch('https://ifconfig.me', { dispatcher });
console.log(res.status, await res.text());

undici's ProxyAgent is HTTP only, so this snippet uses the HTTP form and works when the port you typed serves HTTP. For SOCKS5 in Node use a SOCKS agent with the http module, or another client.

Environment variables

export HTTP_PROXY='http://rJxYKRe2U:Yxa5WGCUkvP9km_country-US@residential.ghostconnect.io:1080'
export HTTPS_PROXY='http://rJxYKRe2U:Yxa5WGCUkvP9km_country-US@residential.ghostconnect.io:1080'
export ALL_PROXY='http://rJxYKRe2U:Yxa5WGCUkvP9km_country-US@residential.ghostconnect.io:1080'
curl 'https://ifconfig.me'   # curl, pip, git and many others read these

What this tool does

Every proxy is the same four facts, a host, a port and usually a username and a password, but every tool wants them written differently. Dashboards hand out host:port:user:pass, browsers and scrapers want user:pass@host:port, curl takes a URL or a separate -U flag, Python requests wants a dictionary with an entry for http and for https, Node needs an agent, and shell tools read HTTP_PROXY. This page parses whichever shape you paste, checks each part (a real hostname or IP, a port from 1 to 65535, credentials without spaces, "@" or ":"), and writes out all of the others, with the password exactly as typed so that GhostConnect residential tags such as _country-US_lifetime-30_session-k2p9x7vq survive the trip.

Read the result from the top. The four plain formats are the proxy itself; copy the one your tool asks for. The snippets below them are complete commands and programs against the target URL you chose, and they use the protocol you picked, so if a snippet fails, the first things to check are that the port matches the protocol (HTTP and SOCKS5 are served on different ports) and that your tool kept the whole password rather than cutting it at an underscore. The formats here are the ones the API returns for residential plans, so a string from the dashboard and one from this page are interchangeable. They work the same for residential, ISP, datacenter and rotating IPv6 proxies; only the host, the port and whether SOCKS5 is offered differ.