Plans and pricing

Which plan fits which team

The three plans deliver the same row with the same field names; they differ in how domains arrive and how often the answer is refreshed. The right choice follows from how your team works today.

The lookup API fits teams where domains arrive one at a time: a curator who gets a site named on a call, a planner checking a publisher a client mentioned, a marketplace admission form that must answer while the applicant waits. A request returns one row as JSON in a few seconds, and the monthly allowance of 2,000 profiles covers a team that checks a hundred sites a working day. The 10,000-profile tier at $499 a month suits a tool that qualifies sites for several teams or clients at once. Each profile is computed fresh at request time, so the API is also the way to re-check a single site the moment a question comes up.

The list job fits teams that already hold lists: an inclusion list per market, a curated marketplace roster, a client's candidate publishers, a prospect list for publisher development. You send the domains as a file, and within a week you get the rows back as CSV or JSON. The first 2,000 domains are covered by the base price; larger lists are quoted per domain and the unit price falls with volume. Most teams then add the weekly refresh, which re-runs the same list every week and returns a change report: sites whose quality score crossed a threshold, sites whose active SSPs changed, sites whose impression range moved by a band. Additions are billed per domain, so a list can grow as briefs come in without a new agreement each time.

The database licence fits organisations that want to join the data with their own at scale and cannot make an outbound call per domain: exchanges, large agencies, DSPs and verification vendors. It delivers every ad-carrying domain in the underlying database of more than 100 million domains, refreshed monthly, with the deep layer for the 100,000 largest sites and audience profiles for any subset you name. Delivery is on-premises, as files or a database dump, with no calls back to us and no per-lookup metering. Pricing depends on the layers included, the refresh cycle and the number of internal users, and is quoted after a conversation about how the data will be used.

What every plan includes

• The full row for each domain. Active SSPs with seat IDs and activity share; the count of authorised but dormant sellers and of resellers; the estimated monthly impression range with ad positions per page; the 0 to 100 quality score with its label; IAB category, language, country and rank; owner or sales house where declared; and the audience profile coded to the IAB Audience Taxonomy.
• A sample on your own domains first. Five to ten domains you know well, run before any purchase, so you can judge the output against sites you already understand. The sample page shows what comes back.
• Stable field names across API, CSV and database, so a team can start with the API and move to a licence without changing anything downstream.
• Support by email from the people who build the data, with a working-day response.

Plan comparison

How a list job runs

You send a plain list of domains, one per line, in any common format. Subdomains and full URLs are accepted and reduced to the registrable domain; duplicates are removed before counting. We confirm the count and the price, run the list, and deliver the rows with a short summary: how many domains carry advertising at all, how many fall below the quality threshold, the distribution of impression bands, and the exchanges that appear most often across the list. The summary is often the first useful output in itself, because it shows a team the shape of a list it had only ever seen as names.

With the weekly refresh switched on, the list is re-run every week and you receive the full rows plus a change file. The change file lists every domain where the quality label changed, the active SSP set changed, the impression band moved, or the owner changed, with the old and new values side by side. Domains you add during the month are appended to the next run and billed per domain on the following invoice. Domains you remove stop being billed from the next run.

How the API is metered

One request for one domain returns one row and counts as one profile against the monthly allowance, whether the domain carries advertising or not, because the answer that a site does not sell ads programmatically is an answer. The audience endpoint returns the full audience segmentation for a domain and counts as one profile as well. Allowances reset on a 30-day cycle from activation. If a month needs more than the allowance, additional profiles are available in blocks at the same unit rate as the plan, and moving between the two tiers takes effect at the next cycle. There is no rate limit that a normal team will meet; the API is built for tools that qualify sites while people work, not for bulk extraction, which is what the list job and the licence are for.

What a database licence contains

