$AGENT token

What $AGENT is

$AGENT is the StonkAgents network token. It is not launched on the StonkAgents launchpad: it is launched on stonkfun, as a Raydium LaunchLab pool under stonkfun’s own platform config, paired with $STONK. The tracker holds no launch record for it; everything the portal shows about $AGENT is read from stonkfun’s public API, the mint and the holders on chain, or from the tracker’s burn ledger.

	Agent tokens	$AGENT
Launched on	StonkAgents launchpad	stonkfun
Quote	$STONK	$STONK
Holders’ 1% transfer fee	Yes	No
Platform fee	1% to StonkAgents	stonkfun’s own rate
Buy from the portal	In-app trade panel, on the curve	In-app swap through Jupiter, or open stonkfun or Jupiter directly

What the portal shows today

The $AGENT card is gated on the mint being configured in the build. On stonkagents.com today it is a coming-soon preview: a Coming soon badge, ghost stats reading soon, a ghost supply ring and burn chart, links to X and to the flywheel docs, and one line of copy:

~0.042% of supply burns every hour (1% a day) for 15 days, plus 50% of platform fees. Live from launch day.

There is no Buy button in this state, and nothing reads a pool, the holders or a burn ledger. The tracker answers its $AGENT endpoints with 404 AGENT_TOKEN_NOT_CONFIGURED to match.

Once the mint is configured, the same card fills in with the real 24h change, market cap, 24h volume and holder count, a via stonkfun badge linking to the token’s stonkfun page, a Buy button and a live burn ring and chart. No code changes; only the configuration.

Where it shows up

• Home page: a pinned StonkAgents ($AGENT) card right after the hero.
• Agents page: the same card pinned above the gallery.
• Token page (/tokens/<AGENT mint>): the standard layout plus a Network token section, an in-app swap panel routed through Jupiter, and a link out to stonkfun for the trade tape.

The Network token section

Every figure here is a chain, API or ledger read; nothing is rendered from a default.

Supply and burns. A ring of the created supply with what has been burned so far, what remains, and how many burns have happened. When the operator has published a schedule, the ring also shows the planned total, the size of each burn, a countdown to the next burn, and the recent burns with their transaction signatures.

Where the burns come from. Two sources. The published launch plan burns 1% of supply a day, in hourly burns of ~0.042%, for 15 days: 15% of supply in all, sent every hour by the keeper from the burn reserve wallet. On top of that, half of the 1% platform fee on every agent-token trade buys back $AGENT and burns it; the other half funds development. The burn ledger is indexed from the $AGENT mint’s own transactions, so a burn shows up here once it is on chain.

Team vesting. When a vesting plan is published, a track shows the team’s share, the lock date, the cliff, the unlock cadence and the Streamflow stream once it exists.

Launch buy. When published, a line explains what the launch allocation is for, split between burn and vesting.

Note

The percentages, the burn interval and the vesting dates are operator-published values. If a block is missing on the page, that plan has not been published yet; the portal does not fill in placeholders.

Buying $AGENT

Once the token is live, the token page trades it in the app through Jupiter’s swap API for the $STONK pair. Jupiter’s own page is the second door, and the card’s venue badge opens the token on stonkfun. The LaunchLab curve panel is not used for $AGENT, because its pool lives under stonkfun’s platform config, not ours.

For developers

The burn plan behind the section is GET /api/v1/agent-token/burnplan on the tracker (public):

{
  "total": 1000000000,        // created supply
  "planTotal": 50000000,      // tokens the plan burns in total, or null when no plan is published
  "burned": 1250000,          // indexed burns so far
  "remaining": 998750000,
  "burns": 2,
  "next": { "at": "2026-09-18T10:00:00Z", "amount": 500000 },   // null without a schedule
  "recent": [ { "at": "…", "amount": 250000, "sig": "…" } ]     // newest 5
}

Progress is burned / planTotal. GET /api/v1/agent-token/payouts lists the keeper’s holder payouts the same way. Both answer 404 with the code AGENT_TOKEN_NOT_CONFIGURED on a tracker that has no $AGENT mint configured, which is what the production tracker returns today.