> For the complete documentation index, see [llms.txt](https://whitepaper.surge.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.surge.xyz/usdsurge-token/usdsurge.md). # $SURGE The **$SURGE token** is the foundational asset of the Surge ecosystem, representing ownership, governance, and growth alignment across its products and participants. It ensures fair distribution of value among community members, contributors, and stakeholders who build and interact with the Internet Capital Markets infrastructure. \ The token’s design emphasizes long-term sustainability and transparent economics, with clear allocations to liquidity, ecosystem incentives, team rewards, and treasury management. \ Through structured vesting and multi-chain liquidity provisioning, $SURGE maintains both accessibility and stability while incentivizing continuous ecosystem expansion. Its tokenomics are engineered to promote balanced participation, reward early involvement, and sustain development momentum without over-concentration of supply. --- # 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://whitepaper.surge.xyz/usdsurge-token/usdsurge.md?ask=&goal= ``` `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.