How Any Get Paid works

Anyone can launch a coin through Any Get Paid and name somebody on one of fifteen networks. The coin is an ordinary pump.fun coin, with the same curve, the same trading and the same graduation. Every trade pays a creator fee, and pump.fun's own fee sharing program sends it to one address, at 100%, which is the address that belongs to whoever the coin names.

On three of the fifteen there is nothing at all for the payee to do: a pump.fun account is already a wallet, and an X or GitHub account already has a vault on pump.fun. On ten more the money still arrives on its own, into an address that is theirs; what they do is say which wallet to send it on to. On the last three the payee is not a person at all: the coin itself, an NFT collection, or a fundraiser.

On chain · Paid on Solana, with no claim to make.

Kols

pump.fun

pump.fun KOLs

Paid straight into the wallet their pump.fun account is signed in with.

NFTs

Magic Eden

NFT collections

Paid into an address worked out from the coin’s own mint, which buys the collection floor as soon as it holds enough.

Not one of these networks is read through a key of ours. Kick, Twitch, YouTube, GitHub, pump.fun, Spotify and the three fundraising platforms all answer an ordinary public request, and every figure on a page here was read from the network it belongs to and written down with the time it was read.

The directory is a starting list, not a limit. The launch form takes anybody those networks know about, whether they are filed here or not.

1. 1

   A wallet of their own

   A pump.fun account is signed in with a wallet, so the sharing config names that wallet and the SOL lands in it. Nothing to claim, no login here, nothing to set up. This is KolPaid.
2. 2

   pump.fun's vault for their account

   pump.fun keeps a fee vault for X and GitHub accounts, keyed to the account's numeric id, so a rename never moves anybody's money. The first coin launched for somebody opens their vault; they withdraw on pump.fun by signing in with that network. This is UsePaid and GitPaid.
3. 3

   The floor of a collection

   A coin can also be paired with an NFT collection, which has no wallet and is never handed anything. The config names one address at 100%, worked out from the coin's own mint, and the fees pile up there until they cover the cheapest one listed. That piece is then bought and stays at the same address. This is FloorPaid.
4. 4

   An address derived for them alone

   A Kick channel, a Twitch streamer, a YouTube channel, a Spotify artist, a TikTok account, a Telegram channel, a Discord server, a Patreon campaign, a game and a fundraiser have neither, so the coin pays an address worked out from one secret this site holds and that payee's own id. The same payee always gets the same address, nobody else is ever paid at it, and the balance is public. To have it sent on they name a wallet and put a short code where only they can put it.

An address that has never been used holds nothing, and the network will not let a transfer leave an account below rent. So the first coin launched for somebody on the third rail opens their account: enough SOL for the chain to keep it, once, out of the launcher's wallet. It is theirs from that moment and this site cannot take it back.

1. 1

   Pick a category, then somebody in it

   The search box under the fifteen reads that network live, so anybody it knows about can be named, listed here or not. Groups and organisations are refused: a vault belongs to a person or to one campaign.
2. 2

   Describe the coin

   Name, ticker, image, and an optional website (it defaults to their page on Any Get Paid). The image is squared and resized in your browser and pinned through pump.fun's own IPFS endpoint, so it looks the same on pump.fun and here.
3. 3

   Optional first buy

   Up to 10 SOL, in the same transaction as the create, so you are the first holder.
4. 4

   Sign

   Your wallet signs two transactions together: create_v2 with you as creator (plus the buy); and a fee share transaction that calls pump.fun's fee program (createSocialFeePda when a vault has to be opened, then createFeeSharingConfig and updateFeeShares) to hand 100% of creator rewards to that one address. Create and fee share cannot travel in one transaction: together they exceed Solana's 1,232 byte limit.

The server builds both transactions and checks, when they come back, that the bytes are exactly the ones it built. A wallet may add signatures and nothing else. If the chain would refuse the create, a validator is asked first and you are never sent to a wallet prompt that was always going to fail.

