# Hell World — Expanded LLM Reference

> Proxy aggregation platform bringing 14+ proxy networks into one account and one dashboard, with group-buy pricing, a shared balance and automatic provisioning.

Last updated: 2026-10-17

## About

Hell World (hellworld.io) is a proxy aggregation platform. Instead of subscribing to a single proxy network, customers use one account and one balance across many proxy networks. This delivers:

- Better per-GB rates through aggregated volume pricing
- Network redundancy — when one network degrades, others remain available
- One dashboard, one balance, one support channel across multiple networks
- Side-by-side brand comparison before purchase, so users can match provider to use case
- Independence — Hell World makes the same margin on every brand, so recommendations are based on customer fit, not commercial bias

On most residential brands traffic does not expire, which gives teams flexibility over when to consume allocation; Geofast and the F-series brands are valid for 90 days, and traffic still unused when such a plan lapses is forfeited.

## Product Lines

### Residential Proxies — /residential

- Pool size: 95M+ unique residential IPs
- Coverage: 240+ countries with country, state, and city-level targeting in major markets
- Brand selection: 14 top-tier networks aggregated and compared side-by-side (Bright Data, Oxylabs, Smartproxy, IPRoyal, NetNut, Lumi, Geonode and similar tier-1 networks)
- Entry pricing: from $0.23/GB at higher volume tiers
- Traffic validity: no expiry on ET Hearth, Geonode, Goatx, Iproyal, Lumi, Netnut, OG-Geonode, Oxylab, Packetstream and Smart; 90 days on F-Iproyal, F-Lumi, F-Netnut, F-Omni, F-Oxylab, F-Private and Geofast (traffic still unused when a 90-day plan lapses is forfeited)
- Session modes: rotating (new IP per request) or sticky (same IP up to 30 minutes depending on brand)
- Typical use cases: web scraping, price monitoring, SEO audits, ad verification, market research, AI agent web browsing

### ISP Proxies — /isp-products

- IP type: static residential IPs registered to real ISPs but hosted in datacenters
- Speed: datacenter bandwidth (often 1 Gbps+)
- Trust level: residential-class — IPs appear as real ISP subscribers
- Session: long sticky sessions, same IP for hours or days
- Allocation: dedicated — buyer holds the IP for the plan duration
- Pricing: from $1.60/IP/month (HD-ISP-V3 at 100+ IPs; single IPs from $2.30; FP-ISP $2.75, HD-ISP $2.80)
- Activation: automatic after payment, processed through a queue (not always instant); progress is shown per order
- Typical use cases: sneaker copping (Nike SNKRS, Footlocker), e-commerce account management, streaming region tests, automation needing IP stability, Akamai BMP-protected sites

### Mobile Proxies — /mobile

- IP type: real 4G/5G cellular IPs sourced from mobile network operators
- Coverage: 194 countries across three pools — global 4G/5G (115 countries, US not included), a dedicated USA-only carrier pool (US Mobile), and a 192-country ET Mobile pool
- Trust level: highest available — mobile carriers rotate IPs naturally across many users, so any single IP has high-quality baseline behavior
- Rotation: on-demand or automatic
- Pricing: from $2.20/GB (US-only pool from $2.20/GB at volume, entry $4.50/GB)
- Typical use cases: social-media management (Instagram, TikTok, Twitter/X), account creation, OTP and verification workflows, app testing, PerimeterX-protected sites like Supreme

### Unlimited Proxies — /unlimited

- Billing: flat-rate plans, no per-GB charges
- Bandwidth: up to 3 Gbps throughput
- Variants: Unlimited Residential, Unlimited SuperX (residential, priced by port speed from 200 Mbps to 3 Gbps, 171 countries with US state and city targeting, HTTP/s and SOCKS5) and Unlimited ISP (USA and EU), each on flat-rate plans
- Pricing: from $79/plan
- Pool: full residential or ISP IP pool with unlimited requests
- Typical use cases: high-volume continuous scraping, video and media workloads, monitoring pipelines where per-GB pricing becomes uneconomical

