> For the complete documentation index, see [llms.txt](https://bluprynt.gitbook.io/bluprynt-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluprynt.gitbook.io/bluprynt-docs/kyi-know-your-issuer/integration-options.md). # Integration Options KYI attestations are designed to be easily integrated by platforms that need to verify token legitimacy and issuer identity. We’re actively partnering with: * **Block explorers**: to visually display which tokens are KYI-verified\\ * **Token listing services**: to prevent copycat or fraudulent submissions\\ * **Wallets and dApps**: to warn users or restrict interaction with unauthenticated tokens Attestations can be queried via API or linked to token metadata, and are compatible with EVM, Solana, and ACE-enabled environments. *** ## Partner With Us If you operate a block explorer, listing platform, or wallet and are interested in surfacing KYI verifications for your users, reach out to our integrations team: 📩 **** Together, we can make Web3 safer and more accountable at the infrastructure level. --- # 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://bluprynt.gitbook.io/bluprynt-docs/kyi-know-your-issuer/integration-options.md?ask=&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.