Trending and newly profiled Solana tokens

What Solana tokens are being pushed right now: DexScreener's top boosted tokens (paid promotion, ranked by boost amount - a signal of marketing spend, not quality) and the latest token profiles (fresh listings with a filled-in profile), both filtered to Solana. Send POST /api/sol-trending with no required fields (2 optional) and pay $0.003 per call over x402 or MPP (there is no free tier). It returns a JSON object with boosts, profiles, counts, source and fetchedAt.

Each row carries the mint, DexScreener URL, description snippet and links. Feed the mints into sol-token-safety to separate the promoted from the sound. Keyless; two small DexScreener reads in parallel.

Category: Crypto & onchain data · Tags: solana trending boosts new-tokens memecoin discovery spl · Also found as: trending-solana-tokens solana-trending-tokens

TRY IN PLAYGROUND →

Parameters

Example request

curl -i -X POST https://agent402.tools/api/sol-trending \
  -H "Content-Type: application/json" \
  -d '{"limit":10}'

Without payment this returns HTTP 402 Payment Required with the exact price for sol-trending; any x402 v2 or MPP client pays it and retries.

Example response

{
  "boosts": [
    {
      "mint": "918p...pump",
      "boostAmount": 500,
      "description": "The cats have arrived",
      "links": [
        {
          "type": "website",
          "url": "https://example.com"
        }
      ],
      "url": "https://dexscreener.com/solana/918p..."
    }
  ],
  "profiles": [
    {
      "mint": "AiRG...pump",
      "description": "",
      "communityTakeover": false,
      "links": [
        {
          "type": "twitter",
          "url": "https://x.com/..."
        }
      ],
      "url": "https://dexscreener.com/solana/airg..."
    }
  ],
  "counts": {
    "boostsSolana": 24,
    "boostsAll": 30,
    "profilesSolana": 30,
    "profilesAll": 30
  },
  "source": "dexscreener",
  "fetchedAt": "2026-08-22T12:00:00.000Z"
}

From an MCP client

catalog.call {
  "slug": "sol-trending",
  "params": {
    "limit": 10
  }
}

The hosted connector at https://agent402.tools/mcp needs a payment for sol-trending; the stdio package pays it from a wallet or from AGENT402_CREDITS_KEY. Local install: npx -y agent402-mcp.

Errors and behavior

• Every field is optional. An input the tool rejects returns an HTTP 4xx whose body carries error, tool, expected, required and example.
• A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement is cancelled when the tool fails. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
• Wallet-only: this tool reaches the network or stored state, so it has no proof-of-work tier. A prepaid card-credits key (Authorization: Bearer a402_...) also pays it.
• A GET or HEAD to /api/sol-trending returns the same 402 quote, so the price can be read without a body.
• An Idempotency-Key header makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/sol-trending", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "limit": 10
  }),
});

Related tools