One API.
Multiple countries.
Simple global routing.
Send HTTP and HTTPS requests from South Africa, the UK, the US and more with a single API key. Pick the exit country per request — Frescoa runs the servers, health checks, metering and limits.
1 GB free every month. No card required.
curl -x http://proxy.frescoa.com:8080 \
-U "country-za:YOUR_API_KEY" \
https://api.ipify.org?format=jsonHow it works
Point any HTTP client at one endpoint. Put the country in the proxy username. That's the whole integration.
- 1Authenticate
Your API key is checked, along with your plan, allowance and rate limits.
- 2Choose a node
A healthy exit node in the country you asked for is selected — sticky per session if you want.
- 3Tunnel
HTTPS travels end-to-end encrypted through a CONNECT tunnel. We never decrypt it.
- 4Meter
Upload and download bytes are counted per key and per country, visible in your dashboard within seconds.
Live country network
Every exit IP is validated against three independent geolocation databases before it carries traffic. If a country is unavailable you get a clear error — never a silent detour through somewhere else.
Built for legitimate geographic workloads
Geo-specific product testing
See exactly what a visitor in Johannesburg, London or New Jersey sees — pricing, content, redirects and consent banners.
QA & release verification
Run your integration and end-to-end suites from the countries your users are in, straight from CI.
International availability monitoring
Check that your sites and APIs are reachable and fast from each market — not just from your own region.
Country-aware applications
Build features that need connectivity from a specific country without running servers there yourself.
Geographic verification
Verify ad placements, localisation and geo-restrictions behave as intended in each jurisdiction.
Authorised data access
Market-intelligence teams collecting data they're permitted to access, from the region it's served to.
Secure by design — never an open proxy
Frescoa is infrastructure for accountable developers. Every connection is authenticated, attributed to an account and subject to limits and our acceptable-use policy.
HTTPS is tunnelled with CONNECT and stays end-to-end encrypted between you and the destination.
Private, loopback, link-local and cloud-metadata ranges are blocked — re-checked on the exit node after DNS resolution.
Every request needs a valid API key. Keys are hashed at rest and can be revoked instantly.
Per-account bandwidth, rate and concurrency limits, anomaly detection, and a human abuse desk.
Simple, bandwidth-based pricing
Pay for the gigabytes you route. Every plan includes every live country.
Route your first request in two minutes.
Create an account, copy your key, add one flag to curl.