The licence is built in layers so that each organisation pays for what it will join. The base layer is every ad-carrying domain in the database with owner, seller relationships, reseller counts, impression band, quality score, category, language, country and rank. The deep layer adds, for the largest 100,000 sites, the active SSP set observed on the live site with activity shares and the ad positions per page, refreshed monthly; it can be extended to a larger set of sites for a defined list. The audience layer adds full audience profiles for any subset you name, from a category to your whole inclusion list. Delivery is as compressed files or a database dump, keyed on the registrable domain, with a diff file at every refresh so downstream systems apply changes rather than reload. The licence covers internal use across the organisation; redistribution or resale inside a product is agreed separately.

Worked examples

A curation company with a 35,000-domain index

The index is refreshed weekly as a list job. Each week the team receives the rows and the change file, reviews the domains that crossed the quality threshold, and updates the exchange and seat ID on deals whose active SSPs changed. New media owners named in client briefs are added by the account team and appear in the next run, so the index grows with the pipeline rather than with a review calendar. Because the audience profile is on every row, the same index is searchable by persona and purchase intent when a brief arrives, which turns list building into a filter.

An agency with inclusion lists in six markets

Six lists of roughly 4,000 domains each are run as one list job and refreshed weekly. The programmatic team uses the change file as its weekly hygiene review and the impression bands to reallocate budgets across sites that are larger or smaller than assumed. The client-facing teams use the rows to explain list decisions with numbers rather than with vendor claims. When a client asks for a new vertical, the team filters the whole database by category, market, scale and quality to build the first draft of the new list in an afternoon.

An exchange running a curated marketplace

The exchange holds the database licence with the deep layer. Publisher applications are checked against the quality score and the impression band before admission, and every admitted publisher is re-checked at each monthly refresh. The audience layer for admitted publishers powers the marketplace's packages, and the seller relationships show the exchange where else each of its publishers sells, which informs both supply-path conversations and publisher development.

A planner checking one site at a time

A media planner on the lookup API checks each publisher named in a proposal as it is written. The row settles three arguments in one call: whether the site is big enough, whether it is clean, and which exchange the deal should be built in. At a hundred checks a day the 2,000-profile plan is enough, and the profiles are fresh each time.

Per-domain pricing for larger lists

Lists above the 2,000 domains covered by the base price are quoted per domain, and the unit rate falls with volume because most of the cost of a list job is fixed. The bands below are indicative; a firm quote comes with the confirmation of your list, and the refresh price follows the same bands at roughly a third of the one-time rate per month.

Additions during a refresh period are billed at the per-domain rate of the band the list is in, on the following invoice. A list that grows past a band boundary moves to the lower unit rate for the whole list from the next run. A list that shrinks is billed on the domains actually run.

Compared with building it in-house

Teams sometimes ask whether they could assemble the same row themselves from public sources and their own tooling. Some of it, yes, for a few hundred sites and for a while. What they underestimate is the maintenance: publishers change partners every week, ad positions move, sites change ownership, and a list that was right in January is measurably wrong by March. Keeping a few thousand rows current is a standing engineering task, and it still leaves the quality score and the audience profile unsolved, because both require models trained on far more sites than any one buyer sees. The list job with weekly refresh costs less per month than a fraction of one engineer and returns a change report the engineer would have had to build. The database licence is the same trade at organisational scale: one supplier keeping 100 million domains current so that internal teams can spend their time on the decisions instead of on the data.

The other comparison buyers make is with the free version of the same answer: asking the publisher or the SSP contact. That works for the twenty publishers a team talks to regularly and fails for the rest, and it produces an answer that is as current as the last email. The row exists for every domain, refreshes on a schedule, and does not depend on who replied.

Procurement, invoicing and terms

Plans are invoiced monthly or annually by Alpha Quantum, a German company, with VAT handled according to your location. API and list-job plans can start immediately on invoice; database licences are agreed under a short data licence covering internal use, refresh cycle and term. Data is delivered from our own infrastructure; no client data is required to produce a profile beyond the domains you want profiled, and the domain lists you send are used only to produce your rows. Cancellation of monthly plans takes effect at the end of the current cycle. Annual plans and licences are priced with a discount against the monthly equivalent and are quoted on request.