Fame.am
Claim profile
Transparency

Data Sources

Every number on Fame.am is grounded in real public signals. Here's exactly where the data comes from, what we collect, and why each source matters.

See also: About Fame.am

WD

Wikidata

WIKIDATA_LOOKUP

The primary knowledge graph. Wikidata provides structured facts about people — birth dates, nationalities, occupations, multilingual labels, sitelinks across language editions, and linked external identifiers.

Data collected
  • ✓Birth/death dates
  • ✓Nationality & country
  • ✓Occupation labels
  • ✓Multilingual sitelinks (language footprint)
  • ✓Social & platform profile links
  • ✓Profile photo URL
  • ✓Short biography
Used for
  • →Language footprint score component
  • →Historical depth signal
  • →Profile completeness
  • →Bio and image on profile pages
  • →Linking out to other social platforms

Wikidata sitelinks are a strong proxy for cross-lingual fame — a person covered in 40 language editions of Wikipedia has more global reach than one in 3.

WP

Wikipedia Pageviews

(via Wikidata)

Wikipedia article access statistics via the Wikimedia REST API. Monthly and weekly pageview totals across all language editions show how often the public looks someone up.

Data collected
  • ✓Monthly pageviews (last 30d)
  • ✓Weekly pageviews (last 7d)
  • ✓Year-to-date pageviews
  • ✓Per-language breakdown
Used for
  • →Public knowledge demand score (20% of Fame)
  • →Momentum score — Wikipedia pageview growth
  • →Historical score — long-term pageview total

Wikipedia pageviews are one of the most reliable fame signals because they represent active search intent across every language.

GH

GitHub

GITHUB_PROFILE

GitHub's REST API provides public profile data for developers, open-source contributors, and tech figures.

Data collected
  • ✓Follower count
  • ✓Following count
  • ✓Public repository count
  • ✓Total stars on repos
  • ✓Bio and location
Used for
  • →Social audience score (contributor to 25% of Fame)
  • →Profile data enrichment for tech profiles

Works without an API key at 60 requests/hour. Set GITHUB_TOKEN for 5,000 requests/hour throughput.

YT

YouTube

YOUTUBE_CHANNEL

YouTube Data API v3 pulls channel statistics for creators, musicians, and public figures with a YouTube presence.

Data collected
  • ✓Subscriber count
  • ✓Total video views
  • ✓Video count
  • ✓Channel description
Used for
  • →Social audience score
  • →Follower count on Fame profile

Requires YOUTUBE_API_KEY (Google Cloud Console, YouTube Data API v3). Free quota: 10,000 units/day.

SP

Spotify

SPOTIFY_ARTIST

Spotify Web API retrieves artist popularity and audience data for musicians and podcasters.

Data collected
  • ✓Monthly listeners
  • ✓Popularity score (0–100)
  • ✓Follower count
  • ✓Artist genres
Used for
  • →Social audience score
  • →Follower count for music profiles

Requires SPOTIFY_CLIENT_ID and SPOTIFY_CLIENT_SECRET (Spotify for Developers dashboard).

TW

Twitch

TWITCH_CHANNEL

Twitch Helix API fetches channel metrics for streamers and gaming content creators.

Data collected
  • ✓Follower count
  • ✓Total stream view count
  • ✓Broadcaster type (partner/affiliate)
  • ✓Channel description
Used for
  • →Social audience score
  • →Follower count for streaming profiles

Requires TWITCH_CLIENT_ID and TWITCH_CLIENT_SECRET (Twitch Developer Console).

TM

The Movie Database (TMDb)

TMDB_PERSON

TMDb's person API enriches film and television profiles with photos, biographies, and credit lists.

Data collected
  • ✓Profile photo
  • ✓Biography text
  • ✓Known for department (Acting, Directing, etc.)
  • ✓Film & TV credits
Used for
  • →Profile image when no Wikidata image exists
  • →Biography text
  • →Profile completeness score

Requires TMDB_API_KEY (free account at themoviedb.org). The free tier provides generous rate limits.

GT

Google Trends

TREND_PULL

Google Trends normalized search interest data, pulled for the person's full name over 90-day windows.

Data collected
  • ✓90-day normalized interest (0–100)
  • ✓7-day average interest
  • ✓30-day average interest
  • ✓Peak interest in period
  • ✓Week-over-week change (%)
Used for
  • →Search interest score (20% of Fame)
  • →Momentum score — search trend 7d
  • →Trend direction (rising/falling/stable)

Google Trends returns normalized values (100 = peak search interest). A rate-limit (429) auto-reschedules the job 30 minutes later rather than failing.

Privacy & attribution

  • · All data collected is publicly accessible via each platform's official API or public pages.
  • · We do not collect private messages, private account data, or any information not explicitly public.
  • · Profiles can be claimed by the person they represent for corrections or removal requests.
  • · Data is refreshed on a rolling cadence — high-fame profiles more frequently than long-tail.

Questions? [email protected] · About →