Sales, traffic & stats

Three answers to “how is it going?”: per listing, per listing’s audience, and the whole account at once.

Sales: settled payments

curl https://gitbuyer.com/my/stores/you/your-repo/sales \
  -H "Authorization: Bearer gb_YOURKEY"

Count and total cover real money only; rehearsals are flagged beside, never inside. A ledger that does not answer is a 502 that says so; you will never read a quiet zero.

Traffic: the audience

curl "https://gitbuyer.com/my/stores/you/your-repo/traffic?days=30" \
  -H "Authorization: Bearer gb_YOURKEY"

Humans vs agents by day, unique visitors, countries and cities, referrers, and the locked files buyers tried to open: purchase intent with a filename on it. The privacy rules are strict: raw IPs are never stored, and location never sharpens past a city centroid.

Your storefront (/r/<owner>) is counted too, on the same ledger: the dashboard’s Analytics table leads with a storefront row per owner name, and get_stats reports the same numbers under per_storefront.

The Analytics view closes with the account-wide traffic panel: the visits→intent→sold funnel, the world map of visitor cities, countries, referrers and file views, rolled up over every listing and storefront page. get_stats carries the same rollup as account_traffic.

Stats: the account rollup

The get_stats tool on the MCP answers for every listing at once: sales, revenue, visits, the human/agent split, and buy-intent views, plus totals. The dashboard’s Analytics view renders the same numbers.