Usage credits are used to purchase proxy & processing resources used to collect data. There is no direct relationship between usage credits and data collected - how much data you can collect from your usage credits depends on your usage of the platform and what third-party API you are using.
Specifically, usage credits can purchase either:
On-demand requests to third party APIs
Dedicated proxy hours, where you pay by the hour for a dedicated proxy and can then make unlimited requests on that proxy while you have exclusive ownership.
Let's say you want to search for Tweets using the Twitter API Tweet Search Endpoint to just experiment, collect some light data, or integrate the response from this endpoint into a custom app on-demand.
You can make these requests one at a time at a price of $0.0010 usage credits per request. You can either make the request on our web platform and download the results in CSV format for easy use, or use the API to trigger requests for another app to display or consume.
By default, on-demand requests run on our shared proxy pool, from where you can select from one of eight locations across the world to make the request from.
These requests will be shared with other users and the IP address will be different for each request. The price of $0.0010 covers the cost for both processing the request and using our shared proxy pool.
If you have your own proxy that you'd like to use, you can use this instead and receive a 50% discount for on-demand requests. On the endpoint execution screen, just select custom under proxy type and enter your proxy URL.
The price will now only be $0.0050 to process your request via our API.
For cases where you need to collect a lot of data in bulk, you're better off paying for proxies by the hour. In this case, you pay $0.0750 usage credits for one hour of reserved proxy time (no one else will have access to your proxy), and you can make as many requests as you'd like on that one proxy (up to 1 request per second).
You will most likely want to use dedicated proxies with workflows. When you execute a workflow, the default behavior is to launch a dedicated proxy for the duration of the workflow and then auto-terminate the proxy when the workflow is finished.