---
updatedAt: 2026-08-11T16:53:50.000Z
agentTools:
  projectIndex: https://developer.demandbase.com/llms.txt
---

# Credit Consumption Model

<Header title="B2B API Credit Consumption Model" headerLevel="1" />

<Header title="Overview" />

This document explains how credits are consumed when using the Demandbase B2B API.  Credit usage vaires by endpoint and billing model.  The two primary models are **Per Record Returned** and **Record Under Management (RUM)**

<Header title="Billing Models" />

<Header title="Overview" headerLevel="3" />

The B2B API supports two billing models. Customers are assigned one of these models based on contract or SKU alignment.

<Accordion title="Per Record Returned" icon="fa-info-circle">
  <ul>
    <li>Credits are deducted <strong>each time a record is returned</strong></li>
    <li>Common for real-time enrichment, CRM plugins, or UI-triggered workflows</li>
  </ul>
</Accordion>

<Accordion title="Record Under Management (RUM)" icon="fa-info-circle">
  <ul>
    <li>Credits are charged <strong>once per unique contact or company</strong> returned by a match call.</li>
    <li>Ideal for batch enrichment, synced databases, or CDP integrations.</li>
    <li>Subsequent fetches of the same record <strong>do not consume additional credits</strong> under this model.</li>
  </ul>
</Accordion>

<Header title="Credit Costs by Endpoint (Per Record Returned Model)" />

<Header title="Overview" headerLevel="3" />

In this model, a credit is deducted **each time a record is returned**.  This includes direct API fetches for contact or company data, as well as supplemental assets like news or logos.

<Header headerLevel="4" title="Cost Per Endpoint" />

| Endpoint                                    | Credit Cost        | Notes                                                                                  |
| :------------------------------------------ | :----------------- | :------------------------------------------------------------------------------------- |
| `/contacts`                                 | 0                  | Free to use; no credits charged                                                        |
| `/companies`                                | 0                  | Free to use; no credits charged                                                        |
| `/match`                                    | 1 per unique match | Based on number of unique contact/company IDs matched                                  |
| `/contact/{contactId}`                      | 1                  | Includes contact and employment details                                                |
| `/company/{companyId}`                      | 1                  | Includes firmographics; optional fields like familyTree and installedTech are included |
| `/company/{companyId}/newsFeed`             | 1                  | Full news feed                                                                         |
| `/company/{companyId}/news?newsCategories=` | 1                  | Category-specific news                                                                 |
| `/company/{companyId}/logos/size`           | 1                  | Company logo image                                                                     |
| `Bulk Match`                                | 1 per match        | Counted per unique matched record                                                      |
| `Bulk Fetch`                                | 1 per record       | Counted per contactId or companyId                                                     |

<Header headerLevel="2" title="Technographics and Family Tree" />

<Accordion title="Per Record Returned" icon="fa-info-circle">
  <ul>
    <li>Credits are deducted <strong>each time a record is returned</strong></li>
    <li>Common for real-time enrichment, CRM plugins, or UI-triggered workflows</li>
  </ul>
</Accordion>

<Accordion title="Record Under Management (RUM)" icon="fa-info-circle">
  <ul>
    <li>Credits are charged <strong>once per unique contact or company</strong> returned by a match call.</li>
    <li>Ideal for batch enrichment, synced databases, or CDP integrations.</li>
    <li>Subsequent fetches of the same record <strong>do not consume additional credits</strong> under this model.</li>
  </ul>
</Accordion>

<Header title="QPS and Throughput" />

<ul>
  <li>The B2B API has default rate limits to ensure playform stability</li>
  <li>Standard QPS limit applies to all API keys.</li>
  <li>Contact your account manager for high QPS enablement</li>
</ul>