> For the complete documentation index, see [llms.txt](https://documents.pix.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documents.pix.fun/why-pixfun-skips-bonding-curves.md).

# Why PixFun Skips Bonding Curves?

At PixFun, we’ve made a deliberate decision to move away from bonding curves.

While bonding curves were originally introduced to bring structure and automated pricing to token launches, in practice, we believe they create more problems than they solve. ***They're often easily exploited by bots and early snipers who front-run the curve***, extracting value before real users even have a chance to participate.

**For creators, the experience can be equally frustrating,** as many will have their token not bound.

PixFun was built to simplify the process. No curves, no headaches. Just instant, fair deployment designed for real users and real momentum.


---

# 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://documents.pix.fun/why-pixfun-skips-bonding-curves.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.