What a record costs

You pay for records, priced per event in USD per 1,000. You pay for every lookup the source answers, including "not found". You never pay when we fail to get an answer, and a search that finds nothing costs nothing.

What a record costs

Every record carries an event field, and each site/event has a price per 1,000 records. The cost of a run is the number of records delivered under each event, divided by 1,000, times that event's price. A job that delivers 2,500 records under one event priced at $4.80 costs $12.00.

• A record is billed when it is delivered. A record the run could not deliver, for instance because the credit balance ran out, is not billed.
• A lookup the source answers "not found" is billed. When you name one item, for example a product id or a property URL, and the source says it does not exist or was removed, you get a record with status: "not_found", the id and url you asked for and no other data, at the same price as a found record of that event. The source answered, and answering cost the same work.
• A record with an error field is one we could not complete (a block, a timeout, an answer we could not read). It is delivered so you can see what failed, and is never billed.
• A request that returned nothing usable produces no record and no charge. It appears in stats.failures. When your input caused it, for example an invalid input or a search that found nothing, it counts toward the unbilled quotas reported by GET /usage; when it failed on our side, it does not. A billed not-found record never counts there.

Prices are keyed by event, not by type: two events can share one type and carry different prices. Records and jobs explains the difference.

Prices

USD per 1,000 records for every event of every listed source, by kind of data. GET /usage returns the prices for your key under prices.

Real estate

Jobs and hiring

E-commerce

Social media and video

Reconcile with GET /usage

GET /usage reports, for the current UTC month, the records billed per site/event under events and the spend under month.cost. Multiply each count by its price and divide by 1,000; the sum is the month's spend. day.cost does the same for the current UTC day.

Example: amazon/product at $4.80 per 1,000 with "amazon/product": 2,500 in events accounts for $12.00 of month.cost.

For one run, stats.counts on the job gives the records per event in the same way. A synchronous POST /records settles its charge before it answers, so GET /usage right after the response already includes it. Amounts are kept to six decimal places, so a sum can differ from month.cost in the last decimal.

Your credit balance

Billing is prepaid: every delivered record draws on the account's credit at the price above. A key needs no credit to be created, only to fetch records. GET /account/credits and the Credits section of your account show the current balance, what running jobs have set aside from it, and the history of what was added.

Records are never invoiced and never owed: a job spends only what the balance already holds. When the balance reaches zero mid-run, the job delivers the records the balance covered, then stops with status cancelled and an error naming the reason. A request made with no balance left is refused before it starts.

Purchased credit expires 365 days after it is added, shown against each entry in the history. The balance is capped at $5,000.00; a purchase that would take it over the cap is refused.

Trial credit

A new account gets $2 of credit once its email address is confirmed, so you can send real requests before you buy anything. It lasts 30 days from the day it is added. You do not need a card, for the trial or to create a key.

• The address must be confirmed. An account that has not confirmed its address gets no trial credit.
• Addresses at disposable mail services, and at relay services that forward mail to another mailbox, get no trial credit. They can still sign up and buy credit.
• A mailbox gets the trial once. Deleting the account and signing up again with the same address does not bring it back. A plus sign and what follows it in the address do not make a new mailbox, and neither do dots in a Gmail address.
• One network gets at most 2 trials in 30 days. A network is one IPv4 address, or one IPv6 /64. Only accounts that never bought credit count toward the limit.

Buying credit

Buy credit at your account, as a fixed pack (Starter, Growth, Scale) or a custom amount, from $10.00 to $2,000.00. Payment runs through Stripe Checkout; the balance updates as soon as the payment completes.

Plans

A plan is optional: a flat monthly fee that includes credit and lowers the per-record rate below the prices above. It is never required to create or use a key.

Choose or change a plan, and manage receipts and payment methods, at your account.

Refunds and disputes

A refund or a won card dispute takes back only the unused part of the purchase it applies to: credit already spent on delivered records is never clawed back. A disputed payment holds the account (no key may fetch records) until the dispute closes; every other key action keeps working.

402: no credit left

A key that has no credit left, or whose account has an open payment dispute, answers 402 instead of delivering records. The message names the reason and points at your account. Authentication lists the exact wording.

Next step

The API reference documents GET /usage field by field, including the resource counters that sit next to the billing windows.