Identify the dev wallet behind a Solana token, check their past launches, success rate, and funding source — with the Noesis /dev analysis.

Bot /devREST GET /api/v1/token/{mint}/dev-profileMCP token_dev_profile

How to profile the dev of a Solana meme coin

TL;DR. Noesis's /dev analysis identifies the creator wallet of any Solana token, then returns their past token launches, success rate (tokens still live), average bonding curve progress, funding source, and Solscan identity. A single call to GET /api/v1/token/{mint}/dev-profile tells you if the dev is a one-token hobbyist, a serial launcher with a history of dead projects, or a known KOL funded from a specific CEX.

Why dev profiling matters on Solana

Every pump.fun launch has a creator wallet, and most of them are not public. Knowing who launched a token is the single most useful piece of context for judging whether to trust it:

/dev surfaces all of this from the token mint alone. You don't need to know the dev's address upfront — the analysis extracts it.

What does /dev return?

The analysis pulls five layers of dev context:

  1. Dev wallet identity — address, any Solscan label, any KOL-cache match (known dev / builder / trader)
  2. Past launches — every token the dev has previously created on pump.fun / Solana launchers, with their current state
  3. Success rate — percentage of prior launches that are still trading above a bonding-curve threshold
  4. Funding source — where the dev wallet's SOL came from originally (CEX, another wallet, protocol)
  5. Wallet age / activity — how long the wallet has existed and its general trading profile

This is strictly on-chain — no Twitter scraping, no speculation, no off-chain identity.

How does Noesis detect the dev wallet?

/dev resolves the creator address by walking three paths in order:

Once the dev wallet is resolved, Noesis fans out:

How to run the analysis

Telegram bot

/dev EPjFWdd5...

Typical output:

🧑‍💻 Dev Profile
Creator: 8hJk...2mQp · "TokenFactory"

Created coins: 14
  Graduated: 3
  Still on curve: 11

Funded by: Kucoin · 0.5 SOL
First activity: 6 days ago

REST API

curl -H "X-API-Key: $NOESIS_API_KEY" \
  "https://noesisapi.dev/api/v1/token/EPjFWdd5.../dev-profile"

MCP

token_dev_profile(mint="EPjF...1v")

or prompt:

Profile the dev of token EPjF...1v. List their past launches, success rate, and how their wallet was funded.

SDKs

TypeScript

import { Noesis } from "noesis-api";
const noesis = new Noesis({ apiKey: process.env.NOESIS_API_KEY! });
const dev = await noesis.token.devProfile("EPjFWdd5...");
console.log(`creator: ${dev.creator}`);
console.log(`created ${dev.created_coins.length} coins`);

Python

from noesis import Noesis
noesis = Noesis(api_key=os.environ["NOESIS_API_KEY"])
dev = noesis.token.dev_profile("EPjFWdd5...")
print(dev["creator"], len(dev["created_coins"]))

Rust

let client = noesis_api::Noesis::new(api_key);
let dev = client.token_dev_profile("EPjFWdd5...").await?;

Understanding the output

Graduation rate = created_coins.filter(c => c.complete).length / created_coins.length. Compute client-side.

How to combine /dev with other commands

Chain 1 — Serial launcher detection

/dev <mint>                          see prior launches
  → /dev <prior_mint_a>              compare profile across past tokens
  → /dev <prior_mint_b>              establish baseline behavior

Chain 2 — Dev + team overlap

/dev <mint>                          get dev wallet
  → /team <mint>                     run team analysis
  → check if dev_wallet appears in the linked cluster

Chain 3 — Dev funding graph

/dev <mint>                          funder = "Kucoin"
  → /links <dev_wallet>              trace all SOL transfer connections
  → identify wallets funded by the dev (co-conspirators)

Chain 4 — Dev → cross-holder ecosystem

/dev <mint>                          get prior launches
  → /cross <mint> <prior_mint>       find wallets holding both — likely team / close friends

When /dev false-positives or misses

Caveats

FAQ

What does a good dev profile look like? Either: (1) an anonymous first-time dev on a fresh wallet (no prior track record but no bad one either), or (2) a labeled KOL with public accountability. The worst profile is a serial launcher with 10+ prior dead launches all funded from the same CEX.

How is /dev different from /team? /dev focuses on one wallet — the creator — and its history. /team scans the full holder list for insider-pattern wallets (including but not limited to the dev). Use both together: /dev for context on the creator, /team for the full insider cluster.

Does /dev work on Raydium-native tokens? Yes, but the "success rate" metric is less sharp — there's no bonding curve threshold, so Noesis falls back to market-cap thresholds.

What counts as a "dead" prior launch? A token is considered dead when its bonding curve progress is below 10% and the price is flat or declining. It's a heuristic, not a hard rule; serial-dev patterns show up clearly at this threshold.

Can /dev tell me the dev's Twitter handle? Only if the dev wallet has a Solscan label that references a public identity. Noesis does not scrape or correlate off-chain data.

If the dev has only one prior launch, is that a red flag? No — single-launch devs are the majority of pump.fun. Absence of history is different from bad history.

Related guides

Noesis — on-chain intelligence. Home · API docs · MCP · llms.txt