> For the complete documentation index, see [llms.txt](https://docs.fetcch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fetcch.xyz/how-to-integrate/quickstart.md). # Quickstart Fetcch API contains various modules, each module has different API route and schema * Identity Module * Resolve any identity from any DID protocol like .eth, .sol, .apt, @metamask, @kana etc * Issue identity in a namespace like @metamask, @kana etc * Transaction Request Module * Request any type of transaction to any address, or DID * Websocket APIs for notifying when a request is created for an address or DID * Synchronized Address Book Module * Create books for any wallet * Share books to different wallet ### API Keys To acquire API Keys, contact @hardik\_fetcch on telegram, we will guide you through entire process and make sure you have a delight while building on Fetcch ### How to authenticate using API Keys? Add your API Key as `secret-key` in headers of every request, and request will be authenticated ### Reading Data All data is user owned and can only be accessed by the user itself by providing a signature. --- # 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.fetcch.xyz/how-to-integrate/quickstart.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.