/desearch/people/tasks/{task_id}/resultsQualified profiles found so far, in the order they were found. Results arrive while the search is still running: keep the returned `next_cursor` and call again to get only new profiles. Free. Billing metadata: successful billable responses include the `X-Desearch-Cost-Usd`, `X-Desearch-Usage-Count`, `X-Desearch-Service`, and `X-Desearch-Currency` headers. JSON object responses also include optional `cost_usd`, `usage_count`, `service`, and `currency` fields. For example, `usage_count=10` at `$0.015 / 1,000` resolves to `cost_usd=0.00015`. JSON arrays, text, and streaming responses keep their body shape and expose billing metadata only through headers.
Base URL
https://api.desearch.aiUse Read People Search results when your application needs scored public profiles of people and creatorswithout maintaining its own crawler, social-data pipeline, or retrieval infrastructure. The endpoint returns structured data that can be consumed by agents, research tools, dashboards, and retrieval-augmented generation workflows. Keep the request focused on the minimum fields your workflow needs so responses remain fast and easy to validate.
Send requests to GET /desearch/people/tasks/{task_id}/results with your Desearch API key in the authorization header. Treat the key as a server-side secret, validate all required parameters before sending the request, and handle non-2xx responses explicitly. Production integrations should use sensible timeouts, retry only transient failures with backoff, and record the response status and request identifier for troubleshooting.
Test the example request below before integrating it into a larger workflow. Confirm that the returned fields, links, and timestamps meet your freshness requirements, then add schema validation at the application boundary. For agentic systems, preserve source URLs with the generated answer so users can inspect evidence and your application can avoid presenting unsupported claims.
task_idstringrequiredThe task_id returned when the search was created
cursorstringnext_cursor from the previous page
limitintegerDefault: 100
Your API key is sent in the Authorization header.
curl -X GET "https://api.desearch.ai/desearch/people/tasks/3f1c2b9e-8d4a-4c1e-9b7a-2e5f6a7b8c9d/results" \
-H "Authorization: YOUR_API_KEY" \
-H "Content-Type: application/json"{
"task_id": "Task Id",
"status": "queued",
"results": [
{
"id": "Id",
"platform": "x",
"handle": "Handle",
"url": "string",
"name": "string",
"avatar_url": "string",
"bio": "string",
"location": "string",
"metrics": {},
"links": [
{}
],
"contacts": [
{}
],
"evidence": [
{
"type": "Type",
"url": "string",
"text": "string",
"title": "string",
"published_at": "string",
"metrics": {}
}
],
"score": {
"value": 0,
"qualified": true,
"summary": "string",
"matched_signals": [
"string"
],
"profile_fit": [
"string"
],
"buying_triggers": [
"string"
],
"evidence": [
"string"
],
"reasons": [
"string"
],
"concerns": [
"string"
]
},
"attributes": {}
}
],
"next_cursor": "Next Cursor",
"has_more": true
}Possible status codes: