> 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/reconciliation-and-trust.md).

# Reconciliation and trust

All paths are relative to the authenticated workspace API host.

## Reconciliation

```
POST /api/reconciliations/runs
GET  /api/reconciliations/runs
GET  /api/reconciliations/runs/{run_id}
GET  /api/reconciliations/runs/{run_id}/findings
GET  /api/reconciliations/runs/{run_id}/proof
```

A run covers seven days or less and carries 1 to 10,000 reference records. Application JWTs need `answer_audit:reconcile` and can reconcile only their bound application key. Finding types are `missing_rawctx`, `unexpected_rawctx`, `late_rawctx`, `duplicate_reference`, `duplicate_rawctx`, and `unanchored_rawctx`.

## Workspace trust operations

```
GET  /api/trust/policy
PUT  /api/trust/policy
POST /api/trust/anchors/run
GET  /api/trust/proofs/answers/{answer_log_id}
```

Proof reads require `answer_audit:read` for an application token. Policy and anchor mutations require a tenant manager. Use the official CLI or SDK verification flow and inspect individual `PASS`, `FAIL`, `SKIP`, and `NA` results rather than inferring correctness from a single boolean.

`ANCHORED` requires a confirmed external anchor and any policy-required verified witness bound to the same checkpoint. It does not prove answer correctness, delivery, or source use.


---

# 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/reconciliation-and-trust.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.