> For the complete documentation index, see [llms.txt](https://docs.kubchain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kubchain.com/quickstart/launching-a-token-on-kub/kap-token-interfaces.md). # KAP Token Interfaces Smart contract token interfaces define the external surface of a token contract. They tell wallets, dApps, explorers, and other contracts which functions and events they can rely on. An interface does not describe internal storage or implementation details. It defines the public contract between your token and every integration around it. On KUB, token interfaces are commonly defined through [KUB Application Protocol (KAP)](/build-on-kub/kub-application-protocol-kap.md) standards. KAP extends familiar ERC patterns with KUB-specific roles, KYC-aware transfer flows, and admin-controlled recovery functions where required. ## What Token Interface Includes A token interface usually defines: * Read functions such as `balanceOf`, `name`, and `symbol` * Write functions such as `transfer`, `approve`, and `transferFrom` * Events such as `Transfer` and `Approval` * Expected behavior for approvals, transfers, and ownership ## Why It Matters Interfaces make integrations predictable. They let wallets display balances and metadata. They let dApps request approvals and submit transfers. They let developers verify whether a token supports the behavior they need before integrating it. On KUB, interfaces also help clarify KUB-specific token behavior. KAP standards add functions such as `adminTransfer`, `internalTransfer`, and `externalTransfer`. These functions are not part of standard ERC token interfaces. ## KAP Token Interfaces Use these KAP interface pages when you need the exact function and event definitions for a token standard on KUB: * [KAP-20](/quickstart/launching-a-token-on-kub/kap-token-interfaces/kap-20.md) - Fungible token interface for KUB with KYC-aware transfer flows and `adminTransfer` * [KAP-721](/quickstart/launching-a-token-on-kub/kap-token-interfaces/kap-721.md) - Non-fungible token interface for unique assets on KUB * [KAP-1155](/quickstart/launching-a-token-on-kub/kap-token-interfaces/kap-1155.md) - Multi-token interface for fungible and non-fungible assets in one contract * [KAP-22](/quickstart/launching-a-token-on-kub/kap-token-interfaces/kap-22.md) - Loyalty points token interface built on KAP-20 with periods and token expiration ## How To Use the Interface Pages Use the interface page when you need to: * Check supported functions and events * Review token behavior before integration * Compare standards before choosing one Choose the token standard that matches your use case, then review its interface in detail before you deploy or integrate it. --- # 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.kubchain.com/quickstart/launching-a-token-on-kub/kap-token-interfaces.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.