Setting up an IN endpoint
Generate credentials in the dashboard, set country to IN (and a city if the job needs one), then paste the endpoint into your browser profile or script. SOCKS5 and HTTP(S) share the same login, so switching protocol never means re-buying an IP. Use code OPEN30 on the first order.
India coverage at a glance
| Attribute | 922 S5 in India |
|---|---|
| Pool | Part of the 350M+ residential network |
| Cities | Mumbai, Delhi, Bangalore, Hyderabad, Chennai and more |
| Carriers | Jio, Airtel, BSNL, ACT |
| Protocols | SOCKS5 / HTTP / HTTPS |
| Billing | Per IP — balance never expires |
| Checkout | Crypto, no KYC |
Why operators pick IN per-IP
Per-IP billing wins in India work where one identity maps to one account. You buy an IN address, assign it to a profile, and it stays yours — no bandwidth meter running in the background while the profile idles.
- Antidetect profiles — one India IP per browser profile, held for weeks.
- Marketplace accounts — IN sellers and buyers kept on separate lines.
- Drop and release monitoring — Mumbai and Delhi exits for regional launches.
- Localized QA — verify what a India shopper sees before a campaign ships.
Frequently asked questions
How much is one India IP?
922 S5 sells IN addresses per IP starting at $0.07/IP, and volume tiers lower the unit price. Bought IPs stay on your balance indefinitely.
Can I keep the same India IP for a profile?
Yes. That is the point of per-IP billing — assign one IN address to one antidetect profile and reuse it as long as the profile lives.
Which India cities are available?
Mumbai, Delhi, Bangalore, Hyderabad, Chennai and additional metros. City selection is part of the credential, so several IN cities can run at once.
Do you require KYC for India proxies?
No. Registration is email-only and checkout is crypto — USDT, BTC, LTC and others. Access activates once the payment confirms on-chain.