Coronium Mobile Proxies

Proxy Integrations

Every tool asks for the same handful of fields. Copy them once from the dashboard, then follow the guide for your browser, cloud phone, agent or library.

What every integration needs

In dashboard.coronium.io, open Your Proxies. Each line's card shows the fields below, under the names the dashboard uses. In List view the Connection column copies the whole endpoint with the login in the format picked in the toolbar.

  • Connection IP
    Where it is
    Proxy card, Cards view
    Where it goes
    Host, server or IP field
  • HTTP Port
    Where it is
    Proxy card
    Where it goes
    Port, when the tool is set to HTTP or HTTPS
  • SOCKS5 Port
    Where it is
    Proxy card
    Where it goes
    Port, when the tool is set to SOCKS5
  • Username and Password
    Where it is
    Proxy card
    Where it goes
    Login fields; the same pair works on both ports
  • Reset Link
    Where it is
    IP Rotation block on the card (List view: Rotate API link in Actions)
    Where it goes
    The tool's change-IP or rotation URL field

Formats tools accept

Colon form, most tools
host:port:user:pass
Login first
user:pass@host:port
SOCKS5 URL
socks5://user:pass@host:port
HTTP URL
http://user:pass@host:port

With the colon form, pair the SOCKS5 Port with SOCKS5 and the HTTP Port with HTTP. Inside a URL, symbols in a username or password need URL encoding. A login that is rejected returns a 407; the 407 error guide walks through the causes.

Check the line before you log in

Exit IP over SOCKS5, DNS resolved through the line
curl -x socks5h://USER:PASS@HOST:SOCKS5_PORT https://api.ipify.org
Exit IP over HTTP
curl -x http://USER:PASS@HOST:HTTP_PORT https://api.ipify.org

Both print the public IP the site will see. It should be a carrier address in the line's country. In a browser, open what is my IP and the WebRTC leak test inside the profile.

The Reset Link changes the IP each time it is requested, link previews included, with at least 60 seconds between changes. Paste it only into the tool that should use it.

Antidetect browsers

An antidetect browser gives each profile its own fingerprint, cookies and storage. The proxy is the profile's network, so it belongs to the profile, not to the browser: one line per profile you need to keep apart, with the profile's timezone and language set to match the line's country.

Cloud phones

A cloud phone is an Android device that runs in a data center, so out of the box its traffic leaves from a hosting IP. Pointing it at a mobile line gives apps on that phone a carrier address. Use one line per phone and paste the line's rotation link where the service has a change-IP field.

AI agents and MCP clients

Agents meet two network problems: their browser leaves from a cloud host that sites distrust, and they need a way to manage lines without a person clicking. The first is solved by giving the agent's browser a line. The second is the Coronium MCP server, which lets an agent list stock, read its lines and rotate an IP, with spending tools off unless you switch them on.

The MCP server in any client

Most MCP clients read a config like this one. Create the token in the dashboard under Account - API Access. The directory profile registers 21 tools and none of them spend money. Clients that support remote MCP with OAuth can use the hosted server at https://api.coronium.io/mcp instead.

MCP client config, directory profile
{
  "mcpServers": {
    "coronium": {
      "command": "npx",
      "args": ["-y", "coronium-proxy-mcp@2.3.0"],
      "env": {
        "CORONIUM_API_TOKEN": "YOUR_CORONIUM_API_TOKEN",
        "CORONIUM_TOOL_PROFILE": "directory"
      }
    }
  }
}

Agent guides

Scrapers and automation

Crawlers and workflow tools usually take one proxy URL per job or per browser context. Give each worker its own line when the target limits by IP, rotate between batches rather than between requests, and keep concurrency at a level a single phone connection can carry.

  • Firecrawl

    Self-hosted Firecrawl with a mobile proxy.

  • ScrapeGraphAI

    LLM scraping graphs routed through a line.

  • Apify

    Custom proxies in Apify actors.

  • n8n

    Proxy settings for HTTP Request nodes.

  • Scrapy

    Proxy middleware and per-request meta.

  • Playwright

    Browser contexts, sessions and rotation.

  • Puppeteer

    Launch flags and page authentication.

  • Selenium

    Authenticated proxies in Selenium drivers.

  • Crawlee

    Crawlee crawlers with a proxy configuration.

  • ChromeDP

    Go browser automation with a proxy.

Code libraries

In code the proxy is one URL with the login inside it. The guides below show the exact syntax for each library, the authentication pitfalls that end in a 407, and how to check the exit IP before you send real traffic.

  • cURL

    The -x flag, socks5h and verbose output.

  • cURL on Linux

    System proxy variables and curl checks.

  • Python Requests

    Proxies dict, authentication and sessions.

  • HTTPX

    AsyncClient proxies, limits and TLS.

  • aiohttp

    Encoded credentials and session timeouts.

  • Axios

    Proxy agents for Node.js.

  • Node.js fetch

    Undici dispatchers for proxied fetch.

Phones, computers and browsers

For manual work the line goes into the operating system, the browser or a proxy app. Phones take an HTTP proxy per Wi-Fi network and usually need an app for SOCKS5, which the phone guides explain.

  • Android

    Wi-Fi proxy settings and proxy apps.

  • iPhone and iPad

    Per-network proxy settings on iOS.

  • Shadowrocket on iOS

    SOCKS5 and rules on iPhone.

  • Windows

    System proxy and proxy clients.

  • Mac

    Network settings and app-level proxies.

  • Browsers

    Chrome, Edge and Firefox proxy settings.

  • Routers

    Sending a whole network through a line.

  • OpenVPN

    Using a line's OpenVPN profile where it has one.

  • Any tool

    The general setup walk-through.

Building your own integration

For your own software, the REST API v3 covers stock, buying, renewal, rotation and replacement. The mobile proxy API page collects the OpenAPI spec, the SDK, the CLI, webhooks and tested requests. Resellers can start from the reseller kit.

Plans and stock for one country, no token needed
npx -y coronium-cli tariffs --country US

Integration questions

HTTP or SOCKS5: which port do I paste?

Whichever protocol the tool is set to. Every Coronium line has an HTTP port and a SOCKS5 port on the same host, with one username and password for both. Browsers and most antidetect tools take either. With SOCKS5, make sure the tool hands hostnames to the proxy (socks5h in curl), so DNS lookups also go through the line.

Where do I find the rotation link?

In dashboard.coronium.io, open Your Proxies. In Cards view the IP Rotation block on each proxy card has the Reset Link; in List view use the Rotate API link button in the Actions column. Paste it into the tool's change-IP field and keep it private, because anyone who has it can change your IP.

Can an AI agent manage lines by itself?

Yes, through the Coronium MCP server or the REST API. The MCP server starts with spending tools off; an agent can list stock, read its lines and rotate an IP. Buying and renewing need the spending setting switched on by you.

My tool is not listed. Will it work?

If it accepts an HTTP or SOCKS5 proxy with a username and password, yes. Use the fields in the table at the top of this page, then check the exit IP with the commands under it before you log in to anything.