> ## Documentation Index > Fetch the complete documentation index at: https://docs.brightdata.com/llms.txt > Use this file to discover all available pages before exploring further. # Get pricing plans > Use GET /pricing_plans in the Bright Data Account Management API to list current and available pricing plans with per-product prices. Returns 200 OK as JSON. The `GET /pricing_plans` endpoint returns your account's current pricing plan and the other plans available to your account, with the per-product prices of each plan. All prices are in USD. Paste your API key into the authorization field. To get an API key, [create an account](https://brightdata.com/?hs_signup=1\&utm_source=docs\&utm_campaign=playground) and learn [how to generate an API key](/api-reference/authentication#how-do-i-generate-a-new-api-key%3F). ## Which API key permission does this endpoint need? `GET /pricing_plans` requires the `billing.read` permission. API keys with the **Admin** or **Finance** [permission level](/api-reference/authentication#what-permissions-level-does-an-api-key-have) have it. Keys with the Ops, Limit or User permission level cannot call this endpoint. ## How do I get my current pricing plan? Call `GET /pricing_plans` with an Admin or Finance API key. The endpoint takes no parameters: ```bash theme={null} curl -H "Authorization: Bearer YOUR_API_KEY" \ "https://api.brightdata.com/pricing_plans" ``` The response contains a `plans` array. Your current plan is the entry where `is_current` is `true`. To print only that plan, filter the response with [jq](https://jqlang.org/): ```bash theme={null} curl -s -H "Authorization: Bearer YOUR_API_KEY" \ "https://api.brightdata.com/pricing_plans" \ | jq '.plans[] | select(.is_current)' ``` ## How is the response structured? Each entry in the `plans` array describes one plan: | Field | Type | Description | | ---------------- | ------- | --------------------------------------------------------------------------------- | | `id` | string | Plan identifier | | `name` | string | Plan name | | `precommit` | number | Monthly pre-commitment of the plan, in USD | | `is_current` | boolean | `true` for the plan your account is on now, `false` for the other available plans | | `product_prices` | object | Prices of the plan, keyed by internal product key | The keys of `product_prices` are the same internal product keys that the [cost breakdown export](/api-reference/account-management-api/Export_cost_breakdown) uses in its filters, such as `dc` (Datacenter proxies) and `res_static` (ISP proxies). Each value holds a product `name` and a `price_groups` array. Each price group has a `name`, a `prices` object and, for some products, an `unlim_ip_tier_prices` object. ## How do I read the prices object? Each key in `prices` is a billing unit and each value is the price in USD for one unit. For example, `"prices": {"gb": 8}` means \$8 per GB. | Key | Billing unit | | ----- | ------------------------------------------ | | `gb` | 1 GB of traffic | | `req` | 1,000 requests (CPM), not a single request | The other possible keys are `compute_hour`, `record`, `total`, `files_archive`, `files_cache`, `req_content`, `block` and `page_load`. Which keys appear depends on the product. ## Which products return unlim\_ip\_tier\_prices? Only Datacenter proxies (`dc`) and ISP proxies (`res_static`) return `unlim_ip_tier_prices`. The object maps each IP tier size to its price in USD. ## Does the endpoint have rate limits or specific errors? No. `GET /pricing_plans` has no endpoint-specific rate limit and no endpoint-specific error codes. ## Related endpoints * [Cost breakdown export](/api-reference/account-management-api/Export_cost_breakdown). Per-day account cost by product, zone, dataset or scraper. * [Total balance](/api-reference/account-management-api/Get_total_balance_through_API). Current balance and pending balance for the next billing cycle. ## OpenAPI ````yaml api-reference/openapi GET /pricing_plans openapi: 3.0.1 info: title: Bright Data API description: >- Integrate Bright Data APIs to your pipeline and secure high-end scraping precision version: 1.0.0 servers: - url: https://api.brightdata.com security: - bearerAuth: [] paths: /pricing_plans: get: description: >- Get your account's current pricing plan and the plans available to it, with per-product prices for each plan. All prices are in USD. Requires the `billing.read` permission (API keys with the Admin or Finance permission level). responses: '200': description: OK content: application/json: schema: type: object properties: plans: type: array description: Your current plan and the plans available to your account. items: type: object properties: id: type: string description: Plan identifier. name: type: string description: Plan name. precommit: type: number description: Monthly pre-commitment of the plan, in USD. is_current: type: boolean description: >- `true` for the plan your account is on now, `false` for the other available plans. product_prices: type: object description: >- Prices of the plan, keyed by internal product key (the same keys as the cost breakdown export filters, for example `dc` or `res_static`). additionalProperties: type: object properties: name: type: string description: Product name. price_groups: type: array items: type: object properties: name: type: string description: Price group name. prices: type: object description: >- Prices in USD, keyed by billing unit. For example, `{"gb": 8}` means $8 per GB. `req` is per 1,000 requests (CPM). Possible keys: `gb`, `req`, `compute_hour`, `record`, `total`, `files_archive`, `files_cache`, `req_content`, `block`, `page_load`. Which keys appear depends on the product. additionalProperties: type: number unlim_ip_tier_prices: type: object description: >- Prices in USD keyed by IP tier size. Returned only for the `dc` (Datacenter proxies) and `res_static` (ISP proxies) products. additionalProperties: type: number components: securitySchemes: bearerAuth: type: http scheme: bearer description: >- Use your Bright Data API Key as a Bearer token in the Authorization header. **How to authenticate:** 1. Obtain your API Key from the Bright Data account settings at https://brightdata.com/cp/setting/users 2. Include the API Key in the Authorization header of your requests 3. Format: `Authorization: Bearer YOUR_API_KEY` **Example:** ``` Authorization: Bearer b5648e1096c6442f60a6c4bbbe73f8d2234d3d8324554bd6a7ec8f3f251f07df ``` Learn how to get your Bright Data API key: https://docs.brightdata.com/api-reference/authentication bearerFormat: API Key ````