receipts

Paste any X username or profile link and see the account's real reach: average and median views, engagement rate, reach per follower, top posts, and the coins and accounts they mention most. Every result page has a share card, a "Share on X" button, and a preview image that shows up when the link is posted on X.

Data comes from the official X API. One full check reads 1 profile and up to 20 posts. At current pay-per-use prices that's about $0.11 per account, and the app caches each account for 12 hours, so repeat views of the same account are free.

---

Try it free first (demo mode)

You can see the whole design with fake numbers before paying X anything. Deploy it (steps below) and set X_DEMO=1. Every page then shows a "Demo data" banner.

---

Step 1 · Get your X API key

1. Go to developer.x.com and sign in with your X account.
2. Create a developer account, then create a Project and an App inside it.
3. Open the app → Keys and tokens → generate the Bearer Token. Copy it somewhere safe. Never post it publicly.
4. In the Developer Console, add credits (pay-per-use is prepaid). $5–10 is plenty to start, about 50–90 account checks. Your credits are also your spending cap: when they run out, lookups stop until you top up.

Step 2 · Put the code on GitHub

1. Create a free account at github.com if you don't have one.
2. Click New repository, name it receipts, keep it Private, and create it.
3. On the empty repo page, click uploading an existing file, then drag in everything from this folder (not the node_modules or .next folders, if you created them). Click Commit changes.

Step 3 · Deploy on Vercel (free)

1. Go to vercel.com, sign up with your GitHub account.

2. Click Add New → Project, pick the receipts repo, and click Import.

3. Before clicking Deploy, open Environment Variables and add:

   Name	Value
   X_BEARER_TOKEN	your Bearer Token from Step 1
   POSTS_LIMIT	20
   CACHE_SECONDS	43200
   RATE_LIMIT_PER_HOUR	30

   For demo mode instead, add X_DEMO = 1 and skip the token.

4. Click Deploy. After about a minute you get a link like receipts-yourname.vercel.app. That's your app.

5. Optional: add NEXT_PUBLIC_SITE_URL = your final link (for example https://receipts-yourname.vercel.app) and redeploy, so share previews always use the right address.

To change a setting later: Vercel → your project → Settings → Environment Variables, edit, then Deployments → ⋯ → Redeploy.

Want your own domain like receipts.xyz? Buy it anywhere, then Vercel → Settings → Domains → Add.

---

Settings

Variable	What it does	Default
X_BEARER_TOKEN	Your X API key. Required for real data.	—
POSTS_LIMIT	How many recent original posts to analyze (5–100). More posts = more accurate, more credits.	20
CACHE_SECONDS	How long to reuse an account's results. Longer = cheaper.	43200 (12h)
RATE_LIMIT_PER_HOUR	Max checks per visitor per hour. Protects your credits.	30
X_DEMO	1 = fake data, no X calls.	0
NEXT_PUBLIC_SITE_URL	Your site's address, for share previews.	—

What the numbers mean

• Avg / median views: from the latest original posts only. Replies and reposts are left out so one viral reply doesn't skew it.
• Engagement: likes + reposts + replies + quotes + bookmarks, divided by views.
• Views per 100 followers: average views ÷ followers × 100. Under 10 often points to inactive or bought followers. 10–30 is healthy, 30+ is strong.
• Coins / accounts mentioned: counted from cashtags ($INJ) and @mentions in those same posts.

Run it on your own computer (optional)

Needs Node.js 18 or newer.

npm install
cp .env.example .env.local   # then fill in X_BEARER_TOKEN, or set X_DEMO=1
npm run dev                  # open http://localhost:3000

There's also a JSON endpoint: /api/profile?u=username.