/network/stats/historyReturns a one-second timeline for the latest 20 minutes so clients can hydrate a recent activity buffer before following the live stream. The current source is explicitly identified as an estimate.
Base URL
https://api.desearch.aiUse Get the latest 20 minutes of network stats when your application needs search-grounded AI resultswithout 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 /network/stats/history 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.
Your API key is sent in the Authorization header.
curl -X GET "https://api.desearch.ai/network/stats/history" \
-H "Authorization: YOUR_API_KEY" \
-H "Content-Type: application/json"{
"window_seconds": 0,
"interval_seconds": 0,
"window_started_at": "2024-01-15T10:30:00Z",
"window_ended_at": "2024-01-15T10:30:00Z",
"points": [
{
"total_searchable_pages": 0,
"searches_completed_today": 0,
"urls_crawled_today": 0,
"observed_at": "2024-01-15T10:30:00Z",
"telemetry_kind": "estimated",
"methodology": "fixed_rate_projection"
}
]
}Possible status codes: