Scheduled collection
PeriodicAgents run on a schedule and refresh a dataset. You query your copy, which is as fresh as the last run.
Best for: Feeds, monitoring, full datasets
Scheduling on the platformSearch courts, registries, portals, and other complex sources from your own application — and get structured records back.
Watch a search
One request, three sources searched in parallel, one response. Illustrative — timings and records are examples.
Illustrative live search: your application sends one search request to NexqData, which searches three sources in parallel — a county court portal, a state business registry, and a licensing board that times out once and answers after a retry. Five records come back from the three sources, and NexqData returns them to your application in 7.1s with a 200 OK response.
How live search works
Four stages between your application asking and your application knowing.
Your application sends the inputs it has — a name, a date of birth, a case number — and which agent or group of sources to search.
NexqData runs the agent engineered for each source. Sources run independently, so one slow portal never holds up the rest.
Each source returns records in the fields agreed when its agent was scoped — not pages of HTML to parse.
Your application gets the results through the API, with a status for every source, so you know exactly which ones answered.
Multi-source
Name a group instead of a single agent, and the same request searches every source in it.
For developers
# Search a source — or a whole group — from your application$ time curl -s -X POST "$NEXQDATA_API/search" \> -H "X-Api-Key: $NEXQDATA_API_KEY" \> -H "Content-Type: application/json" \> -d '{"agent": "court-records-tx", "input": {"firstName": "John", "lastName": "Doe", "dob": "1990-01-01"}}' \> | jq{ "status": "completed", "sources": [ { "source": "court-records-tx", "status": "completed", "records": [ { "caseNumber": "2026-0418823", "court": "District Court 190", "filed": "2026-09-22", "caseStatus": "Open", "matchedOn": ["firstName", "lastName", "dob"] } ] } ]} real 0m7.104suser 0m0.021ssys 0m0.012s$ Illustrative. Endpoint names, input fields, and the shape of each source’s records are agreed with you when we scope your agents.
Scheduled or live
Both run the same engineered agents. The difference is how old the answer is when someone asks.
Agents run on a schedule and refresh a dataset. You query your copy, which is as fresh as the last run.
Best for: Feeds, monitoring, full datasets
Scheduling on the platformAgents run when you ask. The answer comes from the source at that moment, for the inputs you sent.
Best for: Screening, lookups, decisions made now
See the requestOn demand
Built for production
Every source gets its own agent, built around its forms, sessions, and quirks.
Learn more →Group agents that cover the same kind of record and search them all at once.
Learn more →Failed or unusual searches are flagged, and agents are updated when a source changes.
Learn more →Per-user API keys that can be scoped to specific permissions and revoked at any time.
Learn more →Tell us the sources and the inputs you have. We’ll scope the agents and the shape of the results with you.