Understand Demandbase MCP Credit Usage
Demandbase MCP credits measure the amount of Demandbase data returned through MCP.
Simple rule: 1 credit = 1 record returned
Credits are based on the returned, not on how the data is assembled or how many data sources contribute to the result.
What Counts as a Demandbase MCP Record?
A record is one result returned by Demandbase MCP. Examples include:
- Account
- Contact
- Lead
- Full Account Brief
Tip: A Full Account Brief costs 1 credit, even when it combines data from multiple sources, such as Demandbase internal (tenant) data, firmographics, and engagement details.
Nested data included within a record does not consume additional credits. Examples include:
- News articles
- Competitor lists
- Employment history
- Company hierarchies
When Demandbase MCP Credits Are Charged
Demandbase MCP credits are charged when Demandbase MCP successfully returns records. Each returned record consumes 1 credit, including records returned on subsequent pages or across multiple entity types.
Credits Are Not Charged When No Data Is Returned
Demandbase MCP credits are not charged when a request does not return data.
Credits are not charged in the following situations:
- A query returns zero results
- A request fails before data is delivered
- Your balance is zero and the request is rejected
- You repeat a query within a 60-minute window and it returns the same results.
How Pagination Affects Demandbase MCP Credit Usage
Paginated results return a limited number of records at a time, and credits are charged only for the records on the pages you load.
Results default to 5 records per page, which consumes up to 5 credits per page. You can request up to 100 records per page.
Important: Specify a record limit or page size, especially for automated workflows. Some LLMs may override the default page size.
Common Demandbase MCP Credit Usage Scenarios
The following scenarios show how returned records affect Demandbase MCP credit usage:
| Request Type | How It Works | Example | Credit Usage |
|---|---|---|---|
| Single-record lookup | Returns one record. | Look up one account. | 1 credit |
| Full Account Brief | Returns one consolidated Account Brief, which may combine data from multiple sources. | Create an Account Brief for one account. | 1 credit |
| Capped list | Returns records up to the limit you specify. | Request 10 accounts and receive 10. | 10 credits |
| Uncapped list | Returns results in pages. Credit usage increases as additional pages are loaded. | Load a page containing 5 records. | 5 credits |
| Multiple entity types | Charges for each record returned across all entity types. | Receive 10 accounts and 10 contacts. | 20 credits |
| Batch lookup with missing records | Charges only for records successfully returned. | Submit 10 IDs and receive 8 matching records. | 8 credits |
How Your Demandbase MCP Credit Balance Works
When your Demandbase MCP credit balance reaches zero, requests that require credits are rejected before they run.Requests are rejected before they run.
No data is returned and no credits are charged. Add credits to your balance to resume usage.
Best Practices for Managing Demandbase MCP Credits
Use the following best practices to make Demandbase MCP credit usage more predictable:
- Set a record limit for list queries.
- Use single-record lookups for targeted research.
- Set page limits for automated workflows.
- Check your organization's credit balance regularly.
Updated 13 days ago