Solutions describe the problem. These are the jobs — from a one-time collection to a live search API inside your own product.
Featured use case
Query external sources on demand and get structured results back.
Your system sends a name, an ID, or a case number. NexqData runs it across every source in a group and hands back structured results — a search endpoint over sources that never had one.
curl -X POST "$NEXQDATA_API/api/search-groups/$GROUP_ID/run" \
-H "X-Api-Key: $NEXQDATA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"inputParameters": "{\"LastName\":\"Doe\",\"FirstName\":\"Jane\"}"}'
# → { "success": true, "data": { "groupRunId": "5b0c…", "memberCount": 38 } }curl "$NEXQDATA_API/api/search-groups/runs/$GROUP_RUN_ID" \
-H "X-Api-Key: $NEXQDATA_API_KEY"curl "$NEXQDATA_API/api/scraper-agents/group-runs/$GROUP_RUN_ID/export" \
-H "X-Api-Key: $NEXQDATA_API_KEY" -o results.zipMore ways teams use it
Every use case runs on the agents our engineers build for your sources. What changes is how you run them and where the data goes.
Turn difficult websites into reliable structured datasets.
An agent engineered for each source, run whenever you need it, returning validated, structured records instead of pages to parse.
Continuously collect and refresh datasets.
Put any agent, group, or pipeline on a cron or interval schedule in your timezone. Each run lands as a fresh dataset you can pull through the API or export.
Catch new records, changes, and updates.
Re-collect a source on a schedule and keep every run. Compare the latest run with earlier ones in your own systems to see what appeared, changed, or disappeared — with failed or unusual runs flagged as they happen.
Add information from external sources to records you already have.
Send fields from your own records — a name, a company number, a license ID — as an agent's inputs, and attach what comes back to the record it came from.
Collect the same kind of record from many sources at once.
Group agents that cover the same kind of record — every county, every state board — and run them together with one set of inputs. Each source finishes on its own, and the results come back as one bundle with a file per source.
Collect, validate, and deliver — in order, as one run.
Chain agents into ordered stages that run as one: each stage starts only after the last succeeds, a failure stops the chain where it happened, and every stage's output downloads together.
A feed, a search endpoint, a monitoring job — describe the sources and the shape of the output, and an engineer will scope it with you.