API

GET /api/stats

The totals in one object. No parameters, no authentication, cached for a few seconds.

Request

GET /api/stats

Takes no parameters. Anything in the query string is ignored.

Response

200 application/json

{
  "tokens": 128,
  "recipients": 301,
  "claimedAccounts": 44,
  "sweptLamports": "91250000000",
  "paidLamports": "40100000000",
  "burnedLamports": "3900000000",
  "owedLamports": "29000000000",
  "unclaimedLamports": "28540000000",
  "launches24h": 9,
  "updatedAt": "2026-09-29T12:00:00.000Z"
}

Those figures are shape, not data. For what the endpoint returns right now, see Live response below or call it yourself.

Field	Type	Meaning
`tokens`	number	Tokens launched and confirmed here, hidden ones included
`recipients`	number	Distinct handles named on at least one token
`claimedAccounts`	number	Distinct X accounts that were named and have signed in
`sweptLamports`	string	Creator fees collected by confirmed sweeps, all tokens, all time
`paidLamports`	string	Payouts confirmed on chain
`burnedLamports`	string	SOL spent on buys that were then burned, recipients and platform buyback together
`owedLamports`	string	Credited to recipients and not yet confirmed as paid or spent on a burn. Payouts queued or in flight and burn orders waiting for their buy are inside it. The same figure the proof of reserves checks the treasury against
`unclaimedLamports`	string	Balances nobody has claimed or routed yet: credited, minus payouts that have not failed, minus every recipient burn order. The sum of what each account’s page shows as waiting to be claimed
`launches24h`	number	Tokens launched in the last 24 hours
`updatedAt`	string	When these figures were computed

Live response

Read from this endpoint right now. Each cell says "No data yet" rather than showing a zero it cannot justify.

Tokens launched

No data yet

Fees swept

No data yet

Paid out

No data yet

Waiting to claim

No data yet

Rendered from the same GET /api/stats you can call yourself.

Notes and caveats

Swept is not paid. sweptLamports includes the platform’s share, money still waiting in balances, and money routed to burns.
Paid means confirmed. A queued payout, and one that has been sent but not yet confirmed, is still inside owedLamports and not in paidLamports: a sent payout can still expire without landing, and its amount is then owed on the payout that replaces it.
Owed is not unclaimed. owedLamports minus unclaimedLamports is the money already claimed or routed to a burn that has not left the treasury yet.
Unswept fees are nowhere here. Fees still in the vaults are per token, as vaultLamports on GET /api/tokens.

These are historical totals, not a forecast. Nothing here is a rate of return, and nothing on this site projects what a token or a recipient will earn.

Caching and limits

Property	Value
Cache-Control	`public, max-age=0, s-maxage=10, stale-while-revalidate=30`
Server memo	Up to 10 seconds per instance, so a spike is one query rather than thousands
Rate limit	120 requests per minute per IP

Example

curl and jq

curl -s https://slicepad.fun/api/stats | jq

# owed to recipients, in SOL
curl -s https://slicepad.fun/api/stats \
  | jq -r '.owedLamports' \
  | awk '{printf "%.9f SOL\n", $1 / 1e9}'