When executing endpoints or running workflows, you have the option to use shared or dedicated proxies to run the requests on. So what's the difference?

Shared Proxies

Stevesie Data maintains a dynamic pool of proxies running on datacenter IP addresses we offer to our users. They are available in eight locations around the world and the IP addresses are rotated multiple times each day. These are best for:

  • Anonymous or unauthenticated requests

  • On-demand requests triggered from end-users

  • Realtime requirements

Since these proxies are always available, you don't need to wait to launch one & can use them immediately.


You pay per request when using shared proxies (either when executing an endpoint or running a workflow) at a price of $0.0010 usage credits per request.

Dedicated Proxies

If you need to make a lot of requests over a short period of time (such as when using workflow) and/or need a consistent IP address to perform authenticated (or session-based) requests from, you may rent a dedicated proxy from Stevesie Data at the price of $0.0750 per hour, rounded up to the nearest hour. Dedicated proxies work best for:

  • Batch processing (over 75 requests per hour)

  • Dedicated IP to mimic a session or authenticated user

You'll typically be using a dedicated proxy when you launch a workflow (the default option is to launch a new dedicated proxy for each workflow run and then terminate the proxy automatically upon completion).

Traffic Interception

Dedicated proxies also allow you to intercept your own network traffic and view what your apps send & receive to and from servers, allowing you to uncover unofficial API endpoints.

To intercept your own SSL traffic, go to the Proxies Page and click on the link underneath "Intercept Port" for any running proxy. Be sure to launch a dedicated proxy if you don't have one running.

Did this answer your question?