Data dictionary

Every field delivered in a Catamount Data CSV: what it means, how it gets populated, how many of the 8,594 master-list records have it, and where it can mislead.

Summary

FieldTypePopulated%Source
namestring8,594100.0Self-supplied
xHandlestring8,50398.9Self-supplied
xBiostring6,72978.3Public X profile
roleenum6,41174.6Derived from X bio
linkedinURL6,04670.4Self-supplied
companystring5,86668.3Derived from X bio
xLocationstring4,42751.5Public X profile
xFollowersinteger3,92145.6Public X profile
telegramTitlestring3,06335.6Public Telegram profile
telegramHandlestring2,70931.5Inferred — see caveat
company2string2,01723.5Derived from X bio
telegramBiostring1,86521.7Public Telegram profile
websiteURL1,78820.8Public X profile

Field definitions

name

8,594 of 8,594 — 100.0%

The person's name as they entered it themselves. Always present, but not always a full legal name: 26.9% are a single word with no surname, and 9.7% are the person's X handle rather than a name, because that is what they typed.

xHandle

8,503 of 8,594 — 98.9%

X (Twitter) username without the leading @. Supplied by the person and used as the primary key for deduplication. The master list contains zero duplicate X handles.

xUrl

Canonical profile URL, https://x.com/{xHandle}. Present on 80.6% of records as a stored field; derivable from xHandle for the rest.

xDisplayName

The display name on the public X profile at time of enrichment, which frequently differs from name and often carries emoji, a current employer, or a conference location tag.

xBio

6,729 of 8,594 — 78.3%

The public X biography, verbatim, at time of enrichment. This is the highest-signal field in the dataset for judging whether a contact is worth approaching, and it is where company affiliations most often appear in practice — frequently as @handle mentions rather than as company names. Searching only the company column will miss many genuine affiliations.

role

6,411 of 8,594 — 74.6%

A normalised role label inferred by a language model from the X biography. Values include Founder, BD, Marketing, Engineer, Investor, Developer, C-Suite, Community Manager, Researcher, Advisor. Founder is the most common. This is a derived judgment, not a self-reported job title, and it reflects the bio at time of enrichment.

linkedin

6,046 of 8,594 — 70.4%

LinkedIn profile URL as supplied by the person. Not verified against the person's name. Twelve records hold more than one URL in a single cell.

company

company2

5,866 (68.3%) and 2,017 (23.5%)

Primary and secondary company affiliation, inferred by a language model from the X biography. company2 typically captures a previous employer or a second project. Because these are derived from a bio, a person who has changed jobs since enrichment may show a stale employer.

telegramHandle

2,709 of 8,594 — 31.5%

Read this before relying on the field. These handles are inferred, not confirmed. They are produced by testing whether an account with the same username as the contact's X handle exists on Telegram. A matching username is not proof that the account belongs to the same person.

In a 300-contact audit, roughly two thirds of matched Telegram accounts had an empty public profile, leaving nothing to corroborate the match against. Among the accounts that could be checked, about 6% were demonstrably the wrong person — in one case the contact's own X biography named a different Telegram handle than the one held.

Treat every Telegram handle in this dataset as a lead to confirm, not an address to trust. X and LinkedIn are both more complete and more reliable. Full detail on the methodology page.

telegramTitle

telegramBio

3,063 (35.6%) and 1,865 (21.7%)

The display name and biography on the matched public Telegram profile at time of enrichment. These are the fields to read when deciding whether an inferred Telegram handle is plausibly the right person: a title and bio that corroborate the X profile is meaningful evidence, and an empty profile is no evidence at all.

For contacts enriched from September 2026 onward these are populated whether or not the identity check accepted the handle. Previously a rejected candidate was discarded along with its profile evidence, which removed the very thing you would use to judge it — for exactly the ambiguous cases where judging matters.

telegramCandidateHandle

contacts enriched from September 2026 onward

A Telegram handle that was found but did not pass the identity check. It is kept in its own column, separate from telegramHandle, so a verified handle and an unverified one can never be confused.

Treat it as a lead to check, not an address to message. Read it alongside telegramConfidence and the profile fields, and see the verification guide for the thirty-second check.

telegramConfidence

telegramConfidenceReason

contacts enriched from September 2026 onward

What the identity check concluded, and why.

ValueMeaningWhere the handle appears
acceptedSpecific cross-profile evidence supports the match, with no contradictiontelegramHandle
riskySparse, generic or ambiguous evidence — commonly an empty Telegram profiletelegramCandidateHandle
rejectedA contradiction, or an organisational rather than personal accounttelegramCandidateHandle
unscoredThe check could not complete — a provider error or timeouttelegramCandidateHandle
emptyContact predates the check (August 2026) and was never adjudicatedtelegramHandle, unadjudicated

telegramConfidenceReason is a one-line explanation from the evaluator — for instance, that the Telegram profile carried only a first name with no biography, leaving nothing to corroborate. It is there so you can disagree with the verdict on evidence rather than take it on trust.

Note the distinction between an empty value and unscored: empty means the check never ran, unscored means it ran and could not decide. Those are different kinds of unknown.

website

1,788 of 8,594 — 20.8%

Personal or company URL taken from the link field of the public X profile.

xFollowers

3,921 of 8,594 — 45.6%

Follower count at time of enrichment. Always an integer where present. Roughly 23% of records that carry a value are under 100 followers.

xLocation

4,427 of 8,594 — 51.5%

The free-text location string from the public X profile. Self-declared and unnormalised — values range from "Singapore" to "Decentralized" to "worldwide".

xVerified

Whether the X account carried a verification badge at time of enrichment. Note that on X this indicates a paid subscription, not identity verification.

category

The vertical a contact was assigned to — DeFi, Infrastructure, CEOs & Founders, Marketing & Growth, VCs & Investors, Developers, BD & Partnerships, AI, or Gaming. A contact can appear in more than one vertical list.

sourceEvent

The event a contact was first associated with, where retained. Present on a minority of master-list records; complete on event-specific lists.

Fields that are never sold

Email addresses and phone numbers are not included in any list. An email key appears in the delivered file structure for a subset of records and is empty on every one of them.

Last updated 6 September 2026. Coverage figures measured directly against the 8,594-record master list on that date. See also the coverage report and methodology.