Publisher SDK · Android 1.3.2 · MIT

A bandwidth-sharing SDK for apps built for sharing

The PROXIES.SX Android SDK lets an app share a device's connection with the peer network, with the user's consent, and credits the traffic to the publisher's farmer account. It is open source, version 1.3.2, for Android 7.0 and later. Store rules decide where it can ship, so start with the table below.

Registration does not guarantee traffic or earnings. Earnings depend on eligible traffic your devices actually serve and on your active partner terms.

This page covers the Android SDK only, version 1.3.2. The desktop and server peer for Windows and Linux, which also runs on macOS from its Node.js or Go source, is separate software with its own version numbers; its current downloads and checksums are at agents.proxies.sx/peer/.

Checked on against our published supplier terms

Where it can and cannot ship

Checked on 27 September 2026. Per-store quotes, dates and sources are in the store-policy registry.
Distribution eligibility
ChannelStatusWhat applies
Google PlayPrimary purpose onlyProxy services for third parties only where that is the app's primary, user-facing core purpose. Google has used Play Protect to warn about and remove apps carrying some proxy SDKs; plan for rejection risk.
Other stores and sideloaded APKsDeveloper verificationAndroid developer verification starts on 30 September 2026 for installs from participating stores in Brazil, Indonesia, Singapore and Thailand on certified Android 7+ devices; Google plans to extend it to all apps on certified devices in 2027, with an advanced flow for sideloading from unverified developers.
Pre-installed on consumer devicesNot supportedNo pre-install or device-bundling programme is published.
TV platforms, iOS, browser extensionsNot supportedNo SDK is published for these platforms.

Store policies for proxy SDKs, platform by platform

What the SDK is

Coordinate
com.github.bolivian-peru:android-peer-sdk:1.3.2
Licence
MIT, source on GitHub
Android
minSdk 24 (Android 7.0), targetSdk 34
Status
Beta; the API surface may change
Size
139,110 bytes (AAR, before dependencies)
Runs as
A dataSync foreground service with a notification
Credentials
AES-256-GCM through the Android Keystore
Not included
Consent UI, bandwidth caps, on-demand IP rotation

How it works

Peer traffic pathCustomer application to PROXIES.SX gateway to regional relay, then through an outbound WebSocket to your device, which opens the connection to the destination website.Customer appHTTP or SOCKS5Gatewaygw.proxies.sxRegional relayEU and USYour devicephone, Linux, PCWebsitethe destinationoutbound WebSocketJWT, heartbeat 30 sEach customer session is a tunnel_connect TCP tunnel. HTTPS stays encrypted end to end; plain HTTP does not.
The SDK keeps an outbound WebSocket to a regional relay and opens customer TCP tunnels from the device. It honours relay redirects only to *.proxies.sx.

Integrate it

The full walkthrough, API and permissions are on the Android integration page.
Gradle (Kotlin DSL)
// settings.gradle.kts
dependencyResolutionManagement {
    repositories {
        google()
        mavenCentral()
        maven { url = uri("https://jitpack.io") }
    }
}

// app/build.gradle.kts
dependencies {
    implementation("com.github.bolivian-peru:android-peer-sdk:1.3.2")
}

Compared with other bandwidth SDKs

Figures are what each source states; we have not verified other vendors' payouts and publish no per-user figure of our own.
Bandwidth SDKs compared
SDKAccessPay model as statedSource
PROXIES.SXOpen source (MIT), key from the farmer dashboardPer partner terms; live earningsPerGB, no public rateSupplier contract
Infatica SDKPartnership form; "50,000+ monthly active users""We pay per active user per month, up to 60 cents per user"infatica-sdk.io
Honeygain SDKSelf-service, code after registration$100 to $400 per 1,000 DAU a month in top regions (third-party estimate)Proxyway, 16 Dec 2025
Bright SDKPartnership or enterprise agreement$100 to $350 per 1,000 IPs a month (third-party estimate)Proxyway, 16 Dec 2025

Questions

What is a bandwidth-sharing SDK?
A library an app includes so that, with the user's consent, the device can carry proxy traffic for a network's customers. The PROXIES.SX Android SDK runs as a foreground service in the host app and links the device to the publisher's farmer account through an API key.
Can I put it in a game or a utility app on Google Play?
Google Play's Device and Network Abuse policy says apps that facilitate proxy services to third parties may only do so where that is the primary, user-facing core purpose of the app. A game or general utility does not meet that. Google has also used Play Protect to warn about and remove apps carrying some proxy SDKs, and it tells consumers to be wary of apps that pay for unused bandwidth, so plan for rejection risk even for an app built for sharing.
Is there an iOS SDK?
Not today. The SDK on this page is for Android only. The desktop and server peer for Windows and Linux, which also runs on macOS from its Node.js or Go source, is separate software with its own version numbers, published at agents.proxies.sx/peer/.
Does the SDK show a consent screen?
No. SDK 1.3.2 ships no consent or disclosure UI. The publisher must build an in-app disclosure and obtain the user's consent before sharing starts; Google Play's prominent disclosure guidance describes what that looks like.
How are publishers paid?
Earnings are credited to the farmer account that owns the API key, at the rate in that account's partner terms; there is no public rate. Registration does not guarantee traffic or earnings. Through the device withdrawal API the minimum for Android SDK devices is $10.00.
How big is it?
The 1.3.2 AAR is 139,110 bytes before dependencies. It depends on OkHttp, Gson, AppCompat, WorkManager, AndroidX Security and NanoHTTPD, so the effect on your APK depends on what you already include.

Building an app whose purpose is sharing?

Create an SDK key in the farmer dashboard, integrate one test build, and check the device registers and is verified before release.

Sources