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

# Estimate Search Cost

> See how many jobs a search or export would return, and therefore bill, without spending any allowance

Returns the number of jobs a query would consume from your jobs allowance: `min(limit, total matches)` — the same rule [Export Jobs](/docs/api-reference/jobs/export-jobs) bills by. The estimate itself costs **0** and keeps working after you hit a plan cap, so you can size a query before spending on it.

<Warning>
  Requires an API key. Web (JWT) sessions receive `403`.
</Warning>

## Endpoint

```bash theme={null}
POST /v2/jobs/estimate
```

## Request Body

Accepts exactly the same body as [Search Jobs](/docs/api-reference/jobs/search-post): every filter plus `page` and `limit`. Omit `limit` to estimate the cost of exporting every match.

## Response

<ResponseField name="cost" type="number">
  Jobs that would be charged: `limit` when the query matches at least that many, otherwise the total match count. With no `limit`, the total match count.
</ResponseField>

## Example

<CodeGroup>
  ```bash cURL theme={null}
  curl -X POST 'https://api.hirebase.org/v2/jobs/estimate' \
    -H 'x-api-key: YOUR_API_KEY' \
    -H 'Content-Type: application/json' \
    -d '{"job_titles": ["Software Engineer"], "location_types": ["Remote"], "limit": 100}'
  ```

  ```python Python SDK theme={null}
  cost = client.jobs.estimate({"job_titles": ["Software Engineer"], "location_types": ["Remote"]}, limit=100)
  print(cost)  # 100
  ```
</CodeGroup>

<ResponseExample>
  ```json Response theme={null}
  { "cost": 100 }
  ```
</ResponseExample>

<Tip>
  Check `cost` against `Hirebase-Usage-Included-Remaining` from your last response (or `client.last_usage.included_remaining` in the SDK). On hard-capped plans a request that could exceed the remaining allowance is refused up front — see [Usage Headers & Metering](/docs/api-reference/billing/usage-headers#at-the-cap).
</Tip>