Your list.
Enriched.
Within budget.
Turn CSV and JSON rows into API-powered data jobs. Map inputs, set a hard credit cap, and export the results.
| Domain | Status | Result |
|---|---|---|
| atlas.example | Completed | View data |
| north.example | Completed | View data |
| nova.example | Queued | — |
- Up to 10,000 seed rows per jobProcess larger lists with ease.
- Hard credit spending capsYou stay in control.
- CSV and JSONL exportsGet results in your preferred format.
Turn a company CSV into useful research.
Start with company names and domains on the left. Websets sends each domain to an enrichment API, adds the returned information, and stops before exceeding the cap. Review and download the completed sample rows on the right.
From your input to a useful result.
- Choose a sample input
- Apply the feature’s workflow
- Inspect the result
This example runs entirely in your browser with illustrative data. Use the real feature’s guide and listing to check supported inputs, access rules, and pricing.
Explore the example, then use the setup guide to try the real feature.
Project setup and what to check
Input: A CSV or JSON list, a compatible API route, and a hard credit cap. Begin with a few representative rows so you can inspect successful and unsuccessful results.
Workflow: Map the domain column to the route’s input. Run the job and review row results; the budget check happens before each dispatch and pauses the job if the next row would exceed the cap.
Result: A CSV or JSONL export for your CRM import, research notebook, or internal tool. Available enrichment fields depend on the API you selected.
Validate the column mapping and returned fields before processing the full list. Reserve room in the cap for applicable route and infrastructure charges.
From a spreadsheet to a usable dataset.
- 1
Upload your list
Add a CSV or JSON file with your rows.
- 2
Map your inputs
Match your columns to the API’s expected inputs.
- 3
Run and export
Set a credit cap, run your job, and download the results.
Column mapping example
Your input file (CSV)
| domain | company |
|---|---|
| atlas.example | Atlas Labs |
| north.example | Northwind Inc |
| nova.example | Nova Systems |
| orbit.example | Orbit Media |
| summit.example | Summit Tech |
Map to API inputs
from column domain
from column company
Result (enriched data)
| domain | company | Industry | location |
|---|---|---|---|
| atlas.example | Atlas Labs | Software | San Francisco, CA |
| north.example | Northwind Inc | Fintech | New York, NY |
| nova.example | Nova Systems | Hardware | Austin, TX |
| orbit.example | Orbit Media | Marketing | Seattle, WA |
| summit.example | Summit Tech | Software | Boston, MA |
Illustrative data. Available fields and required inputs depend on the selected API.
Inspect the sample CSV and mapping
domain,company
atlas.example,Atlas Labs
north.example,Northwind Inc
nova.example,Nova SystemsSource column → API input
domain → query.domain
company → body.company
Hard credit cap: 25 credits
Export format: CSV or JSONL
Required inputs depend on the selected API.Fictional companies and an illustrative 25-credit cap. A cap limits dispatches; it does not guarantee that every row will finish.
Set the limit before the job starts.
Websets checks worst-case route and add-on costs before dispatching each row. It pauses when the next request would exceed your remaining budget.
17 credits used
8 remaining
Next row cost checked before dispatch
Bulk API enrichment without running your own worker queue
A useful API becomes a different operational problem when you need to call it for thousands of leads, domains, SKUs, or URLs. Live Websets provides a managed batch workflow over marketplace APIs and the platform URL extractor. Upload your seed rows once and configure how each row becomes a request.
Your input list supplies the context for the job. Websets executes the selected route for those rows; it does not invent a prospect list or replace the underlying data provider. This makes the workflow suitable for repeatable enrichment, permitted web extraction, and structured exports that feed an existing spreadsheet or data pipeline.
Use the APIs that fit your dataset
Choose a marketplace route for a specific enrichment task, or the platform extractor for rows containing URLs.
How it works
A domain list can become an API input column; a product list can supply SKU or query values. Verify the chosen listing's required parameters and schema before scaling from a sample to the complete job.
Bind inputs without a custom integration script
Column mapping connects each seed row to the selected route's public inputs.
How it works
You can reuse the same API contract that appears in its playground, keeping request construction visible in the job configuration. The upstream vendor still determines the data returned and the valid combinations of inputs.
Pause before the next row exceeds your cap
The runner checks worst-case route, browser, CAPTCHA, and proxy charges before dispatching each row.
How it works
If the remaining budget cannot cover the next dispatch, processing pauses before that request is sent. A low cap can therefore pause a job even when some earlier requests settled below their worst-case estimate.
Move results into your existing workflow
Live progress and row outcomes help you understand a batch while it runs.
How it works
CSV suits spreadsheet review, while JSONL works well with stream-oriented data processing. Accounts can store up to 200,000 rows across jobs; plan exports and retained jobs around the limits shown in your dashboard.
Common ways to use Websets.
CRM enrichment
Upload a known list of company domains and call an enrichment route for each row. Review results before updating your CRM through its own import process.
Product data collection
Run permitted product URLs or SKUs through a listing or extraction endpoint and export the returned content for catalog research.
Research datasets
Process a defined set of public source URLs into structured outputs. Keep your seed identifiers so results can be traced back to the original inputs.
Start with a focused test.
Use these steps to set up Live Websets and review the result before making it part of a larger workflow.
Create a Webset →- 1
Upload your seed list
Create a Webset and upload CSV or JSON containing up to 10,000 rows. Begin with a small sample to check your inputs and the selected API's response.
- 2
Map columns and set a budget
Map row values into the route's path, query, header, or body inputs. Choose a maximum credit spend that includes the expected route and infrastructure costs.
- 3
Run, review, and export
Follow live job progress, pause or resume processing when needed, and download CSV or JSONL output for your next workflow.
Understand each job’s cost.
Match the feature’s limits and billing model to the work you want to run.
Explore API listings →A Webset uses the selected route's billing rules and any applicable infrastructure add-ons. The hard credit cap limits job dispatches; it does not make a paid API free or guarantee that every input row will finish within a chosen budget.
Test a small representative sample, review actual charges, and then choose the full-job cap. Failed calls follow the platform's refund rules, while successful calls already completed remain part of the job's spend.
Open an API listing for its Reference, Playground, and Pricing. Check the selected route’s allowances and applicable infrastructure charges before increasing usage.
FAQs
How many rows can I upload?
A job accepts up to 10,000 CSV or JSON seed rows, with up to 200,000 stored rows across an account's jobs. The dashboard shows applicable limits.
Can I use Websets with any marketplace API?
Websets can map inputs into marketplace routes and the platform extractor. Select a route whose public inputs and response suit your rows, and test its behavior before launching a large batch.
What happens when the budget is too low?
The job pauses before dispatching a row whose worst-case cost exceeds the remaining cap. Review the budget and job configuration before resuming. Previously completed paid calls remain charged.
Is a Webset the same as an API monitor?
No. A Webset processes a supplied batch of rows. A monitor repeatedly polls a configured route and sends a webhook when the tracked response changes.
Put your next dataset to work.
Turn your list into enriched data with a credit cap you control.