Pre-launch

$SOUP

The utility token for soups.tools — a tokenized agent on pump.fun that earns a share of every paid action and uses it to buy + burn $SOUP. Holders capture platform usage as supply pressure.

Total supply
1,000,000,000SOUP
pump.fun mints fixed 1B at launch
Bundled at launch
15%
Public buys access 85% via the bonding curve
Agent buyback rate
50%
of every paid agent action goes to $SOUP buy + burn

Allocations

All four bundled wallets are bought from the bonding curve in a single Jito bundle at launch — five transactions in one block. No after-the-fact dispersals from the dev wallet. The full distribution is visible on-chain from the very first slot.

Wallet
%
Tokens
Pubkey

Why bundle vs. disperse? Most projects launch with the dev wallet only and quietly send to marketing/promo/coffee wallets later. Even with good intentions, that pattern looks identical to a rugpull setup mid-launch — and the team has to explain itself. Bundling makes the entire initial distribution atomic and verifiable from block zero.

Why Jito specifically? Jito's bundle primitive is the only way to guarantee all five txs land in the same slot or none at all. That atomicity is what makes the on-chain distribution clean. soups.tools uses this same bundle flow for every user-launched coin — we're eating our own dogfood.

Dev vesting

The 10% dev allocation is locked on-chain via Streamflow immediately after the launch bundle lands. The dev wallet has no access to it — vested $SOUP drips out to a separate long-term holding wallet on a public schedule.

Cliff
90days
Zero unlock during this period
Total duration
365days
From launch to fully vested
Unlock cadence
Daily
Linear after cliff
Schedule
  • Day 0–90: 0% unlocked (cliff)
  • Day 91–365: 75.3% unlocks linearly across 275 days
  • Day 365+: fully vested

The Streamflow contract URL will be published here the moment the lock tx lands. Anyone can verify the schedule, recipient pubkey, and remaining-locked balance directly on Streamflow's dashboard — soups.tools doesn't mediate that view at all.

Agent buyback (utility)

$SOUP is a pump.fun tokenized agent — a coin whose mint is registered as a service that charges users for actions. Every paid agent call flows 50% to a buyback PDA that swaps SOL → $SOUP on the open market and burns it.

What the agent does for soups.tools:

  • Smart-exit babysitter — pay per position, agent runs your exit ladder server-side 24/7 (set it and close your laptop)
  • Snipe-on-trigger — pay to register criteria (deployer wallet, name regex, MC window); agent fires bundled buys when matched
  • Auto-bumper — pay for N minutes of micro buy/sell to keep your launch surfaced on pump.fun
  • Concierge launch — one fee, agent handles clone + time + snipe + tweet + bump

More platform usage = more buyback pressure. Vested or unvested, every $SOUP holder benefits from supply contraction.

Transparency note

We could have launched the way most pump.fun coins do — dev buys, then over the following minutes/hours sends little chunks to other wallets. Cheaper, simpler, opaquer.

Instead, every wallet buys directly from the bonding curve in the launch bundle. There is no “dev → marketing” transfer in our tx history because there doesn't need to be — those buys are independent transactions in the same atomic bundle. Anyone scanning our dev wallet's history will see: buy, lock-into-Streamflow, no other outflows ever. That's the cleanest possible signal we can ship.

And we pay the same Jito tips and platform fees as every other soups.tools user. No special treatment.

Not financial advice. $SOUPis a utility token with no guaranteed value. Buy only what you'd be comfortable losing — memecoin market dynamics are unforgiving.