Developers › Pricing

Pricing

You pay per row, and separately for the contact fields you ask for — but only when they contain something. Prices below are read from the same table our billing engine uses, so they are current by construction.

Applies to	Field group	Price per row	What you get
Company row	`core`	3.0 c	Identity, address, industry, register entries, and free availability flags telling you whether the premium groups would return anything for this row (has_decision_maker here means at least one named person, the same set the decision_makers group returns).
Company row	`phone`	8.0 c	Phone numbers published on the company's own website, in confidence order, with the date last seen.
Company row	`email`	8.0 c	The company's general email addresses (info@, sales@…). Named individuals' addresses belong to the decision-maker endpoints, not here.
Company row	`decision_makers`	12.0 c	Named decision-makers with their role and title.
Decision-maker row	`core`	5.0 c	Role, title, employer and freshness — everything except the person's identity and contact details.
Decision-maker row	`name`	7.0 c	The person's name.
Decision-maker row	`phone`	8.0 c	The person's own direct number. Mobile is preferred when several are known — a switchboard does not reach a person.
Decision-maker row	`email`	8.0 c	The person's work address: found directly, or derived from the organisation's address pattern. The response says which.

All prices exclude VAT (25.5 % in Finland). Invoiced monthly in arrears, 14 days net.

Free

Counts. /companies/count and /decision-makers/count cost nothing, however often you call them.
Availability flags. Every company row tells you whether a phone number, an email address or a decision-maker exists for it — before you decide to buy any of them.
The free field groups. web, financials and signals add no cost; they are part of the base row and only opt-in so responses stay small.
Your own usage. /usage and /filters are free and do not consume quota.
Everything in the sandbox. A sandbox key is never charged, whatever it fetches.

Never billed

Empty fields. Ask for phone and you pay only for rows that have a number. The response counts the empty ones explicitly.
Repeats within 30 days. The same row and field group, fetched again with the same key, is free for 30 days from the last paid fetch. Retry loops and re-syncs do not produce a second charge.
Failed requests. Any 4xx or 5xx costs nothing.

A worked example

You fetch 1 000 construction companies in Uusimaa with fields=phone,email. 1 000 base rows are billed. Of those, 610 have a phone number and 480 have a general email address; the remaining 390 and 520 are not billed for those groups. Two weeks later you re-run the same sync: the base rows and every field you already bought are free, and you pay only for rows that are new to the register.

Caps and quotas

Every key has a monthly spend cap. When it is reached, billable calls return 403 spend_cap_reached until the month turns — the counters are free, so you can still see what happened. The cap is a safety limit on your own account, not a payment problem, and we will raise it on request.

Keys also carry a per-minute burst limit, a daily request quota and a monthly row quota. On top of the per-key limits an account can have a monthly request cap shared by all of its keys, agreed in the contract; when it is reached, billable calls return 429 quota_exceeded with a Retry-After pointing at the start of next month. Call /usage to see yours — it reports both the key's own counters and the account total.

Negotiated pricing

Volume, pilots and reseller arrangements are priced per customer. If the list price does not fit what you are building, say what you need — the pricing is per account, so a different number is a conversation and not a workaround.

Prefer a file to an integration? The same data is sold as a one-off CSV or Excel delivery through the web shop, priced per row with volume tiers. See the Finnish price list.