Amapa proxies exit from a residential IP inside Amapa, so the target site sees a local visitor rather than a datacenter. That matters wherever the answer changes by region — local search results, geo-priced listings, ads served to Amapa audiences, and any site that treats out-of-region traffic as suspicious. The pool is addressable by state and by city, so you can be as specific as the target actually checks.
Target Amapa
State_country-br_state-amapa
City e.g._country-br_state-amapa_city-macapa
Append the token to your proxy password. Nothing else changes — same endpoint, same port. Any of the 3 cities below works in place of the example.
Yes. The residential pool is addressable down to Amapa and to 3 of its cities. Add _country-br_state-amapa to your proxy password and every request exits from Amapa.
How do I target a specific city in Amapa?›
Append a city token to the state token, for example _country-br_state-amapa_city-macapa. City targeting narrows the pool, so use it when the target site actually checks the city and the state token when it does not.
Which proxy type works in Amapa?›
Residential is the one addressable by state — those are real Brazil consumer IPs. Datacenter, mobile and ISP are available for Brazil as a whole; mobile carries the highest trust, ISP gives you a static IP for long sessions.
What do Amapa proxies cost?›
Per gigabyte from your Eveses wallet, on a volume ladder — the more you use, the lower the rate. Targeting Amapa, or any city inside it, costs nothing extra.
We add countries, rotate pools and ship API changes most weeks. Drop your email and we'll send the ones worth knowing about — new geo coverage, price-ladder changes and anything that breaks an integration.
✓ New geos & products⚡ Breaking API changes🫥 No spam, ever
Unsubscribe with one click. We never share your email.