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

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

DescriptionEndpointCredits per requestNotes
Website pageview/v1/track1 creditTrack a single (web) event
Email opentrack-email-openFreeTrack an email open event
Email clicktrack-email-clickFreeTrack an email click event

Identification

DescriptionEndpointCredits per requestNotes
IP → company lookup/v1/ip-lookup20 creditsPer API call

Enrichment

DescriptionEndpointCredits per requestNotes
Company enrichment/v1/domain-lookup10 creditsFirmographic details
Contact enrichmentPrivate50 creditsProfessional Details

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.