> For the complete documentation index, see [llms.txt](https://docs.slinky.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slinky.network/slinkylayer/slinky-token.md). # SLINKY Token SLINKY is the access token for SlinkyLayer. Its primary utility is private-chat bandwidth. Users can begin with a complimentary allowance, then hold SLINKY to unlock continued access to private AI conversations. SLINKY can also unlock designated platform features and selected specialist tools. The token is not used to pay for external tool calls. Specialist tools are priced separately in USDC on Base and settled through x402. This page describes how SLINKY functions within the product. It is not an offer to sell or a solicitation to buy SLINKY. Please read [Legal Notices & Risk Factors](https://docs.slinky.network/slinkylayer/legal-notices-and-risk-factors) alongside this page. #### At a glance | SlinkyLayer service | Access requirement | Payment method | | --------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | Complimentary private chat | Available without holding SLINKY, subject to the allowance shown in the interface | No separate tool payment | | Additional private-chat bandwidth | Hold the amount of SLINKY shown in the interface | SLINKY is held, not spent. Unlocking bandwidth does not transfer, burn, lock, or reduce the user's SLINKY balance. | | Open specialist tools | Available to eligible users | Per-request USDC payment on Base through x402 | | Token-gated specialist tools | Meet the SLINKY holding requirement shown in the interface | Per-request USDC payment on Base through x402 | #### Private chat bandwidth Every user can start with a complimentary allowance for private AI conversations. This provides a way to use the chat before holding SLINKY. Once that allowance has been used, holding SLINKY unlocks additional private-chat bandwidth under the active bandwidth schedule. Private-chat bandwidth covers the services required to run the conversation, including model inference, context processing, response generation, and chat orchestration. It does not cover the price charged by an external tool or API. The current SLINKY holding requirements, available chat quotas, quota periods, reset conditions, and rate limits are published in the SlinkyLayer interface. The interface displays the rules that apply at the time the service is used. #### How bandwidth is measured Private-chat requests do not all require the same amount of computation. A short exchange will generally use less bandwidth than an extended conversation with a large context window or a more computationally intensive reasoning mode. Bandwidth usage may reflect: * the model selected for the conversation; * the length of the prompt and response; * the amount of conversation context being processed; * the reasoning mode requested; * infrastructure and network demand; and * rate-limit, security, and abuse controls. The interface shows the user's available quota and relevant usage information. Bandwidth represents access to the private-chat service and should not be understood as a guaranteed number of messages. #### Specialist tools and x402 SlinkyLayer can route a request from the private chat to a specialist tool for live-web search, research, market data, blockchain data, prediction markets, execution, or another supported capability. These tools operate separately from private-chat bandwidth. When a tool charges for a request, the interface identifies the selected tool and displays its USDC price. The user then authorizes the payment on Base through x402. This creates a clear separation between the two service layers: 1. **Private chat:** SLINKY unlocks bandwidth for the conversation, model response, context processing, and routing. 2. **Specialist tool:** USDC pays for the selected tool call through x402. An x402 payment purchases the identified tool service. It does not purchase SLINKY, reduce the user's SLINKY balance, or create any entitlement to a token distribution. Specialist tools are operated by third parties. SlinkyLayer routes requests to them and does not guarantee their availability, accuracy, pricing, or continued support. Certain tools may be unavailable in certain jurisdictions or to certain users. #### Token-gated tools and features Selected tools and platform features can be reserved for users who meet a stated SLINKY holding requirement. In these cases, SLINKY acts as the access credential. It determines whether the user can invoke the tool, but it does not pay the tool's usage price. After access is confirmed, the user still authorizes the applicable USDC payment through x402. Other tools may remain available to any eligible user who pays the displayed x402 price. The SlinkyLayer interface identifies token-gated tools, displays their current SLINKY requirements, and shows the available tool network. Because providers, pricing, coverage, and integrations can change, the interface is the authoritative source for current tool availability and access conditions. #### What holding SLINKY provides Under the active product rules displayed in the interface, holding SLINKY can provide: * additional private-chat bandwidth; * access to designated chat modes or service tiers; * eligibility to use selected specialist tools; * increased chat rate limits; and * access to other identified platform features. These are product-access benefits. They do not create a right to money or financial returns. #### Changes to access requirements SlinkyLayer sets holding requirements, quotas, quota periods, reset conditions, and rate limits, and can change them. These values are adjusted in response to model pricing, inference and infrastructure costs, service capacity, security and abuse conditions, and product design. They are not adjusted to manage the market price of SLINKY, to influence trading activity, or to produce a financial outcome for holders. SlinkyLayer does not commit to maintaining any particular ratio between SLINKY held and bandwidth received. The amount of bandwidth a given quantity of SLINKY unlocks can decrease as well as increase. Current values are always shown in the interface, which is the authoritative source at the time of use. #### What SLINKY does not provide SLINKY does not represent: * equity or ownership in SlinkyLayer or an affiliated entity; * debt, repayment rights, or a claim against company assets; * dividends, revenue sharing, profit sharing, interest, or passive yield; * a promise of liquidity, listing, market support, or price appreciation; * a guarantee that another person will purchase the token; or * a right to redeem SLINKY or bandwidth for a particular fiat value. SLINKY is not a bank account, deposit, stablecoin, stored-value account, or payment account. Private-chat bandwidth is not money, is not transferable, and cannot be redeemed for cash. #### Acquiring SLINKY SLINKY is intended to be acquired and held for access to SlinkyLayer services. It should not be acquired for investment purposes, in expectation of profit, or in expectation that SlinkyLayer or any other person will undertake efforts to increase its value. SlinkyLayer does not offer, sell, or distribute SLINKY through this documentation. Nothing on this page is an offer to sell, a solicitation of an offer to buy, or a recommendation regarding SLINKY or any other asset, and nothing here is investment, financial, legal, tax, or accounting advice. SLINKY may lose all of its value, and SlinkyLayer may modify, suspend, or discontinue any service at any time. See [Legal Notices & Risk Factors](https://docs.slinky.network/slinkylayer/legal-notices-and-risk-factors). #### Eligibility and restricted jurisdictions Access to SlinkyLayer is subject to the Terms of Service. Services are not available to: * persons located in, ordinarily resident in, or organised under the laws of a jurisdiction subject to comprehensive sanctions administered by OFAC or an equivalent authority; * persons appearing on any applicable sanctions or restricted-party list; or * persons in any jurisdiction where use of the services would breach local law. Users are responsible for determining whether their use of SlinkyLayer, and any holding of SLINKY, is lawful in their jurisdiction.