Firmographics tell you how big a company is. They do not tell you what records it keeps. An AI data buyer pays for years of support tickets, client portal activity, CRM history or code with its issue trail. The AI Data Value Score estimates exactly that for any domain, on one scale from 0 to 100. This page explains what every result tells you about a company's data, how to read it, and why a precomputed, comparable score saves a broker more time than a firmographic file, a chatbot prompt or an afternoon of manual research.
We explain what every result contains and how to use it. The inputs, weights, point values, thresholds and the rules that combine the groups stay our own. Every score is an estimate from public signals: not a valuation, not an offer and not proof that a company wants to sell.
Not all company data is worth the same. Our research shows AI labs pay most for the records of real work, held in the systems below. We identify which of these systems each company runs, and it is one of the most important factors in the AI Data Value Score.
Every company comes with the systems we identified, shown as tags. Company level only: we show which systems a company runs, never what is inside them.
Every score has the same shape, whether you check one company in the demo or ten thousand through the API. These are the fields a broker works with. The rest of this page explains what each one tells you and how to act on it.
Fictional company and values, shown to illustrate the fields. A real result also carries the data system tags, verified_active, cached and checked_at.
Buyer programs publish rules about team size, location and years of records, and a firmographic file can screen on the first two. The question that decides whether a deal happens is harder: does this company hold records a buyer wants, in systems that can be exported? Two accounting firms with the same headcount look identical in a firmographic file. One has run a client portal, a help desk and a document management system for fifteen years. The other works from email and a shared drive. A buyer treats them very differently, and so should your pipeline.
The AI Data Value Score starts where firmographics stop. It looks for public evidence that a company keeps records: which data systems it runs, how long it has been in business online, how large its footprint is and whether it is still operating today. From that evidence it estimates the likely data assets and rolls everything into one number you can sort on.
Here is how that compares with the three ways brokers usually qualify a company today.
| Firmographic file | Asking an AI chatbot per domain | Manual research | AI Data Value Score API | |
|---|---|---|---|---|
| What you learn | Size, industry, location | Whatever the model writes about that company, in its own words | Whatever the researcher finds and writes down | Score, grade, likely data assets, nine factor groups, history, status |
| Records the company keeps | Not covered | A guess, phrased differently each time | Found, if the researcher knows where to look | Likely data assets with a confidence level, plus the data systems we identify |
| Years of history | Founding year, when known | Only if it finds a source in that session | Hours of digging, company by company | First seen year and years online in every result |
| Still operating? | As of the last update of the record | Not checked unless it browses, and then not systematically | A visit to the site | Live check at scoring time, returned as a status |
| Comparable across companies | For size, not for data | No fixed scale | Depends on who did the work, and when | One method and one scale for every domain |
| Time per company | Instant | A prompt, a wait and an answer to read | Minutes, often many | Seconds |
| Thousands at once | Yes | One prompt at a time, or your own script around a paid model | No | Loop a CSV through the API |
Each part of a result answers a different question about a company. None of them is enough on its own: a support operation without history could be a startup with ten customers, and a long history without systems could be a dormant brochure site. Together they give a picture of a company's records that no single source gives, in a form you can sort.
Our index holds 120 million domains, 99.99%+ of the active internet, each classified into one of more than 700 IAB content categories. If a company runs a website, it is almost certainly in it.
What it tells you: which industry a company is in, at a level of detail that separates a contract research organization from a hospital, or an insurance broker from a bank. It also lets you work a sector as a whole instead of guessing search terms.
The record types a company probably keeps, each marked medium or high confidence. This is the field that turns a company name into something a buyer can evaluate.
What it tells you: whether a company matches a brief before you spend an hour on research. When a buyer asks for support tickets or code history, you filter for that type and start with the companies that show it most clearly.
We identify which systems each company runs, from help desks and CRMs to issue trackers, learning platforms and HR tools, and show them as tags on every result. It is one of the most important factors in the score.
What it tells you: where the records probably live, because systems keep records. A company that runs its work through systems has records a buyer can actually receive, not years of work scattered across inboxes.
How many years the company has been online, based on domain history from several public sources and returned as a first seen year and a count of years online.
What it tells you: how many years of records a company could hold. Buyers ask for several years of records, and a company online since 2006 has had far longer to build them than one that launched last year.
Footprint signals show how large a company's presence is, from a local practice with a few hundred clients to a business with customers in many countries.
What it tells you: how much activity sits behind the site. A larger footprint usually means more customers, more transactions and more support conversations, and so more records.
A live check confirms the company is still operating, and flags signs of a closure or a new owner. The answer comes back as one of four statuses.
What it tells you: whether the company is still there to sign, so you never spend a week researching a company that closed last spring.
A score tells you how strong the evidence is. The nine factor groups tell you what kind of company stands behind it. Every result marks history, scale, knowledge assets, operational systems, customer systems, organization, industry value, expertise and activity status, so two companies with the same number can still be very different targets.
Strong on history, knowledge assets, industry value and expertise; weak on scale and customer systems. A natural fit for a buyer who wants expert writing and long project records, and a poor fit for one who wants customer conversations.
Strong on scale, operational systems and customer systems; weak on history and expertise. A natural fit for a buyer who wants support conversations and account activity, and a weaker fit for one who asks for ten years of records.
Each group carries one of four marks. Strong means clear public evidence in that area, medium means some, weak means little, and none means we found nothing to go on. A ten-person firm can be strong on history and expertise, and a large company can read weak on a group where it shows very little in public, so read the marks as evidence, not as a measure of size.
Read the groups as a profile rather than a checklist. A company that is strong across most groups is a safe first call for almost any buyer. A company with two or three strong groups and gaps elsewhere is often the better target for one specific brief, because the buyer who wants exactly those records will care less about the gaps. The score ranks the list; the groups tell you which buyer to think of when you reach each name.
Brokers spend a surprising share of their week explaining why a company is on a list. The groups, the likely data assets and the signals in plain words give you that sentence without extra research: "Twenty-two years online, strong on expertise and customer systems, likely holds research records and customer accounts." That is enough for a buyer to say yes or no to a closer look, and enough for a colleague to pick up the account without starting over.
AI data buyers do not buy websites. They buy what sits inside the systems a company runs: the help desk, the CRM, the issue tracker. We identify which systems each company runs, because a company that works through systems like these has years of records a buyer can review. The table shows the main system categories, what each one usually keeps, and why buyers care.
| System category | What it usually keeps | Why buyers care |
|---|---|---|
| Help desk and live chat | Tickets, chat transcripts, macros, satisfaction ratings | Real questions paired with real resolutions, over years |
| CRM and marketing automation | Account histories, deal stages, campaigns, activity logs | How a business sells, step by step, at company level |
| Issue trackers and developer tools | Issues, change discussions, release history | Code with the reasoning behind each change |
| Wikis and knowledge tools | Internal procedures, SOPs, how-to pages | Written expertise in a company's own words |
| Forum software | Threads, replies, accepted answers | Long conversations between users and staff |
| Learning management | Courses, quizzes, completion records | Structured teaching material with assessments |
| Recruiting systems | Job requisitions, application stages | Hiring workflows and job descriptions at scale |
| E-commerce | Orders, carts, refunds, catalogs | Transaction patterns and product data |
| Call and contact center | Call logs, recordings, transcripts | Spoken conversations, rare and in demand |
| Lab, study and quality systems | Samples, methods, results, deviations | Specialist work that never appears on the open web |
| Scheduling and document management | Bookings, contracts, reports, versioned files | Evidence of a business run through systems, not inboxes |
Buyers want to see how work played out over time: a client across several renewals, a product across many releases. Years of records are one of the clearest separators between a company that is worth a buyer's review and one that is not. Every result carries the three history fields below.
The year the company's domain first appears in our history. It is the earliest point from which the company could have been building records under that name online.
How many years have passed since then. This is the number to sort on when a buyer asks for several years of records, and the quickest way to separate an established firm from last year's launch.
The years the company was online before 2023, when human-written records are most valued. AI labs value records written before AI-generated text became common, so a company with many pre-AI years is worth a closer look.
The result gives first_seen_year and years_online for the domain. A company can be older than its domain: a firm that moved to a new domain in 2015 may have kept records for many years before that. Read years online as the least history a company could have, not the most.
A long history is not the same as long records. A company can lose years of email in a system migration. Treat history as how long records could exist; the buyer's review finds out how many do.
Footprint tells you how large a company's presence is. It is one part of the picture, never the whole score, so a company with a small presence and deep records still shows its strengths in the rest of the result.
That matters for brokers, because many good targets are mid-sized professional firms with a modest public profile and deep records. A small footprint does not hide a company with a client portal, a help desk and twenty years of history.
Lists age fast. Companies close, merge, let a domain lapse or leave a parking page behind. Every score includes a live check at the time it is scored, which confirms the company is still operating and flags signs of a closure or a new owner. The answer comes back as one of four statuses.
The company is operating from the domain today, with no sign of a closure or a new owner. This is the status to work first.
There are signs of a closure, a wind-down or a new owner. Who can sign may have changed, and timing matters.
The domain is parked or for sale. Whatever company used it is not operating from it now.
No working site answers on the domain. The API can also return error when there is no usable site to score.
A broker's time is the scarcest input in the pipeline. Practitioners say data deals take 60 to 90 days to close; a week spent researching and writing to a company that closed last spring is a week not spent on one that could sign. The live check removes those companies before you start.
It also catches a quieter problem: a domain that still looks like a website but no longer carries a business. A firmographic record cannot tell the difference. The live check can.
A high score on a company that closed last month is worth nothing to a broker, and a modest score on a company that was just acquired can be the most urgent call of the week. That is why activity status comes back as its own field. Filter on it first, then sort what is left by score, and keep the wind-downs and acquisitions in a separate pile where the conversation, and the person who can sign, are different.
Asking a general AI chatbot about each company is the first thing many brokers try, and for one company it can be a useful start. For a list of two thousand it breaks down in four places: speed, cost, consistency and what it never checks.
The two work well together. Score the whole list first, then use a chatbot or your own reading on the top fifty, where an hour of depth per company pays off. Manual research has the same shape: if careful research takes ten minutes a company, a list of 2,000 companies is more than 330 hours of work before the first email.
The score is not a report you read once. It is a sort key for a pipeline. These are the four ways brokers and sourcing teams use it most.
You already have a list: from a conference, a CRM export, a directory or an old campaign. Send every domain through the score endpoint and sort. The companies at the top show the strongest evidence of the records buyers ask for, so they get your first week, and the bottom of the list waits.
Sort by data_asset_score, highest first.
Every list has companies that closed, merged or let their domain lapse. Filter on status and stop writing to companies that are gone. Keep winding down or acquired in a separate pile: those companies need a different conversation, and sometimes a faster one.
Keep status = active; set aside winding_down_or_acquired.
A buyer asks for support tickets, CRM records or code history. Filter the likely data assets for that type, high confidence first, and you have a short list that matches the request instead of a whole sector. It turns a vague brief into fifty names.
Filter likely_data_assets for support_tickets, crm_records or code_history.
Grades turn a long list into piles you can act on: research A and B first, check C companies for one specific data type, and park D and E unless a buyer asks for something they clearly show. The factor groups tell you why a company landed where it did.
Group by grade, then read factor_groups.
If companies apply to your program, score each domain before your team spends time on the review. A grade, a status and the likely data assets on every application let the team read the strongest ones first and spot a parked or closed domain before anyone schedules anything. Batch scoring is on every plan, so a week of applications goes through in a few calls, on the same scale you use for your outbound targets.
No special tooling: a CSV, a key and a short script. The batch endpoint takes up to 100 domains per call and returns the results in the order you sent them, so a script sends your file in blocks of 100 and writes the results back out, ranked. Full reference in the API documentation.
import csv, time, requests API = "https://www.selldatatoai.com/api/v1/score/batch" HEAD = {"X-API-Key": "YOUR_KEY"} with open("targets.csv", newline="") as f: domains = [line["domain"] for line in csv.DictReader(f)] rows = [] for i in range(0, len(domains), 100): # up to 100 domains per call r = requests.post(API, json={"domains": domains[i:i + 100]}, headers=HEAD, timeout=60) if r.status_code == 429: break # monthly lookups used up job = r.json() while job["status"] != "done": # polling is free time.sleep(10) job = requests.get(job["poll"], headers=HEAD, timeout=60).json() for item in job["results"]: # same order you sent if item["status"] != "done": continue # invalid domain or error, skip it d = item["result"] rows.append({ "domain": d["domain"], "score": d["data_asset_score"], "grade": d["grade"], "status": d["status"], "assets": ";".join(a["type"] for a in d["likely_data_assets"]), }) active = [x for x in rows if x["status"] == "active"] active.sort(key=lambda x: x["score"], reverse=True) with open("ranked.csv", "w", newline="") as f: w = csv.DictWriter(f, fieldnames=["domain", "score", "grade", "status", "assets"]) w.writeheader() w.writerows(active) # Only the companies likely to hold support tickets: tickets = [x for x in active if "support_tickets" in x["assets"]]
| Rank | Domain | Score | Grade | Status | Likely data assets |
|---|---|---|---|---|---|
| 1 | harborline-claims.example | 88 | A | active | Support tickets, customer accounts |
| 2 | northgate-bio.example | 73 | B | active | Research records, knowledge base, customer accounts |
| 3 | ridgeway-engineering.example | 71 | B | active | Code history, knowledge base |
| 4 | copperleaf-legal.example | 57 | C | active | Customer accounts, CRM records |
| set aside | brightpath-analytics.example | 56 | C | winding_down_or_acquired | Separate track: who signs may have changed |
| dropped | oldmill-software.example | 18 | E | parked | No business on the domain |
A score is only useful if it changes what you do next. This is how we suggest reading grade and status together. It is guidance for a pipeline, not a rule inside the score.
| Result | What it usually means | What to do next |
|---|---|---|
| Grade A or B, active | Strong evidence across several groups: records in systems, years of history, a real footprint | Research first. Qualify the company against each buyer's published rules with check your company, then decide which program fits. |
| Grade C, active | Some strong groups and some gaps | Read the factor groups and likely data assets. A C with high-confidence support tickets can suit a buyer who asked for exactly that. |
| Grade D or E, active | Little public evidence of records, or a small footprint and short history | Keep for later unless a buyer asks for something the company clearly shows. Internal systems can be invisible from outside. |
| Winding down or acquired | The site suggests a closure, a wind-down or a new owner | Treat it as its own track. Find out who can sign now; timing matters more here than anywhere else. |
| Parked, unreachable or error | No operating business on the domain today | Drop it from outreach. Re-check later only if you know the company moved to another domain. |
Every plan uses the same index, the same score and the same fields. The only difference is how many lookups you get each month. Batch scoring of your own domain lists, up to 100 domains per call, is on every plan.
For brokers who qualify companies one by one, or score a list of a few thousand domains each month.
For brokers who work a pipeline: several new target files a month, plus a monthly re-check of the companies already in it.
For data companies that score prospect files and inbound applications at volume and load the results into their own tools.
A score you trust is one whose limits you know. These are the ones to keep in mind before you act on a result.
The score reads what a company shows in public. It never sees the records themselves, how clean they are, or what the company's contracts allow.
A help desk, CRM or code host used only by staff may not be identified. Read a weak group as "not visible", not "not there".
Some signals are not available for every company. The result shows what it is based on, so thin evidence reads as thin, not as a verdict.
The score reflects what a company shows at the time of the reading. It does not predict whether the company will grow, sell or close.
Only a buyer can price data, after it sees a manifest and samples. The score tells you which companies to look at first.
A high score says a company likely holds data buyers want. It says nothing about whether its owners would ever sell it.
Results are reused for 30 days. checked_at shows when the reading was taken, so a company that closed last week can still read active until the next reading.
No names, emails or phone numbers, ever. The score tells you which company to approach; finding the right person is your work.
We plan to add a distribution view to the demo that shows where a company's score sits among the domains in our index. It will answer the question brokers ask most after "what is the score?": is that number common or rare? Until it ships, the grade is the quickest way to read a score in context.
No. We publish what every result contains: the score, the grade, the nine factor groups by name, the likely data assets, history, activity status and the data systems we identify. The inputs, weights, point values, thresholds and the rules that combine the groups are our own. Every result still shows each factor group as strong, medium, weak or none, and lists the signals we found in plain words, so you can see why a company scored high or low without the formula.
A firmographic record tells you a company’s size, industry and location. It does not tell you what records the company keeps. The AI Data Value Score estimates the likely data assets, such as support tickets, CRM records, customer accounts or code history, identifies which data systems the company runs, adds years of history and a live check that the company is still operating, and puts all of it on one 0 to 100 scale.
For one company it can be a useful start. For a pipeline it is slow, it costs money per call, the same question can return different answers in different formats, and it does not systematically confirm that the company is still operating. The score is precomputed on one method, comparable across companies, verified active at scoring time and returned as JSON fields you can sort.
Each score includes a live check, at the time it is scored, that the company is still operating. Results are then kept for up to 30 days, so repeat lookups are fast. The response carries checked_at, the time of the reading, and cached, which tells you whether the result came from the last 30 days.
Yes. That is what the API is for. Put your domains in a CSV and send them to the batch endpoint, up to 100 per call. Domains scored in the last 30 days come back at once and the rest within a few minutes; you poll for them for free. Each valid, unique domain is one lookup: Basic includes 5,000 a month, Pro 25,000 and Scale 100,000. Then filter by status, sort by score and filter by the data type a buyer asked for.
Some signals are not available for every company. The result shows what it is based on: each factor group reads strong, medium, weak or none, so you can see where the evidence is thin, and the score still uses everything else we found. Read a weak group as not visible in public, not as proof that the records are absent.
No. A high score means the company shows strong public evidence of the kinds of records AI data buyers ask for. It is an estimate, not a valuation, not an offer and not proof that the owners want to sell. Each buyer reviews the actual records and decides acceptance, scope and price.
That is planned. We intend to add a distribution view to the demo that shows where a company’s score sits among the domains in our index, so you can see whether a score is common or rare. It is not live yet.
Try the score on a company you know in the free demo. When the result makes sense to you, send your own list through the API and sort your pipeline by the data buyers want.