Live search

Turn difficult websites into APIs.

Search courts, registries, portals, and other complex sources from your own application. You send the inputs you have; we run the agents built for each source and hand back structured results.

Talk to an engineer See all use cases →

How a search runs

Request. Execution. Result. Response.

01
Request
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.
02
Execution
NexqData runs the agent engineered for each source. Sources run independently, so one slow portal never holds up the rest.
03
Structured result
Each source returns records in the fields agreed when its agent was scoped — not pages of HTML to parse.
04
API response
Your application retrieves the results through the API, with a status for every source so you know exactly which ones answered.

Example

One request in. Structured records out.

Name a group of sources instead of a single agent, and the same request searches every one of them.

Request

http

POST /search

{
  "agent": "court-records-tx",
  "input": {
    "firstName": "John",
    "lastName": "Doe",
    "dob": "1990-01-01"
  }
}

Response

json

{
  "searchId": "srch_7c1e2f04",
  "status": "completed",
  "sources": [
    {
      "source": "court-records-tx",
      "status": "completed",
      "records": [
        {
          "caseNumber": "2026-0418823",
          "court": "District Court 190",
          "filed": "2026-09-22",
          "caseStatus": "Open",
          "party": {
            "firstName": "John",
            "lastName": "Doe",
            "dob": "1990-01-01"
          }
        }
      ]
    }
  ]
}

Illustrative. Endpoint names, input fields, and the shape of each source’s records are agreed with you when we scope your agents.

Built for on-demand questions