MCP Credit Management

Credits measure your Demandbase MCP data usage.

Simple rule:

1 credit = 1 record returned

You are charged for the data returned to you, not for how the data is assembled or how many sources are used.

---

What Counts as a Record?

A record (also called an entity) is one returned result. Examples include:

• Account
• Contact
• Lead
• Full Account Brief
  Tip: A Full Account Brief costs 1 credit, even when it includes combined data such as CRM data, firmographics, and engagement details.

Nested data is included at no extra cost. Examples include:

• News articles
• Competitor lists
• Employment history
• Company hierarchies

---

When Credits Are Charged

Credits are charged only when data is successfully returned.

Credits are charged when

• A query returns results → 1 credit per record
• You load another page of results → 1 credit per record on that page
• A request returns multiple entity types → each record across each type is charged

Example: 20 accounts + 20 contacts = 40 credits

---

Credits are not charged when

• A query returns zero results
• A request fails before data is delivered
• Your balance is zero and the request is rejected
• You run a duplicate query within a 60-minute window and it returns the same results.

---

Pagination

Results default to 5 records per page, or 5 credits per page.

You can request up to 100 records per page. You are charged only for the pages you load.

Important: Always specify a record limit or page size, especially in automated workflows. Some LLMs may override the default page size.

---

Common Usage Scenarios

Single-record lookup

A lookup that returns one record costs 1 credit.

---

Capped List

A capped list returns records up to a specified limit.

Example: Submit Top 10 accounts and receive 10 records = 10 credits.

---

Uncapped List

An uncapped list returns results in pages. By default, each page returns 5 records and costs 5 credits.

Total cost depends on how many pages you load.

Important: Always set a limit to avoid unexpected usage.

---

Multiple Entity Types

You only pay for records that are returned.

Example: Submit 10 IDs and receive 8 matching records = 8 credits.

---

Batch Lookup (with Missing Records)

• You only pay for records that exist

Example: Submit 10 IDs and receive 8 records = 8 credits

Your Credit Balance

All users in your organization share one credit pool. Heavy usage by one user affects the entire team.

Checking your credit balance is free.

---

What Happens When Credits Run Out?

When your credit balance reaches zero:

• Requests are rejected before they run.
• No data is returned.
• No credits are charged.

Top up your balance to resume usage.

---

Best Practices

Do

• Set a record limit on every list query.
• Use single-record lookups for targeted research.
• Set page limits in automated workflows.
• Check your credit balance regularly.

---

Don’t

• Run uncapped queries on large datasets.
• Let automations loop through pages without limits.
• Assume more data sources means more credits.
• Confuse zero results with a failed request.

---

Quick Reference

---

Key Takeaway

You only pay for records returned: 1 credit per record, regardless of complexity.