pump.fun program

6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P

Fee program

pfeeUxB6jkeY1Hxd7CsFCAjcbHA9rWtchMGdZ6VojVZ

Shareholders

exactly one, at 10,000 basis points

Config admin

the wallet that launched, never this site

Crank wallet

9Aic7dRg7hrVT67f6hCUCuKoq2EjZYoCPZFEqsn3564J

What the crank can do

pay the network fee for a push, and nothing else

What the crank holds

nothing yet, so automatic payments wait. A hundredth of a SOL is months of them.

The coin page reads the config back from the chain on every visit and says plainly whether the fees are pointed where the page claims. If they are not, it says so instead of hiding it.

Fees below pump.fun's own minimum, about 0.001 SOL, stay in the vault until the next trade adds to them. Once the vault clears it, a crank calls distributeCreatorFees and the program credits the shareholder in that same transaction. The crank wallet pays the network fee and touches nothing else; the launch set aside 0.004 SOL for that, so the sending never stalls for want of a few thousand lamports.

On the third rail the money now sits at an address with that payee's name on it. They go to Get paid, name a wallet, and put a short code in the one place only they can edit: the About section of their channel, their channel description, the story of the campaign. This site reads that page and either sees the code or does not. Nothing is emailed, nobody signs in here, and a code added an hour later is found by the next pass.

Spotify publishes nothing an artist can edit and this site can read, so a Spotify claim is looked at by a person. The address and the money in it work the same either way.

Push

a coin's fees sent out of its vault to the address the config names

Payout

what waited at a payee’s own address, sent on to the wallet they gave

Milestone

written every $20 of lifetime creator fees, so the figure is on record

Every dollar figure on this site is the SOL of a receipt at the price read when that receipt was written. Nothing is modelled, projected or estimated, and a page with nothing to show says so rather than filling itself.

1. 1

   Read the config

   Open any coin page: the shareholder and the share are read from the chain in front of you, and the address links to the explorer.
2. 2

   Watch the address

   A payee's page shows the address their coins pay and its balance. It is an ordinary Solana account; the explorer shows every lamport in and out.
3. 3

   Follow a receipt

   Every push and every payout links its transaction. The amount on the receipt is the amount the chain moved.
4. 4

   Run the dry run

   npm run dry-run builds a real launch for every category, then decodes the fee share transaction again out of the bytes a wallet would sign and prints who it pays and at what share. Nothing is sent.

/api/payees?category=twitch

One category’s directory. It refuses to answer without a category, so a list can never be a mix.

/api/search?q=&category=

The same search the box uses, live against that network.

/api/coins, /api/coins/[mint]

Coins launched here, with the address each one pays and what the chain says about it.

/api/receipts

The ledger: every push and every payout, with its transaction.

/api/stats?category=

Totals and a daily series.

/api/activity

What has just happened here: launches, payments, claims, votes, floor buys.

/api/vault/[mint]

What a coin’s vault holds, the round running on it and how the votes stand.

/api/floor/[mint]

What a coin has put aside, what its collection’s floor costs right now, and what it has bought.

/api/wallet/[address]

What an address has been paid through this site.

Every endpoint that lists anything takes ?category=, and the figures in them are the same ones on the pages: read from the network or the chain, with the time they were read.

Does Any Get Paid take a cut?

No. The config names one shareholder at 100%; there is nowhere for a cut to go.

Can a coin be repointed later?

No. The config's admin is the wallet that launched it, not this site.

What if the payee wants nothing to do with it?

Then they never claim, and the SOL sits at an address only they can be paid at.

What if they change their handle?

Nothing breaks. The money is keyed to the account id the network itself uses.

Can a group or an organisation be named?

No. A group has no one wallet and an organisation is not a person.

Where do the follower counts come from?

The networks themselves, read without a key and written down with the time they were read.