One API. Your next token.

From details to launch

The same four steps apply to both chains. Only the transaction you sign changes.

1. 01

   Add your metadata

   Upload the token details and image.

2. 02

   Prepare a launch

   Choose a target, a verified wallet, and an optional creator buy.

3. 03

   Sign and submit

   Sign the prepared transaction locally with your selected wallet.

4. 04

   Follow confirmation

   Retrieve the launch status and confirmed token address.

Authentication

An API credential gives your application access to an Entropy account and the verified wallets you authorize. The selected wallet signs the transaction and pays the launch costs.

Authorization: Bearer <YOUR_API_KEY>

Keep your key on your server or in your local environment. A credential can be limited to specific wallets and permissions, expire, or be revoked. Your wallet's private key stays with you.

Before launching, verify ownership of the wallet, authorize it for the credential, and accept the current Entropy Terms.

Token metadata

Start with your token's name, symbol, and image. Add a description and website if you want to tell people more about it.

{
  "name": "Example Coin",
  "symbol": "EXAMPLE",
  "description": "An example token.",
  "image": "./example.png",
  "website": "https://example.com"
}

Upload the image with your details to receive a metadataId. The image path above refers to a local file; it is not a hosted image URL. Reference the returned ID when preparing a launch. To change the token details, upload new metadata and use the new ID.

Create a launch

Choose the launch target and a verified wallet from your account. Use a Solana wallet for Pump.fun or an EVM wallet for Robinhood Chain.

{
  "targetId": "pump-solana-mainnet",
  "walletId": "wal_solana_123",
  "metadataId": "meta_123",
  "options": {
    "creatorBuySol": "0",
    "mayhemMode": false,
    "cashback": false
  }
}

{
  "targetId": "robinhood-mainnet",
  "walletId": "wal_evm_456",
  "metadataId": "meta_123",
  "options": {
    "creatorBuyEth": "0"
  }
}

Creator-buy amounts are decimal strings in SOL or ETH. Use "0" to launch without an initial purchase.

The response includes a launchId, the resolved launch and fee configuration, and a transaction preparation. Review the fee basis, recipients, and shares before signing.

Sign & submit

Sign the returned transaction with the wallet selected for the launch. An API key authorizes the request; your wallet signature authorizes the transaction.

Solana

A base64-encoded versioned transaction. Add your wallet signature and preserve the signatures already included. Sign within the returned blockhash validity window.

EVM

Transaction fields including the chain, destination, data, value, nonce, and gas parameters. Sign locally and return the hex-encoded signed transaction.

Submit the preparationId and signed transaction for that launch. The signer and transaction contents must match the preparation. Keep the returned transaction identifier to follow confirmation.

Launch status

Retrieve the same launch to follow its progress from preparation to confirmation.

preparing

Your launch transaction is being prepared.

awaiting_signature

The transaction is ready for your wallet to sign.

submitted

The transaction has been submitted to the network.

confirmed

The launch is confirmed. The result contains the token address and transaction identifier.

failed

Read the error code, message, and retryable field before trying again.

Retries & recovery

Give each launch a unique request key

Include an Idempotency-Key when creating a launch. Repeating the same request with the same key returns the existing launch. Reusing that key with different details returns a conflict.

Idempotency-Key: example-coin-launch-001

Check the launch before submitting again

A timeout does not mean a transaction failed. Retrieve the existing launch and check its transaction status before preparing a replacement. Keep the launch ID and preparation ID together throughout the flow.

Respect transaction validity

A Solana transaction can expire with its blockhash. On EVM, an API preparation expiry does not cancel a signed transaction on the network. Check the nonce and any contract deadline before replacing it.