> 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/tools/boost/maker-bot.md).

# Maker Bot

[Maker Bot](https://j.tools/en/tools/maker-bot) is being built to place maker-style orders that add passive market activity around your token on Solana. It is not live yet. This page explains what the tool is meant to do and what to use in the meantime.

{% hint style="info" %}
**Coming soon.** Maker Bot is not live yet. The tool opens to a "coming soon" screen with no inputs. Watch the Changelog for the launch.
{% endhint %}

## What it will do

The plan is to let a token project run maker-style orders that support market activity, the passive side of market making. The idea is steady, low-key order flow around your token rather than aggressive buys. If the term is new to you, the [Glossary](/getting-started/glossary.md) covers maker orders and market making, and [DEXes and liquidity](/concepts/dexes-and-liquidity.md) explains where this order flow would land on-chain.

The exact mechanics are still in design. The marketing copy mentions things like spread controls, cycle settings, and validation checkpoints, but none of that is built yet. Treat those as direction, not a feature list. Nothing here is a promise of behavior, returns, or supported venues until the tool actually ships.

[**See Maker Bot in the app →**](https://j.tools/en/tools/maker-bot)

## Current status

* The tool shows a coming-soon screen only. There is no form, no DEX picker, and no transaction step.
* No order is placed and no market making happens yet. The tool has not launched.
* No fee is charged, because there is nothing to run yet. When the tool launches, the in-app fee summary and the [Fee schedule](/reference/fee-schedule.md) will be the source of truth.

{% hint style="warning" %}
The planned tool is flagged as **high risk** in our internal config, which is how we tag features that do automated, repeated on-chain activity. When Maker Bot does launch, read the in-app warnings and the fee summary closely before you run anything.
{% endhint %}

## What to use meanwhile

If you want to add real market activity around your token today, these tools are live:

{% content-ref url="/pages/SyDtWrNajVH0Y5kGtFI1" %}
[Volume Bot](/tools/boost/volume-bot.md)
{% endcontent-ref %}

{% content-ref url="/pages/ybeUy9qGvgKXJiara9XV" %}
[Pump Volume](/tools/boost/pump-volume.md)
{% endcontent-ref %}

If your goal is to widen the holder count rather than trade volume, look at Holder Booster:

{% content-ref url="/pages/o5eO6abVdoCCB4WkfKVR" %}
[Holder Booster](/tools/boost/holder-booster.md)
{% endcontent-ref %}

## FAQ

<details>

<summary>How is Maker Bot different from a volume bot?</summary>

A volume bot drives trade count and turnover. Maker Bot is planned for the passive, maker side: resting order flow rather than aggressive market buys. Until it ships, [Volume Bot](/tools/boost/volume-bot.md) and [Pump Volume](/tools/boost/pump-volume.md) cover the volume side. See [DEXes and liquidity](/concepts/dexes-and-liquidity.md) for how each kind of activity reaches the book.

</details>

<details>

<summary>Can I use Maker Bot right now?</summary>

No. It opens to a coming-soon screen. There is no way to place an order or run market making with it yet.

</details>

<details>

<summary>Will it charge a fee?</summary>

Not today, because nothing runs. When the tool launches, the platform fee will appear in the app before you confirm, and it will match the [Fee schedule](/reference/fee-schedule.md).

</details>

<details>

<summary>When does it launch?</summary>

No date yet. Watch the Changelog and this page for the update.

</details>

<details>

<summary>Does J Tools hold my funds or keys for this?</summary>

No, and that will not change when the tool ships. J Tools is non-custodial. You sign everything in your own wallet, and we never hold or request your keys.

</details>

## If something goes wrong

There is nothing to run yet, so there are no errors to hit on this page. Once the tool launches, common issues and their meanings will live in the [Error codes reference](/reference/error-codes.md).

## Related tools

{% content-ref url="/pages/SyDtWrNajVH0Y5kGtFI1" %}
[Volume Bot](/tools/boost/volume-bot.md)
{% endcontent-ref %}

{% content-ref url="/pages/ybeUy9qGvgKXJiara9XV" %}
[Pump Volume](/tools/boost/pump-volume.md)
{% endcontent-ref %}

{% content-ref url="/pages/o5eO6abVdoCCB4WkfKVR" %}
[Holder Booster](/tools/boost/holder-booster.md)
{% endcontent-ref %}

{% content-ref url="/pages/sAoyZDh9f2RlcKOAuq5G" %}
[Multi Swap](/tools/trade/multi-swap.md)
{% endcontent-ref %}

{% hint style="success" %}
**J Tools is non-custodial.** We never hold your private keys and never ask for them. Every transaction is built in your browser and signed by your own wallet. If any page ever asks you to paste a private key, stop, close it, and let us know.
{% endhint %}


---

# 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/tools/boost/maker-bot.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.
