> For the complete documentation index, see [llms.txt](https://docs.j.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.j.tools/getting-started/quick-start.md).

# Quick start

This walkthrough takes you from a connected wallet to a live SPL token in about five minutes. Do the steps in order.

{% hint style="info" %}
**Before you start:** your wallet is on Solana mainnet (J Tools has no testnet, so every action is real and on-chain), and it holds a little SOL for the platform fee and the network cost. The app shows the fee before you sign. More in [Fees and the SOL you need](/getting-started/fees-explained.md).
{% endhint %}

## Connect your wallet

{% stepper %}
{% step %}

#### Connect your wallet

Click **Connect wallet** in the top bar and choose your wallet: Phantom, Solflare, Backpack, or any wallet that supports the Solana Wallet Standard.
{% endstep %}

{% step %}

#### Approve the connection

Your wallet asks you to approve. This only shares your public address. It does not give J Tools access to your funds, and it never exposes your private key.
{% endstep %}
{% endstepper %}

## Create your first token

{% stepper %}
{% step %}

### Open Token Creator

Go to [Token Creator](/tools/launch/token-creator.md), the simplest way to mint a standard SPL token.
{% endstep %}

{% step %}

### Fill in the basics

**Name and symbol.** A name (for example `My Token`) and a short ticker (for example `MYT`).

**Supply and decimals.** How many tokens to mint and their decimal places. Nine decimals is the common Solana default.

**Image and details.** A logo and a short description. This is what wallets and explorers show next to your token.
{% endstep %}

{% step %}

### Review the fee and sign

The app shows the platform fee and the network cost before anything happens. When you are ready, sign the transaction in your wallet.

{% hint style="warning" %}
**About fees.** Every action has two costs: the Solana **network fee** paid to validators, and the **J Tools platform fee**. The platform fee always shows in the app before you confirm, and nothing is charged until you sign. Fees can change over time, so trust the in-app summary rather than a number you saw once.
{% endhint %}

A caution banner here is expected on the multi-step token tools. [Phantom warnings explained](/help-and-security/phantom-warnings.md) shows how to tell a normal banner from a real red flag.

{% hint style="info" %}
**About wallet warnings.** Some tools sign more than one thing in a single step, for example creating a token and its metadata together. Phantom can show a caution banner for these multi-step transactions. The banner is expected here and does not mean something is wrong. Read what you are signing, then approve.
{% endhint %}
{% endstep %}

{% step %}

### You have a token

Once the transaction confirms, your token is live on-chain. Copy the mint address from the success screen. You will use it everywhere else on J Tools.
{% endstep %}
{% endstepper %}

## What next?

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Make it trustworthy</strong></td><td>Revoke authorities so holders can trust your token.</td><td><a href="/pages/gbx1RbByQOVKZzt0PQkP">/pages/gbx1RbByQOVKZzt0PQkP</a></td></tr><tr><td><strong>Add liquidity</strong></td><td>Open a pool so people can trade it.</td><td><a href="/pages/QT0nYfDbGpJo4Cm5Tbs6">/pages/QT0nYfDbGpJo4Cm5Tbs6</a></td></tr><tr><td><strong>Reach holders</strong></td><td>Airdrop tokens to a list of wallets.</td><td><a href="/pages/ABVX2mBQDoCv7DEdVmKp">/pages/ABVX2mBQDoCv7DEdVmKp</a></td></tr></tbody></table>

## Something went wrong?

If a step stalled, a transaction failed, or the result is not what you expected: when you see a short message or a code like `AFF_WITHDRAW_MIN`, the [Error codes reference](/reference/error-codes.md) tells you what it means and how to clear it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.j.tools/getting-started/quick-start.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.