> 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/overview.md). # Overview ADCP's implementation is deliberately narrow: Solidity contracts implementing the accounting/credit/reserve core, a Next.js frontend reading and writing against them, and a small, decoupled evidence-capture service. There is no framework-heavy backend — most state lives on-chain. ## Where things live * **Protocol contracts** — the accounting core, credit engine, collateral vault, oracle router, and compliance/eligibility adapter. See [Contract Interfaces](/developers/contract-interfaces.md). * **Frontend** — a static-exported Next.js application reading contract state via standard RPC calls and writing via a connected wallet. See [Frontend Integration](/developers/frontend-integration.md). * **Evidence service** — an optional, additive service for recording human-tester assertions against independently chain-verified transaction outcomes. Never a precondition for any protocol operation. See [Evidence API](/developers/evidence-api.md). ## What is and is not documented here This is a technical reference for understanding and verifying the current controlled pilot's actual behaviour — not an SDK, and not a guarantee of API stability across future deployments. Where a capability is planned but not yet built (for example, a formal OpenAPI specification for the evidence service), this documentation says so explicitly rather than describing an endpoint that does not exist. ## Source of truth Contract addresses, ABIs, and configuration are derived from the frontend's own canonical manifest files, not retyped by hand into documentation — see [Deployment Reference](/network/deployment-reference.md). --- # 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/overview.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.