Loading
Metaplex development on Solana — NFTs, tokens, compressed NFTs, candy machines, token launches, autonomous agents. Use when working with Token Metadata, Core, Bubblegum, Candy Machine, Genesis, Agent
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add internet-court/internet-court-skill --skill metaplex -a cursor -y
Metaplex development on Solana — NFTs, tokens, compressed NFTs, candy machines, token launches, autonomous agents. Use when working with Token Metadata, Core, Bubblegum, Candy Machine, Genesis, Agent Registry, or the mplx CLI.
Metaplex development on Solana — NFTs, tokens, compressed NFTs, candy machines, token launches, autonomous agents. Use when working with Token Metadata, Core, Bubblegum, Candy Machine, Genesis, Agent Registry, or the mplx CLI.
Metaplex provides the standard infrastructure for NFTs and tokens on Solana:
Prefer CLI over SDK for direct execution. Use SDK only when user specifically needs code.
| Approach | When to Use |
|---|---|
CLI (mplx) | Default choice - direct execution, no code needed |
| Umi SDK | User needs code — default SDK choice. Covers all programs (TM, Core, Bubblegum, Genesis) |
| Kit SDK | User specifically uses @solana/kit, or asks for minimal dependencies. Token Metadata only — no Core/Bubblegum/Genesis support |
IMPORTANT: You MUST read the detail file for your task BEFORE executing any command or writing any code. The command syntax, required flags, setup steps, and batching rules are ONLY in the detail files. Do NOT guess commands from memory.
| Task Type | Read This File |
|---|---|
| Any CLI operation (agent guidelines, batching, explorer links) | ./references/cli.md |
| CLI: Agent Registry (identity, delegation, revocation, token linking) | ./references/cli.md + ./references/cli-agent.md |
| CLI: Core NFTs/Collections | ./references/cli.md + ./references/cli-core.md + ./references/metadata-json.md |
| CLI: Token Metadata NFTs | ./references/cli.md + ./references/cli-token-metadata.md + ./references/metadata-json.md |
| CLI: Compressed NFTs (Bubblegum) | ./references/cli.md + ./references/cli-bubblegum.md + ./references/metadata-json.md |
| CLI: Candy Machine (NFT drops) | ./references/cli.md + ./references/cli-candy-machine.md + ./references/metadata-json.md |
| CLI: Token launch / bonding curve (Genesis) | ./references/cli.md + ./references/cli-genesis.md |
| CLI: Execute / asset-signer wallets / agent vault | ./references/cli.md + ./references/cli-core.md (execute section) |
| SDK: Execute / asset-signer PDA / agent vault | ./references/sdk-umi.md + ./references/sdk-core.md (execute section) |
| CLI: Fungible tokens | ./references/cli.md + ./references/cli-toolbox.md |
| SDK setup (Umi) | ./references/sdk-umi.md |
| SDK: Core NFTs | ./references/sdk-umi.md + ./references/sdk-core.md + ./references/metadata-json.md |
| SDK: Token Metadata | ./references/sdk-umi.md + ./references/sdk-token-metadata.md + ./references/metadata-json.md |
| SDK: Compressed NFTs (Bubblegum) | ./references/sdk-umi.md + ./references/sdk-bubblegum.md + ./references/metadata-json.md |
| SDK: Token Metadata with Kit | ./references/sdk-token-metadata-kit.md + ./references/metadata-json.md |
| SDK: Agent Registry (identity, wallets, delegation) | ./references/sdk-umi.md + ./references/sdk-agent.md |
| SDK: Token launch + bonding curve swaps (Genesis) | ./references/sdk-umi.md + ./references/sdk-genesis.md |
| SDK: Low-level Genesis (custom buckets, presale, vesting) | ./references/sdk-umi.md + ./references/sdk-genesis-low-level.md |
| Off-chain metadata JSON format/schema (NFT or token) | ./references/metadata-json.md |
| Account structures, PDAs, concepts | ./references/concepts.md |
| CLI errors, localnet issues | ./references/cli-troubleshooting.md |
The mplx CLI can handle most Metaplex operations directly. Read ./references/cli.md for agent guidelines (batching, JSON output, explorer links), then the program-specific file.
CLI v0.1.0 breaking changes (for agents/scripts migrating from older versions):
--json <file>(used to pass an offchain metadata file path) is now--offchain <file>.--jsonis now the standard OCLIF flag for machine-readable output.- All commands now return structured JSON when
--jsonis passed — use this for programmatic/agent use.
| Task | CLI Support |
|---|---|
| Register agent identity | ✅ |
| Fetch agent data | ✅ |
| Revoke execution delegation | ✅ |
| Set agent token (Genesis link) | ✅ (requires asset-signer mode) |
| Create fungible token | ✅ |
| Create Core NFT/Collection | ✅ |
| Create TM NFT/pNFT | ✅ |
| Transfer TM NFTs | ✅ |
| Transfer fungible tokens | ✅ |
| Transfer Core NFTs | ✅ |
| Upload to Irys | ✅ |
| Candy Machine drop | ✅ (setup/config/insert — minting requires SDK) |
| Compressed NFTs (cNFTs) | ✅ (batch limit ~100, use SDK for larger) |
| Execute (asset-signer wallets) | ✅ |
| Check SOL balance / Airdrop | ✅ |
| Query assets by owner/collection | ❌ SDK only (DAS API) |
| Token launch (Genesis) | ✅ |
| Bonding curve swap (Genesis) | ✅ |
Agent Identity: 1DREGFgysWYxLnRnKQnwrxnJQeSMk2HmGaC6whw2B2p
Agent Tools: TLREGni9ZEyGC3vnPZtqUh95xQ8oPqJSvNjvB7FGK8S
Genesis: GNS1S5J5AspKXgpjz6SvKL66kPaKWAhaGRhCqPRxii2B
Core: CoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d
Token Metadata: metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s
Bubblegum V1: BGUMAp9SX3uS4efGcFjPjkAQZ4cUNZhtHaMq64nrGf9D
Bubblegum V2: BGUMAp9Gq7iTEuizy4pqaxsTyUCBK68MDfK752saRPUY
Core Candy: CMACYFENjoBMHzapRXyo1JZkVS6EtaDDzkjMrmQLvr4J
Use Agent Registry to register on-chain identity and execution delegation for MPL Core assets. The Mint Agent API (mintAndSubmitAgent) is the recommended path — it creates the Core asset and registers identity in a single transaction. For existing assets, use registerIdentityV1 directly. Any Core asset already has a built-in wallet (Asset Signer PDA) via Core's Execute hook — the registry adds discoverable identity records and lets owners delegate an off-chain executive to operate the agent. Agents can optionally link a Genesis token via setAgentTokenV1. Read ./references/cli-agent.md (CLI) or ./references/sdk-umi.md + ./references/sdk-agent.md (SDK).
Use Genesis. The Launch API (genesis launch create / createAndRegisterLaunch) is recommended — it handles everything in one step. Two launch types:
launchpool (default): Configurable allocations, 48h deposit, team vesting supportbonding-curve: Instant bonding curve (constant product AMM) — no deposit window, trading starts immediately, auto-graduates to Raydium CPMM on sell-out. Supports creator fees, first buy, and agent mode.Read ./references/cli.md + ./references/cli-genesis.md (CLI) or ./references/sdk-genesis.md (SDK launch flow). For custom buckets/presale/vesting, use ./references/sdk-genesis-low-level.md.
| Choose | When |
|---|---|
| Core | New NFT projects, lower cost (87% cheaper), plugins, royalty enforcement |
| Token Metadata | Existing TM collections, need editions, pNFTs for legacy compatibility |
Use Bubblegum when minting thousands+ of NFTs at minimal cost. See ./references/cli-bubblegum.md (CLI) or ./references/sdk-bubblegum.md (SDK).
Always use Token Metadata. Read ./references/cli-toolbox.md for CLI commands.
Use Core Candy Machine. Read ./references/cli.md + ./references/cli-candy-machine.md.
Creating an asset into a Core collection requires the collection's update authority (or an UpdateDelegate) to sign — a user's wallet can't, and the authority key must never be in a frontend. The app needs either a custom on-chain program (PDA granted UpdateDelegate, mint logic in the program) or a backend/API holding a delegate keypair that signs mints. Read the "Minting into a Collection from an App" section in ./references/sdk-core.md before designing the minting flow.
Use Core Execute when an asset (NFT, agent, vault) needs to hold SOL/tokens, transfer funds, sign transactions, or own other assets. Every Core asset has a signer PDA that can act as an autonomous wallet. Read ./references/cli-core.md (CLI) or ./references/sdk-core.md (SDK), execute section.
When a task needs deeper detail than the skill references provide (edge cases, full API surfaces, guides), consult the Metaplex docs: