Save the configuration
Choose an operation in the workbench, enter its inputs and give the saved request a name you will recognize. Saving keeps the operation and its parameters in your account. It does not run the request, reserve credits or save an API key.
A saved request is a reusable configuration, not a stored response, a schedule or a collection. Your account can keep up to 100 saved requests. Delete configurations you no longer need to make room.
Open, review, then run
Open Saved requests and select the configuration. The workbench loads its inputs so you can review the URL or query, locale and credit cost. Nothing runs merely because you opened it. Choose Run when you want fresh results.
Source content and search results can change between runs. Check the response each time and retain its source evidence when you export it. A successful repeat request uses credits normally.
Keep credentials out of names and URLs
The generated code reads your API key from a server environment variable. Do not paste a key or password into a saved request name, query or target URL. Use public sources that do not require login credentials.
If you need the whole account’s stored metadata, use the account export. For collected page content, download the corresponding collection before it expires.