---
updatedAt: 2026-10-09T13:34:31.000Z
agentTools:
  projectIndex: https://developers.leadboxer.com/llms.txt
---

# Credit Usage & Cost Model

Some API endpoints consume credits when they are called. Credits are used to account for request processing performed by the platform.

This page explains:

* When credits are consumed
* How credit usage works
* Where to find exact usage
* Fixed credit costs per endpoint

***

## When are credits consumed?

Credits are consumed **per request** when an endpoint is called.

* Credit usage is **not based on results**
* Credit usage is **not affected by response size**
* Credit usage is **independent of enrichment depth**

If a request reaches the API and is processed, the associated credits are consumed.

Endpoints that consume credits are clearly marked in the API reference with a **Credits** notice.

***

## Fixed credit usage model

All credit-consuming endpoints use a **fixed credit cost per request**. This means:

* Each request consumes a known, predefined number of credits
* The same endpoint always consumes the same number of credits
* Credits are consumed regardless of whether the response contains data, except for `/v1/email-lookup`, which only consumes credits when a profile is found

There are **no variable credit costs**.

***

## Credit costs per endpoint

The tables below lists the fixed credit cost per request for each endpoint.

**Website & email events**

<Table align={["left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Description
      </th>

      <th>
        Endpoint
      </th>

      <th>
        Credits per request
      </th>

      <th>
        Notes
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Website pageview
      </td>

      <td>
        `/v1/track` or JS lib
      </td>

      <td>
        1 credit
      </td>

      <td>
        Track a single (web) event
      </td>
    </tr>

    <tr>
      <td>
        Email open
      </td>

      <td>
        `track-email-open`
      </td>

      <td>
        Free
      </td>

      <td>
        Track an email open event  
        _includes free company enrichment_
      </td>
    </tr>

    <tr>
      <td>
        Email click
      </td>

      <td>
        `track-email-click`
      </td>

      <td>
        Free
      </td>

      <td>
        Track an email click event  
        _includes free company enrichment_
      </td>
    </tr>

    <tr>
      <td>
        Form submit
      </td>

      <td>
        `/v1/track` or JS lib
      </td>

      <td>
        Free
      </td>

      <td>
        Track a form submit including email    
        _includes free company enrichment_
      </td>
    </tr>
  </tbody>
</Table>

<br />

**Identification**

<Table align={["left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Description
      </th>

      <th>
        Endpoint
      </th>

      <th>
        Credits per request
      </th>

      <th>
        Notes
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        IP → company lookup
      </td>

      <td>
        `/v1/ip-lookup`
      </td>

      <td>
        20 credits
      </td>

      <td>
        Per API call and
        per unique IP per 24 hours
      </td>
    </tr>

    <tr>
      <td>

      </td>

      <td>
        JS lib (tracking pixel)
      </td>

      <td>
        20 credits
      </td>

      <td>
        Per unique userId + IP per 24 hours
      </td>
    </tr>
  </tbody>
</Table>

<br />

**Enrichment**

<Table align={["left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Description
      </th>

      <th>
        Endpoint
      </th>

      <th>
        Credits per request
      </th>

      <th>
        Notes
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Company enrichment  
        (Firmographic details)
      </td>

      <td>
        `/v1/domain-lookup` or JS lib
      </td>

      <td>
        10 credits
      </td>

      <td>
        Per API call
      </td>
    </tr>

    <tr>
      <td>

      </td>

      <td>
        JS lib (tracking pixel)
      </td>

      <td>
        10 credits
      </td>

      <td>
        per unique domain
      </td>
    </tr>

    <tr>
      <td>
        Contact enrichment  
        (Professional Details)
      </td>

      <td>
        `/v1/email-lookup`
      </td>

      <td>
        50 credits
      </td>

      <td>
        Per API call that finds a profile.  
        _No profile found (404): free_
      </td>
    </tr>
  </tbody>
</Table>

<br />

## Where to see your actual credit usage

You can review:

Credits consumed

Total credits used over time

Remaining credits and limits

in the **Credit Cost Overview** within your account.

This overview reflects the actual number of requests processed by the API.

***

## Failed and invalid requests

* Requests that fail validation or authentication **do not consume credits**
* Requests that reach processing and return a valid response **do consume credits**

Rate-limited or blocked requests do not consume credits.

***

## Best practices

To manage credit usage effectively:

* Monitor request volume via the Credit Cost Overview
* Avoid unnecessary polling
* Cache responses client-side where appropriate

***

## Changes to credit costs

Credit costs per endpoint may change over time as the platform evolves.

Any changes will be reflected in:

* This documentation
* The API reference
* The Credit Cost Overview

Changes will of course be timely announced and ongoing plans will remain unchanged unless announced otherwise.

<br />