> For the complete documentation index, see [llms.txt](https://docs.adcpcapital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adcpcapital.com/developers/frontend-integration.md). # Frontend Integration The ADCP frontend at [adcpcapital.com](https://adcpcapital.com) is a statically-exported Next.js application. Every protocol read and write happens client-side, through a connected wallet and standard RPC calls — there is no proprietary backend API standing between the frontend and the contracts themselves. ## Wallet connectivity Wallet connection uses the WalletConnect/Reown protocol. A visitor can read every public page — the commercial/product pages, and the protocol/evidence views — without connecting a wallet at all. A wallet is required only to originate, repay, or otherwise write a transaction. ## Network expectations The application expects to be connected to the network its active configuration specifies (currently Base Sepolia, chain ID `84532` — see [Base Sepolia](/network/base-sepolia.md)). If a connected wallet is on a different network, the application shows an explicit "wrong network" state and offers a network-switch action — it never silently reads or writes against the wrong chain. ## Building your own integration Because every write is a standard wallet-signed transaction against a standard EVM contract, an independent integration does not require using the ADCP frontend at all — it requires only the contract addresses and ABI referenced in [Deployment Reference](/network/deployment-reference.md) and [Contract Interfaces](/developers/contract-interfaces.md), plus ordinary wallet/RPC tooling. ## What is not yet published A formal SDK or client library is not published at this time. This page will be extended if and when one exists, rather than describing a package that does not exist yet. --- # 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://docs.adcpcapital.com/developers/frontend-integration.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.