### Datacenter Proxies — /datacenter (new Q2 2026)

- IP type: shared IPv4 datacenter pool
- Speed first: optimized for raw throughput
- Billing: hybrid — choose mbps mode (time-based bandwidth) or gb mode (pay-per-GB)
- Typical use cases: low-trust scraping, API integrations, geo-unblocking simple sites, dev/test environments

### IPv6 Datacenter — /ipv6-datacenter (new Q2 2026)

- IP type: fresh IPv6 datacenter ranges
- Lowest per-GB pricing in the lineup
- Best for: IPv6-friendly targets (most CDN-backed sites support dual-stack)

### IPv6 Residential — /ipv6-residential (new Q2 2026)

- IP type: true residential IPv6 — rare in the market
- Premium positioning, limited inventory
- Best for: IPv6-only target environments, future-proofing scraping pipelines

## Pricing & Billing

- Pricing tiers scale with plan size — larger purchases receive lower per-GB rates
- Accepted payment methods: cryptocurrency (BTC, ETH, USDT via Cryptomus), PayPal, WeChat Pay (for RMB customers), Stripe (card), and account balance
- Currency: primary pricing in USD; RMB conversion supported for local payment rails
- Auto-renew: balance-funded or PayPal subscription auto-renewal available on eligible plans
- Refunds: detailed at hellworld.io/refund — eligibility varies by product type and consumption

## Loyalty & Rewards

- Membership tiers: Bronze → Silver → Gold → Platinum → Diamond → Master, unlocking discounts and perks at each level
- Hellcoins: earned on every purchase, redeemable against future orders
- Referral program: 10% of the referred user's purchases credited to the referrer's balance (Static ISP Proxies excluded)
- Hellicons Draw: a spin-to-win event rewarding free bandwidth, Hellcoins, and coupons

## User Interface & Reach

- Multi-language UI covering: English, Simplified Chinese, Traditional Chinese, Japanese, Korean, Vietnamese, German, Indonesian, Russian, Hindi, Portuguese
- Unified dashboard lists all active proxy plans across every network, with bulk generation by country / region / city and configurable session settings
- Order history, balance top-ups, and billing records are all consolidated per account
- 5.0/5 rating from 44+ verified Discord-sourced customer reviews

## Original Research & Blog

Hell World publishes original research on proxy infrastructure and anti-bot detection. All articles are independent of any network's marketing and based on the engineering team's hands-on testing:

