proxybase-openclaw-skillPurchase and manage SOCKS5 residential proxies via ProxyBase API with cryptocurrency payments. Supports order creation, payment polling, proxy delivery, band...
Install via ClawdBot CLI:
clawdbot install proxybase-user/proxybase-openclaw-skillProxyBase provides US residential SOCKS5 proxies for AI agents via a REST API
with cryptocurrency payments. Proxies never expire by time ā only by bandwidth.
| Item | Value |
|---|---|
| API Base | $PROXYBASE_API_URL (default: https://api.proxybase.xyz/v1) |
| SOCKS5 Host | api.proxybase.xyz:1080 |
| Auth Header | X-API-Key: (key starts with pk_) |
| Payments | Crypto via NOWPayments (USDT TRC20, BTC, ETH, SOL, etc.) |
| Pricing | ~$10/GB US residential |
This skill uses zero-configuration registration. The first time any
ProxyBase command is run, the agent automatically registers and stores
credentials in {baseDir}/state/credentials.env. No manual API key setup
or openclaw.json edits are required.
For manual or debugging use, you can also register explicitly:
source {baseDir}/scripts/proxybase-register.shAll persistent state lives in {baseDir}/state/:
credentials.env ā API key (PROXYBASE_API_KEY=pk_...)orders.json ā Tracked orders with status and proxy info.proxy-env ā Sourceable SOCKS5 proxy environment variablescurl -s -X POST "$PROXYBASE_API_URL/agents" | jq .Returns { "agent_id": "...", "api_key": "pk_..." }.
Save the api_key ā it is required for every subsequent call.
curl -s "$PROXYBASE_API_URL/packages" -H "X-API-Key: $PROXYBASE_API_KEY" | jq .Returns array of packages:
us_residential_1gb ā 1 GB, $10us_residential_5gb ā 5 GB, $50us_residential_10gb ā 10 GB, $100Each has: id, name, bandwidth_bytes, price_usd, proxy_type, country.
curl -s "$PROXYBASE_API_URL/currencies" -H "X-API-Key: $PROXYBASE_API_KEY" | jq .Returns { "currencies": ["usdttrc20", "btc", "eth", "sol", ...] }.
Default: usdttrc20 (USDT on Tron ā fast, low fees).
curl -s -X POST "$PROXYBASE_API_URL/orders" \
-H "X-API-Key: $PROXYBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"package_id":"PACKAGE_ID","pay_currency":"usdttrc20"}' | jq .Parameters:
package_id (required) ā from list packagespay_currency (optional) ā default usdttrc20callback_url (optional) ā webhook URL for status notificationsReturns: order_id, payment_id, pay_address, pay_amount, pay_currency,
price_usd, status, expiration_estimate_date.
curl -s "$PROXYBASE_API_URL/orders/ORDER_ID/status" \
-H "X-API-Key: $PROXYBASE_API_KEY" | jq .Status progression:
payment_pending ā confirming ā paid ā proxy_active ā bandwidth_exhausted
When proxy_active, the response includes:
{
"status": "proxy_active",
"proxy": {
"host": "api.proxybase.xyz",
"port": 1080,
"username": "pb_xxxx",
"password": "xxxx"
},
"bandwidth_used": 52428800,
"bandwidth_total": 1073741824
}curl -s -X POST "$PROXYBASE_API_URL/orders/ORDER_ID/topup" \
-H "X-API-Key: $PROXYBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"package_id":"PACKAGE_ID","pay_currency":"usdttrc20"}' | jq .Returns same shape as create order. Bandwidth is additive ā same credentials,
same proxy, more bandwidth.
curl -s -X POST "$PROXYBASE_API_URL/orders/ORDER_ID/rotate" \
-H "X-API-Key: $PROXYBASE_API_KEY" | jq .Returns { "order_id": "...", "message": "...", "rotated": true }.
The next connection gets a fresh IP. Existing connections are unaffected.
source {baseDir}/state/credentials.env 2>/dev/nullsource {baseDir}/scripts/proxybase-register.sh if no keyPOST /orders with chosen package + currencypay_address, pay_amount, pay_currency, and expiration_estimate_dateproxy_active, expired, or failedFor a streamlined flow, use the provided scripts:
Create order and track it:
bash {baseDir}/scripts/proxybase-order.sh us_residential_1gb usdttrc20Poll an order until terminal state:
bash {baseDir}/scripts/proxybase-poll.sh ORDER_IDCheck all tracked orders:
bash {baseDir}/scripts/proxybase-status.shClean up expired/failed orders:
bash {baseDir}/scripts/proxybase-status.sh --cleanupTop up bandwidth on an active order:
bash {baseDir}/scripts/proxybase-topup.sh ORDER_ID us_residential_1gbRotate proxy credentials (new IP):
bash {baseDir}/scripts/proxybase-rotate.sh ORDER_IDPoll with extended timeout (for slow BTC confirmations):
bash {baseDir}/scripts/proxybase-poll.sh ORDER_ID --max-attempts 200After order creation, the flow must pause for crypto payment.
Set up a cron job to poll every 30 seconds:
{
"name": "proxybase-poll-ORDER_ID",
"schedule": { "kind": "every", "everyMs": 30000 },
"sessionTarget": "isolated",
"payload": {
"kind": "agentTurn",
"message": "Run: bash {baseDir}/scripts/proxybase-poll.sh ORDER_ID\nIf proxy_active, announce the SOCKS5 credentials to the user and delete this cron job. If expired or failed, announce the failure and delete this cron job. If still pending or confirming, reply with NO_REPLY."
},
"delivery": { "mode": "announce", "channel": "last" },
"deleteAfterRun": false
}Tell the user: "Let me know when you've sent the payment and I'll check the status."
When they say they paid:
bash {baseDir}/scripts/proxybase-poll.sh ORDER_IDPass callback_url when creating the order:
curl -s -X POST "$PROXYBASE_API_URL/orders" \
-H "X-API-Key: $PROXYBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"package_id":"PACKAGE_ID","pay_currency":"usdttrc20","callback_url":"https://your-gateway/hooks/proxybase"}'ProxyBase sends status updates to the webhook. Always combine with cron polling as backup.
source {baseDir}/state/.proxy-env
# Now all curl/wget commands go through the proxy automatically
curl https://httpbin.org/ipOr manually:
export ALL_PROXY="socks5://USERNAME:PASSWORD@api.proxybase.xyz:1080"
export HTTPS_PROXY="socks5://USERNAME:PASSWORD@api.proxybase.xyz:1080"
export NO_PROXY="localhost,127.0.0.1,api.proxybase.xyz"curl --proxy socks5://USERNAME:PASSWORD@api.proxybase.xyz:1080 https://httpbin.org/ipimport requests
proxies = {"https": "socks5://USERNAME:PASSWORD@api.proxybase.xyz:1080"}
r = requests.get("https://httpbin.org/ip", proxies=proxies)
print(r.text)# Direct IP
curl -s https://httpbin.org/ip | jq .origin
# Proxied IP (should be different)
curl -s --proxy socks5://USERNAME:PASSWORD@api.proxybase.xyz:1080 https://httpbin.org/ip | jq .origin| Error | Meaning | Action |
|---|---|---|
| 401 Unauthorized | API key invalid or missing | Re-register: source {baseDir}/scripts/proxybase-register.sh |
| 404 Not Found | Order ID invalid | Check order ID, remove from tracking |
| 429 Too Many Requests | Rate limited | Wait 5-10s and retry, max 3 attempts |
| 500/502/503 | Server error | Retry up to 3 times with 5s delay |
| partially_paid | Underpayment | Tell user the remaining amount; keep polling |
| expired | Payment window closed (~24h) | Create new order |
| failed | Payment error | Create new order, log for support |
| bandwidth_exhausted | All bandwidth used | Top up: POST /orders/{id}/topup |
callback_url providedapi_key or proxy passwords in chat messages ā use env varsGenerated Mar 1, 2026
AI agents can use residential proxies to scrape e-commerce sites, social media, and news outlets without triggering IP bans, enabling real-time competitive analysis and trend monitoring. This is ideal for gathering pricing data, product reviews, and consumer sentiment across US markets while maintaining anonymity.
Proxies allow AI agents to simulate user interactions from various US residential IPs to verify ad placements, check for fraudulent clicks, and ensure compliance with advertising campaigns. This helps digital marketing agencies and advertisers audit ad performance and detect bot traffic effectively.
AI agents can manage multiple social media accounts, schedule posts, and analyze engagement metrics using rotating residential IPs to avoid platform restrictions and shadow bans. This supports influencers, brands, and agencies in maintaining authentic online presence across platforms like Twitter, Instagram, and Facebook.
Security teams employ AI agents with residential proxies to conduct ethical hacking and vulnerability assessments from diverse US IP addresses, mimicking real attacker behavior without revealing corporate infrastructure. This aids in identifying security weaknesses in web applications and networks.
AI agents scrape airline, hotel, and rental car websites using residential proxies to aggregate real-time pricing and availability data without being blocked. This enables travel agencies and booking platforms to offer competitive deals and dynamic pricing strategies to customers.
Offer tiered subscription plans (e.g., monthly or annual) providing access to residential proxies with varying bandwidth limits, targeting businesses that require consistent proxy usage for tasks like data scraping or ad verification. Revenue is generated through recurring fees based on usage tiers and additional features like IP rotation.
Charge users based on actual bandwidth consumption, allowing flexibility for occasional or variable proxy needs, such as one-off market research projects or seasonal advertising campaigns. This model appeals to startups and small businesses with fluctuating demands, minimizing upfront costs.
Partner with other software providers or agencies to resell proxy services under their own brand, integrating the API into their existing tools for data analytics or security solutions. This expands market reach through B2B partnerships and generates revenue via wholesale pricing and licensing fees.
š¬ Integration Tip
Ensure the PROXYBASE_API_KEY is securely stored in environment variables and use the provided helper scripts to automate order creation and polling, simplifying the payment and proxy delivery process for seamless integration.
Connect Claude to Clawdbot instantly and keep it connected 24/7. Run after setup to link your subscription, then auto-refreshes tokens forever.
ERC-8004 Trustless Agents - Register, discover, and build reputation for AI agents on Ethereum. Use when registering agents on-chain, querying agent registries, giving/receiving reputation feedback, or interacting with the AI agent trust layer.
Autonomous crypto trading on Base via Bankr. Use for trading tokens, monitoring launches, executing strategies, or managing a trading portfolio. Triggers on "trade", "buy", "sell", "launch", "snipe", "profit", "PnL", "portfolio balance", or any crypto trading task on Base.
Deploy ERC20 tokens on Base using Clanker SDK. Create tokens with built-in Uniswap V4 liquidity pools. Supports Base mainnet and Sepolia testnet. Requires PRIVATE_KEY in config.
Query DeFi portfolio data across 50+ chains via Zapper's GraphQL API. Use when the user wants to check wallet balances, DeFi positions, NFT holdings, token prices, or transaction history. Supports Base, Ethereum, Polygon, Arbitrum, Optimism, and more. Requires ZAPPER_API_KEY.
Interact with Solana blockchain via Helius APIs. Create/manage wallets, check balances (SOL + tokens), send transactions, swap tokens via Jupiter, and monitor addresses. Use for any Solana blockchain operation, crypto wallet management, token transfers, DeFi swaps, or portfolio tracking.