Run the safe first request
Check account balances to confirm that your API key works before running traffic-consuming requests.
What You Can Do
Automate a Cloud Browser
Start a browser, connect over CDP, and reuse saved identity and browser state.
Search and Fetch Web Data
Discover relevant public pages, then fetch rendered HTML from a target URL.
Build proxy connections
Generate copy-paste rotating proxy URLs for HTTP clients, browser profiles, and automation tools.
Use static proxies
List assigned static proxies and copy their ready-to-use connection strings.
Track usage and balance
Read account-level and product-level balance and usage rollups.
How the Pieces Fit
A Calm First Path
1
Create an API key
Open API keys, create or copy a Client API key, and keep it out of proxy connection strings.
2
Confirm access
Run
GET /v2/account/balances. It is the easiest way to check that the key is valid.3
Pick one workflow
Choose Cloud Browser for browser automation, Web Data to search for pages or fetch rendered HTML, or proxy connections if your own client will make the request through a proxy.
4
Copy the returned value
For proxies, use the returned
connection.connectionString instead of rebuilding credentials by hand.5
Watch usage
Use usage endpoints for
yesterday, last7Days, last30Days, and optional requestedRange reporting.Quickstart
Make the first useful v2 calls.
Use MCP
Give MCP-compatible agents Floppydata tools with one API key.
API Reference playground
Run live requests directly from endpoint pages.