> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/credit-rate-card/openapi.json](/docs/api/credit-rate-card/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Credit rate card: Get the credit rate card

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Credit rate card](/docs/api/credit-rate-card.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Get the credit rate card

`GET /v1/credits/rate-card` - operationId `credit-rate-card.get`

| Permission | Rate limit |
| --- | --- |
| Any signed-in caller | 12,000 requests a minute per API key |

Returns the price of every credit action, such as a found email, AI qualification of 1,000 contact rows or a
Kenso inbox for a month. The call needs no `X-Ken-Workspace-Id`; send it to get the card of that workspace
(see `version`).

`millicreditsPerUnit` is the price of one unit, and `unitSize` is the quantity prices are usually
quoted for. `pricing` says how to read it: `fixed` is the exact price; `typical` marks work whose
price depends on what it does (a campaign build, a reply draft, a reply, a Ken chat turn, a translation, a podcast
request), and `millicreditsPerUnit` is then the median price of one unit across Kenso in the last 30 days, or 0
while fewer than 20 units were charged. `typical` says how it was measured. Each ledger line shows the exact
amount. A domain row's price depends on the name, so a domain order shows each name's price in credits before
checkout.

Some rows appear only while Kenso offers the action: `web_scrape`, `podcast_search`,
`places_search_page`, `places_detail_open`, `instagram_account_monthly`, `event_post_person`,
`event_post_person_paid_source`, `social_data_record` and `smtp_email`.

`depths` prices one lead at each campaign depth (`bulk`, `personalized`, `multichannel`)
from these rows. A campaign estimate with that `depth` uses the same price per lead.

`version` is `1` unless you send `X-Ken-Workspace-Id` for a workspace on the new plans, which gets
that card with `version` `2`: its rows use the new prices, and a row may have `millicreditsPerUnit`
0 (not charged in credits). Version 2 lists AI work at 0, with a note that it counts toward the plan's AI limit.
A workspace whose plan has no AI limit (Free after its trial, an older plan) still pays AI work at the version 1
prices, and its credit estimates price it that way.

A Kenso Lifetime workspace's card (send its `X-Ken-Workspace-Id`) lists the add-ons it pays in credits at its
own prices, on either version and each a month: `ken_inbox_monthly` 250 credits, `prewarmed_inbox` 400
credits in place of the inbox price, `azure_domain_monthly` 1,250 credits and `linkedin_account_monthly`
2,500 credits.

Open to any signed-in caller.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/credits/GET/v1/credits/rate-card)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of a workspace to answer for. Without it the call answers for no workspace. A workspace you are not a member of answers `404 not_found`. |

### Response 200

`data` is a `CreditRateCard`.

| Field | Type | Description |
| --- | --- | --- |
| `object` | string | Always `credit_rate_card`. |
| `usdPerCredit` | string | The price of one credit in US dollars, as a string such as `"0.02"`. |
| `version` | integer (int32) | Which prices the card lists: `1`, or `2` for a workspace on the new plans. |
| `items` | array of CreditRateCardItem | One row per credit action. |
| `depths` | array of CreditDepth | What one lead costs at each campaign depth, from these prices: `bulk`, `personalized` and `multichannel`, in that order. A campaign estimate with the same `depth` prices its leads at this rate. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/credits/rate-card" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": {
    "object": "string",
    "usdPerCredit": "string",
    "version": 1,
    "items": [
      {
        "action": "email_found",
        "unit": "valid_email",
        "unitSize": 1,
        "millicreditsPerUnit": 1,
        "billing": "per_use",
        "note": "string",
        "pricing": "string",
        "typical": {
          "millicredits": 1,
          "windowDays": 1,
          "from": "2026-09-23T15:02:11Z",
          "to": "2026-09-23T15:02:11Z"
        },
        "freePerDay": 1
      }
    ],
    "depths": [
      {
        "depth": "string",
        "millicreditsPerLead": 1,
        "lines": [
          {
            "action": "email_found",
            "unitsPerLead": 1,
            "millicreditsPerLead": 1,
            "description": "string"
          }
        ]
      }
    ]
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### CreditRateCardItem

The price of one credit action.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `action` | string | no | The credit action, such as `email_found`. |
| `unit` | string | no | What one unit is, such as `valid_email`, `contact_row`, `build`, `reply_draft`, `chat_turn`, `send`, `inbox`, `domain`, `registrar_usd` or `linkedin_account`. Expect new values. |
| `unitSize` | integer (int32) | no | The quantity the price is usually quoted for, such as 1,000 contact rows. |
| `millicreditsPerUnit` | integer (int64) | no | The price of one unit, in millicredits. A `typical` row: the typical price, 0 while there is not enough data. A domain row's price depends on the name: a domain order shows each name's price before checkout. 0 on a version 2 row that costs no credits. |
| `billing` | string | no | How often the action is billed: `per_use`, `monthly`, `one_time` or `yearly`. |
| `note` | string | no | More pricing detail, such as when the action is free. Omitted when none. |
| `pricing` | string | no | `fixed`: `millicreditsPerUnit` is the exact price. `typical`: the price depends on the work, and `millicreditsPerUnit` is a recent median; each ledger line shows the exact amount. |
| `typical` | CreditTypicalPrice | no | How a `typical` row's price was measured. Omitted on `fixed` rows, and when it could not be measured just now. |
| `freePerDay` | integer (int32) | no | Uses a workspace gets free in any 24 hours (counted over the last 24 hours) before each costs the price. Omitted when none. |

### CreditDepth

What one lead costs at a campaign depth.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `depth` | string | no | `bulk` (find, qualify and send a template), `personalized` (plus one AI personalization) or `multichannel` (tier-1: research the lead's company and personalize the email and the LinkedIn note). |
| `millicreditsPerLead` | integer (int64) | no | What one lead costs, in millicredits. |
| `lines` | array of CreditDepthLine | no | The credit actions one lead needs, with their units. |

### CreditTypicalPrice

How a typical price was measured: the median price one unit cost customers across Kenso.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `millicredits` | integer (int64) | no | The median millicredits of one unit. Null while fewer than 20 units were charged in the window. |
| `windowDays` | integer (int32) | no | The length of the window measured, in days. Always 30. |
| `from` | string (date-time) | no | The start of the window measured, in UTC. |
| `to` | string (date-time) | no | The end of the window measured, in UTC. |

### CreditDepthLine

One credit action of a campaign depth.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `action` | string | no | The credit action, such as `email_found`. |
| `unitsPerLead` | integer (int32) | no | Units of the action one lead needs. |
| `millicreditsPerLead` | integer (int64) | no | What those units cost, in millicredits. |
| `description` | string | no | What the line covers, in plain words. |
