> 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/evidence-api.md). # Evidence API > **Status: not yet deployed for the current pilot's own domain. No OpenAPI specification exists yet.** This page describes the concept and its design principles, not a committed, stable public API surface. Treat any endpoint shape mentioned here as illustrative of the existing codebase's design, not as a guaranteed contract. ## Purpose The evidence service is a small, deliberately **decoupled** service for recording human-tester assertions — a PASS/FAIL/SKIP judgment against a named scenario — and, where a transaction is involved, independently re-deriving that transaction's real on-chain outcome via RPC rather than trusting a frontend-reported result alone. ## Decoupling principle Nothing in the evidence service executes, signs, or blocks a protocol operation. If this service is unavailable, wallet and contract interactions are completely unaffected — only the evidence trail for that interaction is missing until the service is available again. Recording evidence is best-effort and additive, never a precondition for using the protocol. ## Current status An evidence-capture service exists in the codebase and has been used for earlier controlled-testing rounds, each with its own dedicated deployment and origin restriction (a service instance is configured to accept requests only from one specific frontend origin, never a wildcard). A fresh instance scoped to the current `adcpcapital.com` deployment has not yet been deployed. Until it is, the application's own evidence-recording UI (where present) shows a local-only tally with an explicit notice, rather than silently doing nothing or falling back to a different deployment's evidence service. ## What will be documented once it exists Once a dedicated instance for the current domain is live, this page will be updated with its actual, stable endpoint reference — session lifecycle, step recording, and read-only report endpoints — rather than the current placeholder-free description above. --- # 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/evidence-api.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.