> For the complete documentation index, see [llms.txt](https://rawctx.gitbook.io/rawctx-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rawctx.gitbook.io/rawctx-docs/api-reference/rawctx-http-api/answer-evidence.md).

# Answer evidence

All paths below are relative to the authenticated workspace API host.

## Core records

```
POST /api/answer-audit-logs
GET  /api/answer-audit-logs
GET  /api/answer-audit-logs/{id}
POST /api/answer-audit-logs/{id}/events
GET  /api/answer-audit-logs/export?format=jsonl|csv
GET  /api/answer-audit-logs/{id}/ledger/verify
```

An application JWT needs `answer_audit:create` to create a record and `answer_audit:read` to read records for its bound application. Event append and export are tenant-manager operations. The current export response has no pagination and is capped at 200 rows.

## Text-only keyed commitment request

```http
POST /api/answer-audit-logs
Authorization: Bearer <application-or-user-token>
Content-Type: application/json

{
  "application_key": "support_assistant",
  "environment": "production",
  "idempotency_key": "support:req_123:msg_456",
  "question": {"text": "What is the refund policy?"},
  "answer": {"text": "Refunds are available within 30 days."},
  "source_refs": []
}
```

When tenant keyed hashing is required, omit caller hashes so the service can derive commitments with the active tenant key. Whether raw text is stored is controlled separately by tenant settings.

## Lifecycle events

Accepted event types are `correction_appended`, `voided`, `redacted`, and `retention_extended`. Status values are `recorded`, `corrected`, `voided`, and `redacted`. A retention event records history but does not itself mutate `retention_until`.

## Evidence resources

```
POST /api/evidence-assets
GET  /api/evidence-assets
POST /api/evidence-assets/{id}/retrieve
POST /api/evidence-assets/{id}/download
POST /api/answer-audit-logs/{id}/evidence-assets/upload
POST /api/answer-audit-logs/{id}/evidence-assets/register
POST /api/answer-audit-logs/{id}/evidence-assets/{asset_id}/download
```

Runtime retrieval requires an application JWT with `answer_audit:evidence:read`. Bind the response's `source_ref` and `access_event_id` into an answer created by the same application key.


---

# 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://rawctx.gitbook.io/rawctx-docs/api-reference/rawctx-http-api/answer-evidence.md?ask=<question>&goal=<endgoal>
```

`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.