Skip to content
Console(opens in a new tab)

Credits and pricing

Plans, what uses credits, how a request is metered, and what happens when credits run out.

One credit costs 1¢. The price of each data product is on the rate card. Your balance and usage are on the Usage page in Enigma Console.

A data product is a group of fields that is billed as one unit. Most data products match one kind of record that you read through a connection: the names of a brand bill as Brand Name, and its websites bill as Website. A few records split their fields. For example, on an address, latitude and longitude bill as Address Latitude/Longitude, and the other fields bill as Address.

When you read through two connections, each record of each connection is charged at its own price. The examples below label each line with its data product.

  • A search uses credits for the data products in its response.
  • A list materialization uses credits for the data products in its output.
  • aggregate, account, lists, listMaterialization, backgroundTask, and introspection use no credits.
  • A selection of only id, edges, and node uses no credits.
  • In a search, math fields such as count and has use no credits. In a list, a math field uses the credits of the data product that its field reads.
  • Each record in the response counts once for each data product that you select on it.
  • Each edge of a connection is a separate record. first and conditions.limit set how many records you pay for.
  • A data product with no value on a record costs nothing, except for the products that the rate card marks “bills on request”. Those charge for every query.
  • GovArchive Record counts once per request, not once per record.

Each example is a selection inside a search for one record, such as search(searchInput: { entityType: BRAND, name: "Safeway", conditions: { limit: 1 } }). The costs use the list prices on the rate card and the results of a real search for Safeway.

... on Brand {
id # No credits
names(first: 1) { edges { node { name } } } # Brand Name: 2 credits per record
websites(first: 1) { edges { node { website } } } # Website: 2 credits per record
}
  • Brand Name is listed as 2 credits per record on the rate card.
  • Website is listed as 2 credits per record on the rate card.

The search returned one record of each, so this search uses 4 credits:

Brand Name 1 × 2 + Website 1 × 2 = 4 credits.

... on Brand {
operatingLocations(first: 25) { # No credits: no field of the location
edges { node {
addresses(first: 1) { edges { node { city state } } } # Address: 2 credits per record
} }
}
}

Address 25 × 2 = 50 credits.

first: 25 is the most records you pay for, not a fixed charge. If the brand has only 10 operating locations, the search returns 10 and uses Address 10 × 2 = 20 credits. A location with no address costs nothing for Address.

... on Brand {
# Brand 12M Card Revenue Amount: 10 credits per brand
cardTransactions(first: 1, conditions: { filter: { AND: [
{ EQ: ["period", "12m"] },
{ EQ: ["quantityType", "card_revenue_amount"] }
] } }) {
edges { node { projectedQuantity periodEndDate } }
}
}

Brand 12M Card Revenue Amount 1 × 10 = 10 credits. The filter sets both period and quantityType, so the search counts once for the brand.

... on LegalEntity {
bankruptcies(first: 1) { edges { node { filingDate chapterType } } } # Bankruptcy: 10 credits per record, bills on request
}

Bankruptcy 1 × 10 = 10 credits. The response is empty, but Bankruptcy bills on request.

  • Each output row counts once for each data product in the row.
  • Each list filter is a data product, and it counts once for each output row.
  • The run checks your balance before it charges. When the balance is too low, the run pauses with the message Insufficient credits. and nothing is charged.
  • A paused run continues when you add credits. A paused run cannot be canceled.
  • search, createList, and createListMaterialization fail with a 400 response and the message Insufficient credits to complete this action.
  • The API updates the credit check a few seconds after each request. A burst of requests can take the balance below zero.
  • account.creditsAvailable shows whether the account can use credits. It does not give the balance.
  • Auto-recharge refills the balance to autoRechargeRechargeToAmount credits when it falls below autoRechargeThresholdAmount credits.
  • autoRechargeLimitUsd caps the auto-recharge spend in each billing period. At the cap, auto-recharge stops until autoRechargeReenableAfterTimestamp.
  • Change these settings on the Plan page in Enigma Console.
Plan Price per month Included credits per month API access
Free $0 None No
Pro $20 2,100 Yes
Max $200 25,000 Yes
Enterprise Contact sales By contract Yes
  • Profile views and searches in Enigma Console use no credits.
  • Console limits these actions per day and per month. The Console header shows what is left.
Action Free Pro Max Enterprise
Profile views 60 per day, 300 per month 120 per day, 1,200 per month 1,200 per day, 12,000 per month By contract
Searches 20 per day, 100 per month 40 per day, 400 per month 400 per day, 4,000 per month By contract
Segment searches 10 per day, 50 per month 20 per day, 200 per month 200 per day, 2,000 per month By contract
  • A segment export or a file enrichment runs as a list materialization and uses credits. For a segment, the Console shows the cost before you generate it.