# No hourly cap on Web Search for paid plans

**Published:** October 4, 2026 | **Authors:** Cristian Correa

---

## What changes

Until today, `POST /global/web-search/v1` allowed 10 requests per hour per organization, on every plan. An agent researching a topic runs more than 10 searches in a session, and it hit a `429` even when the plan had plenty of credits left. From today:

| Plan | Hourly cap on Web Search |
| --- | --- |
| Free | 100 requests / hour (was 10) |
| Hobby, Standard, Pro, Scale and Enterprise | No hourly cap |

On paid plans each search spends 10 credits, like any live lookup, and those credits are the only limit. The free plan keeps an hourly cap, now ten times wider.

```bash
curl https://api.croma.run/global/web-search/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "colombia insolvency proceedings 2026", "limit": 10 }'
```

## In the headers

On a paid plan, Web Search's `RateLimit-Policy` carries only the credits policy, and `X-RateLimit-Remaining` reports the credits you have left. On the free plan the hourly cap still shows, as `"webSearch";q=100;w=3600`. Go over it and the response is a `429` with `Retry-After`, as before.

## What stays the same

Research keeps 10 requests per hour, and Extract and Generate keep 60. They are listed in [rate limits](https://docs.usecroma.com/rate-limits).

## One confusing number gone

The console showed "100 requests / 24h" as your organization's limit. That number predates the plans and no longer applies: your allowance is your plan's credits, shown in your balance. We removed it.

The Web Search guide is in [the docs](https://docs.usecroma.com/guides/global/web-search), and the plans are on [pricing](/pricing).

---

**More updates:** [View all changelog entries](/en/changelog/sitemap.md) | [Croma](https://usecroma.com)