> For the complete documentation index, see [llms.txt](https://kkone.gitbook.io/kkone-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kkone.gitbook.io/kkone-docs/reference/fees-and-risk.md).

# Fees and risk

## Narrative analysis during beta

Default-model narrative analysis is currently free during beta. Any pricing change will be disclosed before it takes effect.

## Onchain fees

You may still pay network, deployment, protocol, trading, or other onchain costs. Fees vary by network conditions and the action being performed.

* Base offers the fee modes shown in the product, including the recommended Default + 10% option.
* Robinhood Chain uses Automatic fee handling in V2.
* A fee estimate is not a guaranteed final fee.
* A displayed launch-capacity estimate does not reserve or promise that many successful launches.
* Solana fees are not applicable to V2 because Solana actions are not enabled.

## Included Base launches

If KK.one displays included Base launches for your account, they apply only to eligible Base deployments and follow the current entitlement shown in the product. They cannot fund a Robinhood Chain deployment and should not be treated as a permanently fixed allowance.

## Creator allocation

Current Base and Robinhood Chain launches allocate 2% of total token supply to the creator at launch, with no lockup or vesting under the current rule. This is separate from Creator Rewards and from any network- or protocol-specific fee.

## Creator rewards

Reward assets, estimates, fees, and claim execution are network-specific. KK.one does not promise that a token will generate rewards, that displayed rewards will remain available, or that the reward will exceed the cost of claiming.

## Key risks

Using KK.one and interacting with onchain tokens involves substantial risk, including:

* total loss of token value;
* no or low liquidity;
* high slippage and price impact;
* front-running, MEV, and public-mempool exposure;
* smart-contract or protocol vulnerabilities;
* network congestion, reorganization, outage, or delayed confirmation;
* wallet compromise, phishing, incorrect approvals, or lost account access;
* incorrect network, address, token, or amount;
* AI-generated errors, duplicated concepts, or misleading metadata;
* market-data, RPC, indexer, explorer, wallet, or third-party failure;
* Auto Sell trigger or execution failure;
* legal, regulatory, tax, sanctions, and intellectual-property risk.

Blockchain transactions are usually irreversible. KK.one cannot recover assets sent to an incorrect address or unsupported network.

## No advice or endorsement

KK.one does not provide investment, legal, or tax advice and does not act as a fiduciary. Rankings, narrative detection, creator allocation, rewards, and automated rules are not recommendations or guarantees.

An X source post does not mean its author created, approved, sponsored, or endorses the related token.


---

# 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://kkone.gitbook.io/kkone-docs/reference/fees-and-risk.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.