Integration

SOAX integration

SOAX sells residential and mobile proxy access; this is its account API. List and inspect proxy packages and their traffic left, browse the countries, regions, cities, ISPs, ASNs and ZIP codes a package can target, read the account, credit blocks and subscription, pull usage analytics (credits burned and traffic over a date range), and check whether a host is on the SOAX firewall blocklist. Not exposed: connection strings and package password rotation (both return the package's proxy password), API key creation, listing and revocation, and the package password, allowed IPs and allowed users in package details. Authentication is an API key starting with s_live_, sent as a Bearer token; each route needs a scope on that key.

Connect SOAX How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SOAX.Built from the 18 SOAX tools below, on the connection you add once.

What you can do with SOAX

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Country, 2 operations

list_package_countriesList package countriesGETLists the countries this package can route traffic through, each with its code, name and price tier. Pass a code as cc to the other list_package_* tools. Scope proxy:packages:read.
list_proxy_countriesList proxy countriesGETLists every country on the SOAX network with its tier, whatever the package. For what one package can target use list_package_countries. Scope proxy:packages:read.

Package, 2 operations

get_packageGet packageGETReturns one package's configuration: status, types, tiers, traffic in bytes, connection limit, port and target rules and allowed protocols. Password, allowed IPs and users are not returned here. Scope proxy:packages:read.
list_packagesList packagesGETLists proxy packages with status, network types, tiers and traffic limit, spent and left (bytes). Paginated: pass next_cursor as cursor while has_more is true. Scope proxy:packages:read.

Account, 1 operation

get_accountGet accountGETReturns the organization's account: name, status (active or suspended), current plan identifier and creation date. Scope account:read.

Asn, 1 operation

list_package_asnsList package asnsGETLists ASNs of a country this package can target, with code, name, rank and volume_level. Answers 403 when the plan does not include ASN targeting. Scope proxy:packages:read.

Blocklist, 1 operation

check_firewall_blocklistCheck firewall blocklistGETChecks whether the SOAX system firewall blocks the host of a URL or bare domain or IP (blocked true or false). false only means not blocklisted, not reachable. No scope needed; 1 call per second per IP.

City, 1 operation

list_package_citiesList package citiesGETLists cities of a country (optionally one region) this package can target, with code, name, rank and volume_level. Scope proxy:packages:read.

Credit, 1 operation

list_credit_blocksList credit blocksGETLists active credit blocks with initial and remaining balance, effective and expiry dates. Proxy traffic consumes credits by the tier of the country it routes through. Scope account:read.

Credits burned, 1 operation

get_credits_burnedGet credits burnedPOSTReturns credits burned per day, split by tier: each item has a date and a data list whose key is the tier number as text and value the credits. Read-only. Range at most 365 days. Scope proxy:analytics:read.

Isp, 1 operation

list_package_ispsList package ispsGETLists ISPs of a country (optionally narrowed by region and city) this package can target, with code, name, rank and volume_level. Scope proxy:packages:read.

Me, 1 operation

get_current_api_keyGet current api keyGETReturns the calling API key's id, scopes, package restriction (package_ids, null = all packages), organization id and remaining rate-limit quota. Needs no scope: use it first to check what the key can call.

Region, 1 operation

list_package_regionsList package regionsGETLists regions of a country this package can target, with code, name, rank (1 = largest IP pool) and volume_level (1 to 3, 3 = most IPs). Scope proxy:packages:read.

Subscription, 1 operation

get_subscriptionGet subscriptionGETReturns the active subscription: plan, status and current billing period dates. Answers 404 when the account has no active subscription. Scope account:read.

Summary, 1 operation

get_usage_summaryGet usage summaryPOSTReturns total credits burned and traffic (GB) for a date range, plus the same totals for the previous period of equal length. Read-only. Range at most 365 days. Scope proxy:analytics:read.

Tier, 1 operation

list_proxy_tiersList proxy tiersGETLists the proxy tiers SOAX offers (tier number and name). Tiers group countries by pool quality and price. Scope proxy:packages:read.

Traffic, 1 operation

get_traffic_breakdownGet traffic breakdownPOSTReturns traffic in GB per interval bucket, grouped by package, proxy_type, tier, country or domain. Read-only. Range at most 365 days. Scope proxy:analytics:read.

Zip code, 1 operation

list_package_zip_codesList package zip codesGETLists ZIP codes of a country (optionally narrowed by region and city) this package can target. Answers 403 when the plan does not include ZIP targeting. Scope proxy:packages:read.

Use SOAX from Claude Code, Cursor or Codex

Connect SOAX in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SOAX operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SOAX

Create your workspace
Sign up free. Nothing to install.
Connect SOAX once
Add your SOAX connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.