> ## Documentation Index
> Fetch the complete documentation index at: https://clair.im/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Response times

> How long each Clair endpoint takes, why, and what to set your client timeout to.

Every request is live: Clair loads the page when you ask, so the response time
is mostly the time the source site takes to hand over its data. Some sites
answer a plain request in a second or two. Others only show their data inside
a real browser, after a wait, a click, or a scroll. Those take longer on every
request, and that time is expected.

Each endpoint is labeled by how it loads, with the time most requests finish
in and the limit after which Clair stops and returns an error.

## How an endpoint loads

| Label | Most endpoints | What happens |
| - | - | - |
| Page fetch | 1–7 s | One request for the page, through a proxy network that gets past the site's bot checks. No browser. Usually a few seconds; a site that challenges the request takes longer. |
| Browser render | 10–20 s | The site builds the page with JavaScript or blocks plain requests, so a real browser opens it and waits for the content. Starting the browser and loading the page takes most of the time. |
| Browser with steps | 9–37 s | A real browser opens the page, then waits, clicks, or scrolls so the site loads the rest. Each step adds seconds, and they cannot run in parallel. |
| Live AI answer | 10–40 s | A real browser asks the AI product the question and waits until it has finished writing. The answer's length sets the time, not the network. |

## Reading the numbers

* **Typical** is the range most requests finish in, measured on live requests
  with nothing cached. A request inside it is working as intended.
* A request above the range but under the limit usually means the source site
  blocked the first try and Clair tried again a different way. This happens
  on a small share of requests to any site.
* **Limit** is where Clair stops. The request returns `504` and is not
  charged. Retry it.
* A repeated request can come back in milliseconds: Clair keeps a result for a
  short time and serves the same request from it.

Set your client timeout a few seconds above the endpoint's limit, so you get
Clair's error body and not a dropped connection. To get through a long list
faster, send requests in parallel within your plan's rate limit; one slow
request does not hold up the others. A `503` `overloaded` means the
endpoint is at capacity for the moment: wait a second and retry.

## Every endpoint

### Web Scraper API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/scrape` | Page fetch | 1–5 s | 60 s |

### Amazon API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/amazon/search` | Page fetch | 2–5 s | 60 s |
| `GET /v1/amazon/product` | Page fetch | 3–6 s | 60 s |
| `GET /v1/amazon/reviews` | Page fetch | 4–7 s | 60 s |
| `GET /v1/amazon/offers` | Page fetch | 2–4 s | 60 s |
| `GET /v1/amazon/lookup` | Page fetch | 2–4 s | 60 s |
| `GET /v1/amazon/seller` | Page fetch | 1–3 s | 60 s |
| `GET /v1/amazon/seller-products` | Page fetch | 2–4 s | 60 s |
| `GET /v1/amazon/bestsellers` | Page fetch | 1–3 s | 60 s |
| `GET /v1/amazon/categories` | Page fetch | 1–3 s | 60 s |

### Google Search API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/google-search` | Page fetch | 3–8 s | 60 s |

### Google Maps API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/google-maps/search` | Browser with steps | 9–15 s | 60 s |
| `GET /v1/google-maps/place` | Browser with steps | 13–17 s | 60 s |

### ChatGPT API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/chatgpt` | Live AI answer | 15–33 s | 90 s |

### Google AI Overview API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/google-ai-overview` | Live AI answer | 10–26 s | 75 s |

### Google AI Mode API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/google-ai-mode` | Live AI answer | 13–40 s | 85 s |

### YouTube API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/youtube/search` | Page fetch | 1–4 s | 40 s |
| `GET /v1/youtube/video` | Page fetch | 1–3 s | 40 s |
| `GET /v1/youtube/channel` | Page fetch | 1–4 s | 40 s |
| `GET /v1/youtube/comments` | Page fetch | 1–2 s | 40 s |
| `GET /v1/youtube/transcript` | Page fetch | 1–3 s | 50 s |

### TikTok API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/tiktok/video` | Page fetch | 1–3 s | 40 s |
| `GET /v1/tiktok/profile` | Page fetch | 1–3 s | 40 s |
| `GET /v1/tiktok/videos` | Browser with steps | 19–37 s | 60 s |
| `GET /v1/tiktok/hashtag` | Browser with steps | 22–37 s | 60 s |

### Instagram API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/instagram/post` | Page fetch | 1–4 s | 40 s |
| `GET /v1/instagram/profile` | Page fetch | 1–3 s | 40 s |
| `GET /v1/instagram/hashtag` | Page fetch | 1–3 s | 40 s |

### Glassdoor API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/glassdoor/jobs` | Page fetch | 2–6 s | 90 s |
| `GET /v1/glassdoor/job` | Browser render | 24–40 s | 70 s |
| `GET /v1/glassdoor/companies` | Page fetch | 2–7 s | 70 s |
| `GET /v1/glassdoor/company` | Page fetch | 1–22 s | 90 s |
| `GET /v1/glassdoor/salaries` | Page fetch | 1–38 s | 90 s |

### Indeed API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/indeed/jobs` | Page fetch | 3–7 s | 60 s |
| `GET /v1/indeed/job` | Page fetch | 2–6 s | 50 s |
| `GET /v1/indeed/companies` | Page fetch | 2–6 s | 50 s |
| `GET /v1/indeed/company` | Page fetch | 2–16 s | 50 s |
| `GET /v1/indeed/reviews` | Page fetch | 3–8 s | 50 s |

### Google News API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/google-news` | Page fetch | 2–6 s | 60 s |

### Google Shopping API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/google-shopping` | Page fetch | 3–7 s | 60 s |
| `GET /v1/google-shopping/product` | Browser with steps | 12–25 s | 80 s |

### Trustpilot API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/trustpilot/reviews` | Browser render | 10–20 s | 45 s |
| `GET /v1/trustpilot/search` | Browser render | 10–15 s | 45 s |
| `GET /v1/trustpilot/categories` | Browser render | 12–20 s | 45 s |
| `GET /v1/trustpilot/review` | Browser render | 12–20 s | 45 s |

### Crunchbase API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/crunchbase/search` | Page fetch | 1–13 s | 55 s |
| `GET /v1/crunchbase/organization` | Page fetch | 1–3 s | 55 s |
| `GET /v1/crunchbase/person` | Page fetch | 1–2 s | 55 s |

### Reuters API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/reuters/search` | Page fetch | 2–10 s | 50 s |
| `GET /v1/reuters/article` | Page fetch | 1–3 s | 50 s |

### Bloomberg API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/bloomberg/search` | Page fetch | 1–3 s | 40 s |
| `GET /v1/bloomberg/article` | Page fetch | 1–3 s | 40 s |

### Associated Press API

| Endpoint | How it loads | Typical | Limit |
| - | - | - | - |
| `GET /v1/ap/search` | Page fetch | 1–6 s | 60 s |
| `GET /v1/ap/article` | Page fetch | 1–5 s | 60 s |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.