> For the complete documentation index, see [llms.txt](https://stellar-developer-tools.gitbook.io/anchortrace-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stellar-developer-tools.gitbook.io/anchortrace-sdk/guide/install-and-run.md).

# Install and run

Published to npm as `@anas.abubakar/anchortrace-sdk`. From a clone (Node 22 or newer, pnpm 11):

```bash
git clone <this repo> && cd anchortrace-sdk
pnpm install --frozen-lockfile
pnpm build
node dist/cli.js reconcile examples/cases/wrong-issuer.case.json
```

```bash
# a SEP-24 record file plus evidence files (raw Horizon /transactions/{hash} and /operations bodies)
node dist/cli.js reconcile record.json --evidence ops.json

# the same, reading the transaction live from Horizon (read-only GET)
node dist/cli.js reconcile examples/sep24/wrong-issuer.sep24.json --horizon testnet --network testnet

node dist/cli.js reconcile record.json --evidence ops.json --format json --out report.json
node dist/cli.js explain report.json                 # step-by-step why, and what would change it
node dist/cli.js export report.json --redact --out shareable.json
node dist/cli.js validate record.json                # offline shape check
node dist/cli.js schema report > report.schema.json
```

Options that change the verdict are explicit: `--fee-policy anchor_deducted|customer_paid_on_top|no_fee` (default `anchor_deducted`, echoed in the report), `--asset CODE:ISSUER|native` when the record omits the asset (it is never guessed), `--tolerance-bps`, `--anchor-account` (deposits), `--network testnet|public`.

Exit codes: `0` no failing outcome; `1` an outcome named by `--fail-on` (default `discrepant,ambiguous,unsupported,insufficient_evidence`; `--strict` adds `pending`); `2` invalid input or usage; `3` unexpected error.


---

# 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://stellar-developer-tools.gitbook.io/anchortrace-sdk/guide/install-and-run.md?ask=<question>&goal=<user_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.