> For the complete documentation index, see [llms.txt](https://docs.charterfnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.charterfnd.com/readme.md).

# A Clearer Way to Launch a Token

Launching a token is hard. Traditionally, it means forming and staffing three separate entities from scratch: a lab company, an offshore foundation (typically in the Cayman Islands), and a British Virgin Islands company to mint the token.&#x20;

The costs of this structure are significant: months of duplicated legal work and tens of thousands of dollars up front, long before the project is ready to ship. This happens at a time when capital is tight, and every hour (and dollar) should be put towards building.

Charter replaces the traditional token launch process by providing shared infrastructure. The Charter Foundation forms and initially governs the launch entities in collaboration with the builder, sees the project through the token launch, and finally converts the top-level company into an independent long term governance organization. Said entity then leaves the dock under its own command.

The result is a faster, more disciplined, and structurally de-risked path to token launch. This path is further optimized with built-in access to [ecosystem partners](/miscellaneous/the-charter-ecosystem.md), liquidity infrastructure, and an accelerated application pathway for listing on Kraken.

### Jump right in

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-bolt">:bolt:</i></h4></td><td><a href="/pages/pm64t3ptzBV87DF8BWsZ"><strong>Quickstart</strong></a></td><td>Learn more about how Charter helps with token launches.</td><td></td><td></td><td><a href="/pages/7FvWQMF0kTK7HGhlQfmo">/pages/7FvWQMF0kTK7HGhlQfmo</a></td></tr><tr><td><h4><i class="fa-stairs">:stairs:</i></h4></td><td><a href="/pages/ASBRi0GPoHV544wLrJ1J"><strong>Charter Process</strong></a></td><td>Understand the process from planning to launch to independence.</td><td></td><td></td><td><a href="/pages/QPzbTvC6XsT5gERiU43E">/pages/QPzbTvC6XsT5gERiU43E</a></td></tr><tr><td><h4><i class="fa-book">:book:</i></h4></td><td><a href="/pages/HpqESZf1utMIeFr609ig"><strong>Technical Documentation</strong></a></td><td>Detailed breakdown for builders and lawyers diving deep.</td><td></td><td></td><td><a href="https://github.com/GitbookIO/gitbook-templates/blob/main/product-docs/broken-reference/README.md">https://github.com/GitbookIO/gitbook-templates/blob/main/product-docs/broken-reference/README.md</a></td></tr></tbody></table>


---

# 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.charterfnd.com/readme.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.
