Dolphin Anty Integration

Dolphin Anty team accounts — each profile exits through a unique residential IP

Dolphin Anty's cloud-synced profiles and team sharing make multi-account operations scalable. BytesFlows adds the critical IP layer: every profile gets its own residential exit — isolated by country, city, or ISP.

Dolphin Anty profiles: with vs without residential proxy

Even with perfect browser fingerprint isolation, accounts can be linked if they share IP ranges or ASNs.

Feature
Without Proxy / VPN
With BytesFlows Residential
Exit IP per profile
Shared or VPN datacenter
Unique residential IP each
Team member IP isolation
Same office/VPN IP visible
Each team member uses own sub-user
Platform ban risk
High — IP clustering detectable
Low — genuine residential traffic
Geo-specific local behavior
Timezone/IP mismatch flags
IP matches profile locale

Add BytesFlows proxy to Dolphin Anty profiles

Configure in the Dolphin Anty desktop app. One sub-user per profile for complete team isolation.

  1. 1

    Create BytesFlows sub-users for your team

    In BytesFlows dashboard → Residential → Sub-users, create one sub-user per team member or per profile slot. Name them descriptively (e.g., "agent-us-01") for easy management.

  2. 2

    Open Dolphin Anty and navigate to a profile

    In Dolphin Anty, click "New Profile" or select an existing one. Go to the Proxy section within the profile settings.

  3. 3

    Set proxy type to HTTP and enter credentials

    Choose HTTP proxy type. Host: p1.bytesflows.com, Port: 8001. Enter the BytesFlows sub-user credentials. Optionally append geo to username: -cc-US, -cc-GB, or -cc-US-city-miami.

  4. 4

    Check proxy and confirm residential ISP

    Click "Check proxy" in Dolphin Anty. Verify the displayed ISP is a home broadband provider (e.g., Comcast, AT&T, BT), not a datacenter. This confirms the residential routing.

  5. 5

    Save profile and share with team

    Save the profile. If using Dolphin Anty cloud sync, the proxy credentials are stored in the profile and shared with all team members who have access — they'll all use the same BytesFlows credentials for that profile.

Built for Dolphin Anty team workflows

1

Dolphin Anty automation API compatible

BytesFlows proxies work with the Dolphin Anty REST API for programmatic profile creation. Inject proxy parameters when creating profiles via API for automated large-scale multi-account setups.

2

Cloud profile proxy persistence

Proxy credentials saved in a Dolphin Anty cloud profile persist across team member sessions. A profile always uses the same BytesFlows sub-user — maintaining IP consistency across launches.

3

City-level geo targeting

Match your Dolphin Anty profile's timezone and locale settings to a specific BytesFlows city IP. Append -cc-US-city-houston to the username for a Houston residential IP that aligns with a US Central timezone profile.

Dolphin Anty + proxy FAQ

Does Dolphin Anty support SOCKS5 proxies?
Yes. In the profile proxy settings, select SOCKS5 as the proxy type and use port 1080 with the same BytesFlows sub-user credentials. SOCKS5 is preferred for full traffic tunneling without HTTP header modification.
How do I manage proxies for 100+ Dolphin Anty profiles?
Use the Dolphin Anty automation API. Create BytesFlows sub-users in bulk via the BytesFlows dashboard (there's no creation limit), then use the API to create Dolphin Anty profiles with different sub-user credentials. This can be scripted in Python or Node.js for one-command setup of large profile sets.
Can different team members in Dolphin Anty use different BytesFlows sub-users?
Yes. If each team member creates their own set of profiles, they can each use their own BytesFlows sub-users — getting fully isolated IP pools. Alternatively, profiles can be centrally managed with shared credentials where IP consistency across team members is preferred over per-member isolation.

Scale Dolphin Anty operations with residential IPs

1 GB free residential traffic — test with your Dolphin Anty team workflow before committing.