> 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/introduction/what-is-adcp.md). # What Is ADCP ADCP (Autonomous Digital Capital Protocol) is verifiable capital infrastructure for digital credit and real-world-asset (RWA) financial products. ## The business model ADCP is built first as B2B infrastructure for established financial businesses, not as a full asset-management company. The financial partner keeps: * the client relationship * brand * licence / regulated role * product strategy and distribution * suitability / servicing where applicable * custody / bank / VASP relationships * its own product economics ADCP provides: * capital-control rules * credit infrastructure and collateral logic * reserve logic and risk constraints * accounting and reconciliation * observable evidence * product configuration and position infrastructure The commercial question a prospective partner should ask is simple: **would this capability be more valuable to buy than to build?** ## What ADCP is not * Not another generic BTC lending app, and not a retail crypto product. * Not a tokenisation company that must issue every asset itself. * Not a claim that software eliminates licensing, auditors, or law. * Not a yield-manufacturing mechanism. ## One engine, multiple products ADCP's architecture is one deterministic capital-accounting core supporting multiple, clearly distinguished products. See [Products Overview](/products/overview.md) for the current product taxonomy and status. ## Current status The protocol's credit and accounting core is implemented and running in a **controlled pilot** on Base Sepolia — see [Controlled Pilot](/introduction/controlled-pilot.md) for exactly what that means and does not mean. --- # 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/introduction/what-is-adcp.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.