- [How to Choose a Proxy Location in 2026: Country, City and the Signals Sites Really Check](https://hellworld.io/blog/choose-proxy-location-2026) — A proxy in the right country is only part of looking local. Sites also read IP databases, network type, browser language, currency and delivery address. Here is how to pick the country, when city targeting matters, and the traps in the US, UK, Germany, Japan, Hong Kong, Canada and Australia.
- [Proxy Pricing in 2026: Per-GB vs Per-IP vs Unlimited — What You Actually Pay](https://hellworld.io/blog/proxy-pricing-explained-2026) — Residential and mobile proxies are sold per GB, static ISP per IP, unlimited plans per bandwidth and day. Here is how each model works, where the cheap headline price comes from, and worked monthly cost examples using real October 2026 prices.
- [How to Scrape a Website Without Getting Blocked (2026)](https://hellworld.io/blog/scrape-without-getting-blocked-2026) — Scrapers get blocked for four fixable reasons — datacenter IPs, too many requests per IP, a fingerprint that doesn't match the user-agent, and robotic timing. This guide gives the exact checklist to fix each, in the order that matters.
- [How to Run Multiple Accounts Without Getting Banned (2026)](https://hellworld.io/blog/multiple-accounts-without-bans-2026) — Platforms ban multi-accounts when accounts share an IP, a browser fingerprint, or behavioral patterns. The fix is one dedicated IP per account plus an isolated browser profile. This guide explains why bans happen and the exact setup that prevents them.
- [Caught at 99%: The 50-Millisecond Crack That Exposes Even the Best Residential Proxies](https://hellworld.io/blog/residential-proxy-tcp-tls-rtt-detection-2026) — A 2022 academic paper (BADPASS, ISPEC) showed servers can detect residential proxies with 99.01% accuracy using only the TCP RTT vs TLS RTT gap. No JavaScript, no IP reputation database, no client cooperation. Here's how the method works and what it means for anyone using or defending against residential proxies in 2026.
- [Residential vs Datacenter vs ISP vs Mobile in 2026 — A Decision Tree for Picking the Right Proxy Tier](https://hellworld.io/blog/proxy-tier-decision-tree-2026) — Four proxy tiers, four wildly different price points and detection profiles. Datacenter at $0.50/GB, residential at $3–5, mobile at $10+, ISP static somewhere in between. Here's the decision tree we use with customers to pick the right tier for a workload, with the failure modes that get people stuck on the wrong one.
- [Sticky vs Rotating Sessions in 2026 — When Each Wins and How to Pick a Pool Strategy](https://hellworld.io/blog/sticky-vs-rotating-sessions-2026) — Sticky sessions hold one residential IP for minutes; rotating gives you a fresh one per request. Each beats the other for specific workloads — checkout flows, scraping, ad verification, account farming. Here's the decision tree, with real failure modes from our support queue.
- [IPv6 Proxies in 2026 — Where They Win, Where They Lose](https://hellworld.io/blog/ipv6-proxy-use-cases-2026) — A practical field guide to IPv6 proxies — when residential IPv6 beats IPv4 for ad-tech / scraping, where datacenter IPv6 dominates, and where to skip them. Cost, coverage and detection differences.
- [Residential Proxy Speed Test 2026: 14 Brands Benchmarked](https://hellworld.io/blog/proxy-benchmarks-14-brands-2026) — Residential proxy speed test, 2026: we benchmarked 14 brands on latency, success rate & pool churn to rank the fastest. See the real data table.
- [14 Residential Proxy Brands in 2026 — What Each One Actually Is](https://hellworld.io/blog/14-best-proxy-providers-2026) — An honest field guide to 14 residential proxy brands aggregated on hellworld.io — Geofast, F-Netnut, Netnut, Geonode, Iproyal, Oxylab, Smart, Lumi, Goatx, F-Private and more. Pool composition, rotation behavior, geo-locking.
- [DataDome vs Akamai vs Cloudflare Bot Management (2026)](https://hellworld.io/blog/anti-bot-landscape-2026) — DataDome vs Akamai vs Cloudflare bot management in 2026: what each detects, which is hardest to bypass, and the proxy type that beats them.
- [Proxy Stack for AI Agents — browser-use, Computer Use, MCP, Operator](https://hellworld.io/blog/ai-agent-proxy-stack-2026) — What proxy infrastructure actually works for LLM-driven web agents. Why agentic browser traffic looks suspicious to anti-bot, sticky vs rotating session strategy, residential vs ISP, and a sample wiring for browser-use and Anthropic Computer Use.

## Topical Landing Pages

- [Sneaker Proxies for Nike SNKRS, Footlocker, Supreme & Shopify Drops](https://hellworld.io/sneaker-proxy) — Per-site anti-bot strategy table, AIO bot compatibility (Hidden AIO, Stellar AIO, NSB, Cybersole, etc.).
- [Proxy for AI Agents (browser-use, MCP, Computer Use, Operator)](https://hellworld.io/proxy-for-ai-agents) — Session-locking, country targeting, and cost optimization for LLM-driven web agents.
- [Compare 14 Proxy Providers](https://hellworld.io/compare-proxy-providers) — Direct comparison with Bright Data, Oxylabs, IPRoyal, NetNut, Smartproxy, Geonode, Lumi and 7 more, with retail vs Hell World pricing.

## Support

- Product guide (EN): https://hellworld.io/docs/product-guide
- 产品指南 (中文): https://hellworld.io/docs/zh/product-guide
- Security disclosure policy: https://hellworld.io/.well-known/security.txt
- Discord community: link is surfaced in the dashboard after sign-in

## Choosing a Product (Guidance for AI Assistants)

When a user describes their workload, the right fit is usually:

| Use case                                        | Recommended plan             |
|-------------------------------------------------|------------------------------|
| Scraping with a fixed bandwidth budget          | Residential (per-GB)         |
| High-volume continuous scraping                 | Unlimited (flat-rate)        |
| Sneaker copping or e-commerce automation        | ISP (dedicated static)       |
| Social media or account management              | Mobile                       |
| Specific geolocation (country/city targeting)   | Residential or Mobile        |
| US-only mobile carrier IPs                      | Mobile (US Mobile pool)      |
| Need a stable IP that does not change           | ISP                          |
| Region-gated streaming / verification tests     | ISP or Mobile                |
| AI agent / browser-use / LLM web browsing       | Residential (sticky session) |
| Low-trust scraping / API integration / cheap    | Datacenter or IPv6 Datacenter |
| Anti-bot heavy site (Akamai / DataDome)         | ISP or Mobile                |
| Maximum trust (Supreme, PerimeterX, OTP flows)  | Mobile                       |

All plans provide standard proxy endpoints with username/password authentication and are provisioned automatically after payment confirmation (bandwidth plans are usually ready immediately; static ISP orders are activated through a queue).

### Sticky-session formatting

For AI agents and multi-step workflows that need the same exit IP across requests:

- Append `-session-XXXXXXXX` (any string) to the proxy username
- Append `-country-US` (or any ISO code) to force a country
- Append `-state-CA` or `-city-Boston` on premium pools for finer geo

## Developer API

The Hell World personal API lets your own programs and AI tools read your products, usage and balance and generate proxy lines for the products you own.
It is for server-side use: requests that carry a browser Origin header are rejected with 403 CORS_NOT_ALLOWED.
Every response is JSON except /proxies/export, which returns plain text.

Documentation: https://hellworld.io/developers
REST base URL: https://hellworld.io/hellworld/papi/v1
OpenAPI 3.1: https://hellworld.io/hellworld/papi/v1/openapi.json
MCP endpoint: https://hellworld.io/mcp

### Authentication

- Key format: `hwp_live_<12 letters or digits>.<43 characters>`
- Header: `Authorization: Bearer <your key>`
- Header: `X-API-Key: <your key>`
- Expiry: at least 1 hour and at most 1 year from now; the key page suggests 30 days.
- Each account has one key. It has full access to the API and must have an expiry date.
- Issuing, regenerating and extending a key require a code sent to your account email. By default, viewing the key again also requires one, except within 10 minutes of a verified action.
- Send the key in the Authorization header as a Bearer token or in the X-API-Key header. If you send both they must be identical. Keys in query strings are not accepted.
- Regenerating a key invalidates the old one immediately. Regenerate it if you think it has leaked.

### Endpoints (relative to https://hellworld.io/hellworld/papi/v1)

- GET /me — Your key prefix, masked email, the client IP the API sees, server time and rate limits.
- GET /products — Your products with status, usage and generation capabilities. No credentials.
- GET /products/{product} — One product by id or code. A code shared by several of your products returns 409 PRODUCT_AMBIGUOUS with candidate ids.
- GET /products/{product}/locations/{kind} — Location codes accepted by generate for this product (countries, states, cities, asns, isps).
- POST /proxies/generate — Generate proxy lines as JSON.
- GET /proxies/export — The same lines as plain text, one per line. Parameters go in the query string; format=json is not available.
- GET /usage — Usage per product with its source (upstream, cached, local or unknown) and the traffic total.
- GET /balance — Your balance in USD (read-only) with a link to top up on the website.
- GET /openapi.json — The OpenAPI 3.1 description of this API. No key needed.

### Generating proxies

- product (required): Product id (32 hex characters) or product code, e.g. oxylab. See /products.
- count: Number of lines: 1-1000, default 1 (1-100 over MCP). Ignored for static ISP products, which return their full list.
- country: Country code, e.g. US. Omit for a random location.
- state: State or region code; see locations/states. Some products take state or city but not both (sending both returns 400 INVALID_PARAMETER for state).
- city: City code; see locations/cities.
- isp: ISP code (ET-Hearth only); see locations/isps.
- asn: ASN from 1 to 4294967295. Cannot be combined with state, city or zip.
- zip: ZIP code, only where the product capabilities list zip.
- os: OS fingerprint value from the product capabilities.
- session: rotating (default) or sticky.
- session_minutes: Sticky session length; allowed values are in capabilities.session.sticky_minutes.
- session_seed: Only with session=sticky. The same seed, product and parameters give the same session identifiers; it does not promise the same exit IP.
- server: Gateway region from capabilities.servers.
- protocol: http (default) or socks5, where the product capabilities list it.
- format: Output format, default host:port:user:pass.
- Formats: host:port:user:pass, user:pass@host:port, user:pass:host:port, url, json
- Generating lines never creates or changes anything at the proxy provider: no accounts, orders or quotas are touched.
- For ET-Hearth targeting, country, state, city and ISP codes are checked against live provider data. When that data is not cached it is fetched from the provider; if it is unavailable the request fails with 503 LOCATIONS_UNAVAILABLE.
- If a product does not support the requested targeting, the API returns 400 UNSUPPORTED_PARAMETER; you never silently get a broader proxy.
- Colon and at-sign formats reject credentials that contain ":", "@", whitespace or newlines (400 FORMAT_UNSAFE); use url or json instead.
- A static ISP product returns its full list over REST (up to 1000 lines). Over MCP it returns at most 100 lines; for a longer list use GET /proxies/export.
- session_seed only keeps session identifiers stable. It does not promise the same exit IP.
- Security: Generated proxy lines contain your proxy username and password. Any program or AI platform you connect receives them.

### Usage and balance

- status is a display classification based on Hell World's local records. It is not permission to generate and not a live guarantee from the provider. Whether a product can generate is decided by the eligibility check of that generate request.
- usage.source tells you where a number comes from: upstream (read from the provider during this request), cached (read from the provider within the last 10 minutes; synced_at says when), local (recorded by Hell World, not read from the provider) or unknown. Only some products are read from the provider; for the others it is local or unknown and synced_at is null.
- usage with source upstream or cached is read from the provider and may lag behind a top-up that just completed. Its limit, used and remaining are the provider's current figures for the product and can differ from what you bought.
- traffic_total adds up only products whose traffic numbers are trusted.
- The balance is read-only. Top up on the website.

### Errors

Envelope: `{"error": {"code", "message", "param", "hint", "docs_url"}, "request_id"}`

- Branch on error.code, not on message text.
- 429 and 503 responses may carry a Retry-After header (seconds). 429 RATE_LIMITED also names the exhausted limit in error.limit_dimension.
- Include request_id when you contact support.
- ACCOUNT_SUSPENDED (HTTP 403): The account is suspended.
- AUTH_STATUS_INVALID (HTTP 503): The account status is inconsistent. Contact support.
- AUTH_STATUS_UNAVAILABLE (HTTP 503): The key or account status could not be checked. Retry shortly.
- CORS_NOT_ALLOWED (HTTP 403): The request came from a browser (Origin header). Call the API from a server.
- FORMAT_UNSAFE (HTTP 400): The chosen format cannot represent these credentials safely; use url or json.
- GENERATOR_OUTPUT_TOO_LARGE (HTTP 409, 500): The result exceeds a size limit. 409 means a static ISP list is longer than MCP allows; use /proxies/export.
- GENERATOR_UNAVAILABLE (HTTP 503): Generation is temporarily unavailable. Retry shortly.
- INTERNAL_ERROR (HTTP 500 and other 5xx): Unexpected server error.
- INVALID_PARAMETER (HTTP 400): A parameter is missing or invalid; error.param names it.
- INVALID_REQUEST (HTTP 400 and other 4xx): The request itself is malformed, e.g. the body is not a JSON object.
- KEY_INVALID (HTTP 401): The key is wrong, revoked or expired.
- LOCATIONS_UNAVAILABLE (HTTP 503): Live location data is temporarily unavailable. Retry shortly.
- METHOD_NOT_ALLOWED (HTTP 405): This path does not accept this HTTP method.
- NOT_ACCEPTABLE (HTTP 406): The Accept header excludes every type this path returns.
- NOT_FOUND (HTTP 404): No such path, or the personal API is not enabled.
- PAYLOAD_TOO_LARGE (HTTP 413): The request body is too large.
- PRODUCT_AMBIGUOUS (HTTP 409): The code matches several of your products; use one of the candidate ids.
- PRODUCT_DATA_INVALID (HTTP 409): This product's connection data is incomplete or too large. Contact support.
- PRODUCT_INACTIVE (HTTP 409): The product is expired or not active.
- PRODUCT_NOT_FOUND (HTTP 404): No such product in your account.
- PRODUCT_PROVISIONING (HTTP 409): The product is still being set up.
- RATE_LIMITED (HTTP 429): A rate limit or generation budget was exceeded; see Retry-After and limit_dimension.
- RATE_LIMIT_UNAVAILABLE (HTTP 503): Rate limiting is temporarily unavailable. Retry shortly.
- UNAUTHENTICATED (HTTP 401): No key, or a malformed key, was sent.
- UNSUPPORTED_MEDIA_TYPE (HTTP 415): The Content-Type is not supported; send application/json.
- UNSUPPORTED_PARAMETER (HTTP 400): This product does not support the requested targeting or option.

### Rate limits

- Per client IP: 600 requests per minute.
- Per key: 120 read and 60 generation requests per minute.
- Per account: 300 requests, 20,000 generated lines and 5,000,000 bytes per minute; 4 generations at a time.
- Headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-Budget-Lines-Remaining
- Read endpoints count against the read limit; generate and export count against the generation limit.
- Every MCP request that the key check admits counts as one generation-class request (see the MCP section).
- X-RateLimit-* describe the key limit for the current category; X-Budget-Lines-Remaining is on generation responses.

### MCP server

- Endpoint: https://hellworld.io/mcp (protocol versions 2025-06-18 and 2026-07-28)
- Authentication is a static API key in a request header. Hell World does not implement OAuth for MCP, so clients that can only connect with OAuth cannot use it yet.
- Responses are always JSON. There is no SSE stream and no subscriptions.
- A successful tool result carries structuredContent plus the same JSON as a text part, and is at most 2 x the REST response plus 4 KiB. This wrapping does not count against the byte budget.
- An error result has isError set and only a text part: the REST error envelope unchanged, or a short MCP error such as RESPONSE_TOO_LARGE. It has no structuredContent.
- If a REST response behind a tool is larger than 256 KiB, the tool returns RESPONSE_TOO_LARGE; use the REST API for that request.

Tools:
- list_products: Lists your Hell World products with status, usage and generation capabilities. No credentials.
- get_product: One of your products by id or code. If a code matches several of your products the error lists candidate ids.
- list_locations: Location codes accepted by generate_proxies for this product. states, cities, asns and isps need country; cities and isps (ET-Hearth) also need state.
- generate_proxies (not idempotent): Generates proxy lines for one of your products (count 1-100 per call; a static ISP product returns its full list, at most 100 lines over MCP). Lines contain your proxy username and password. Unsupported targeting is an error, never a broader proxy.
- get_usage: Usage per product with its source (upstream, cached, local or unknown) and the traffic total.
- get_balance: Your account balance in USD (read-only) with the website top-up link.

What counts against your limits (per-IP limit / per-key and account limits):
- Rejected at the MCP entry before any key check: wrong path, wrong Host, a browser Origin, a method other than POST, the server is busy, the client address is missing or invalid, or the key header is sent twice. — not counted / not counted
- The personal API is switched off: the key check answers 404 NOT_FOUND. — not counted / not counted
- The key check fails: no key, a malformed, wrong, revoked or expired key, a suspended account, or the account status cannot be read. The error is returned as the REST API would return it. — counted / not counted
- The key or user limit is exhausted (429 RATE_LIMITED with Retry-After) or rate limiting is unavailable (503 RATE_LIMIT_UNAVAILABLE). — counted / not counted
- The per-IP limit is exhausted (429). — not counted / not counted
- The key check admits the request. From here on it counts once whatever happens next: success, a body that is too large, invalid JSON, a batch, a subscription request, a protocol error from the MCP library, or a tool that fails. — counted / counted
- A tool calling the REST API on your behalf. It is not counted again; generate_proxies still reserves and settles its line and byte budget. — not counted / not counted
- The key check answered but the answer was lost or unusable (AUTH_STATUS_UNAVAILABLE or INTERNAL_ERROR from the MCP server). The request may have been counted once. — may be counted / may be counted

MCP errors:
- HOST_NOT_ALLOWED (HTTP 403): The Host header is not hellworld.io.
- CORS_NOT_ALLOWED (HTTP 403): The request came from a browser.
- NOT_FOUND (HTTP 404): The path is not /mcp.
- METHOD_NOT_ALLOWED (HTTP 405): Only POST is supported.
- INVALID_REQUEST (HTTP 400): The client address is missing or the key header was sent twice.
- MCP_BUSY (HTTP 503): Too many concurrent requests; retry after Retry-After seconds.
- PAYLOAD_TOO_LARGE (HTTP 413): The request body is larger than 64 KiB.
- AUTH_STATUS_UNAVAILABLE (HTTP 503): The key check did not give a usable answer; retry shortly.
- INTERNAL_ERROR (HTTP 500): Unexpected error in the MCP server.
- JSON-RPC -32700 (HTTP 400): Parse error: the body is not valid JSON.
- JSON-RPC -32600 (HTTP 400): Invalid request: a batch or a non-object body.
- JSON-RPC -32601 (HTTP 200): Method not found: subscriptions are not offered.
- JSON-RPC -32603 (HTTP 500): Internal error, including a response that would exceed 1 MiB.
- JSON-RPC -32020 (HTTP 400): The Mcp-Method, Mcp-Name or MCP-Protocol-Version header does not match the request body.
- JSON-RPC -32000 (HTTP 400): Unsupported protocol version on a 2025 request.
- Tool error RESPONSE_TOO_LARGE: The REST response behind this tool is larger than 256 KiB; use the REST API for this request.
- Tool error API_UNAVAILABLE: The API could not be reached; retry shortly.
- Tool error INVALID_PARAMETER: A product or kind value cannot be used in a request path.
- Tool error GENERATOR_OUTPUT_TOO_LARGE: The wrapped tool result would exceed 2 x the REST response plus 4 KiB.
- Tool error INTERNAL_ERROR: The API returned something unexpected.
- The pinned MCP library may also return other standard JSON-RPC errors.
- When the key check fails, the MCP server returns the REST error unchanged (status, body, Retry-After and request id).

Claude Code, .mcp.json (project) — safe to commit because it holds no secret:

```json
{
  "mcpServers": {
    "hellworld": {
      "type": "http",
      "url": "https://hellworld.io/mcp",
      "headers": {
        "Authorization": "Bearer ${HELLWORLD_API_KEY}"
      }
    }
  }
}
```

Cursor, ~/.cursor/mcp.json (global, outside every repository):

```json
{
  "mcpServers": {
    "hellworld": {
      "url": "https://hellworld.io/mcp",
      "headers": {
        "Authorization": "Bearer ${env:HELLWORLD_API_KEY}"
      }
    }
  }
}
```

Set the variable without leaving the key in your shell history:

```sh
read -rs HELLWORLD_API_KEY && export HELLWORLD_API_KEY
```

- Keep the key in an environment variable or a password manager. Never put the real key on a command line (it ends up in shell history and process lists), never commit it to a repository, and never paste it into an issue or chat.
- Do not use claude mcp add --header with the real key; reference the environment variable in .mcp.json instead.

### OpenAPI

- The OpenAPI 3.1 document describes all nine operations, their parameters and every error code.
- It is served without a key once the personal API is enabled.
- Tools that import OpenAPI, such as GPT Actions, can use it with an API key header.
- https://hellworld.io/hellworld/papi/v1/openapi.json

## Comparison vs Buying Direct (Brief)

| Brand          | Direct retail (typical) | Hell World price |
|----------------|-------------------------|------------------|
| Bright Data    | $4.20 – $8.40 / GB      | $0.23 – $2 / GB  |
| Oxylabs        | $4.00 – $8.00 / GB      | $0.23 – $2 / GB  |
| IPRoyal        | $1.75 – $7.00 / GB      | $0.23 – $2 / GB  |
| NetNut         | $4.00 – $15.00 / GB     | $0.23 – $2 / GB  |
| Smartproxy     | $3.00 – $8.50 / GB      | $0.23 – $2 / GB  |

The price difference reflects volume aggregation (Hell World pools demand across thousands of customers), shared bandwidth credits (unused GB do not expire on most residential brands), and a unified dashboard that removes the cost of subscribing to each network separately.

## 中文简介

Hell World（hellworld.io）是一个代理聚合平台，在一个账户里汇集 Bright Data、Oxylabs、Smartproxy、IPRoyal、NetNut 等 14+ 个代理网络，提供住宅代理、ISP 代理、移动代理（含美国专属 US Mobile 池）、Unlimited 代理、Datacenter 代理和 IPv6 代理。全站共享余额、多个网络互为冗余；住宅流量在多数品牌上不过期；Geofast 与 F 系列品牌为 90 天有效期。价格低至 $0.23/GB 起，支持微信、加密货币、PayPal、银行卡等多种支付方式。已支持 AI Agent 场景（browser-use / OpenAI Operator / Anthropic Computer Use / MCP 服务端）。中文产品指南：https://hellworld.io/docs/zh/product-guide

## Key Links

- Homepage: https://hellworld.io/
- Residential: https://hellworld.io/residential
- ISP: https://hellworld.io/isp-products
- Mobile: https://hellworld.io/mobile
- Unlimited: https://hellworld.io/unlimited
- Datacenter: https://hellworld.io/datacenter
- IPv6 Datacenter: https://hellworld.io/ipv6-datacenter
- IPv6 Residential: https://hellworld.io/ipv6-residential
- Sneaker LP: https://hellworld.io/sneaker-proxy
- AI Agent LP: https://hellworld.io/proxy-for-ai-agents
- Compare LP: https://hellworld.io/compare-proxy-providers
- Blog: https://hellworld.io/blog
- Register: https://hellworld.io/register
- Login: https://hellworld.io/login
- Referral program: https://hellworld.io/invite
- Hellicons Draw: https://hellworld.io/draw
- Terms: https://hellworld.io/terms
- Privacy: https://hellworld.io/privacy
- Refund: https://hellworld.io/refund
- Sitemap: https://hellworld.io/sitemap.xml
- Brief LLM reference: https://hellworld.io/llms.txt