> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/upcoming-changes.md).

# Upcoming Changes

This section documents API and platform capabilities that are planned or in active development but not yet available in production. Items are published here early so your team can plan ahead and avoid conflicts with what is coming.

> **Nothing listed here should be treated as a production dependency until it appears in the main documentation and Changelog.**

### What's Coming

Nothing is currently listed as in development in this section.

### Superseded

| Page                                          | What happened                                                                                                                                                                                                                                                                                                          |
| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Consumer Fee Control and Exact Net Settlement | The design described on that page was replaced during development and was never implemented. The requirement it addressed, a merchant receiving an exact settlement amount while fees are recovered elsewhere, is met by the Split Funding Program, which is available today and documented in the main documentation. |

> **Bead does not have a consumer fee program.** Nothing in this section should be read as one being in development. Bead has no fee field, no rate configuration, no calculation and no consumer-facing disclosure. Bead can process a fee an integrator has already calculated and folded into the amount they send. See Consumer Fee Passthrough for Wallet and Crypto Tenders.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.bead.xyz/upcoming-changes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.