---
title: Receipts
description: Trace an answer to its facts, calculations and sources; keep the evidence with the case.
icon: receipt
---

Every completed execution returns `answers`, `receipt` and `usage`. Keep the receipt with your submitted model and original state when you need evidence. It returns inline; there is no receipt-history lookup.

## Read the refund result

This shortened receipt is from the combined run in the [quickstart](/docs/quickstart): Jev read the customer’s message, then the cancellation Decision calculated the result:

```json
{
  "read": {
    "customer_intent": { "value": "cancel_refund", "source": "jev" }
  },
  "provenance": {
    "plan_amount": "state",
    "period_days": "state",
    "unused_days": "state",
    "accepted_on": "state",
    "refundable": "state",
    "customer_intent": "jev"
  },
  "decisions": {
    "refund_eligible": { "value": true },
    "refund_amount": { "value": 20 },
    "processing_deadline": { "value": "2026-10-28" }
  }
}
```

`provenance` identifies the account facts supplied in `state`; the receipt does not duplicate their values. `read.customer_intent` came from Jev reading the message. The Decision calculated $20 and October 28; Jev did not invent the refund amount or date.

In a Decision-only run, `read` is empty and every input’s provenance is `state`. In Jev + Decision runs, `read` contains the named Jev facts with `source: jev`. Jev’s answers also appear in the response’s `answers`, alongside native answers; there is no separate full upstream response in the public result.

## Keep the rule with the result

`decisions` records computed values and executed rules or branches. `functions` records function evaluation. A table’s `# why` annotation belongs to the definition; it is not a reason generated after the answer. Keep the model so rule references remain meaningful. The receipt describes what ran, not whether your terms or facts are correct.

Keep three things together:

1. The native model submitted for this case.
2. The original state, including any message or evidence.
3. The returned answers and receipt.

Public receipt JSON contains `read`, `provenance`, `decisions` and optional `functions`. They do not return a receipt id, the submitted model, input schema, questions or matching state values. The console combines the trace with its locally retained request to display those input values.

## Usage and failures

Response `usage` reports billable input and output tokens. Timing, settled charges, provider counts and balance are console/internal details. Every shape uses the same single rate. See [Pricing and limits](/docs/resources/pricing-and-limits).

If Jev succeeds but the following native model fails, HTTP `200` includes `decision_error` and preserves Jev’s answers. Check that field before treating the result as a completed native decision. See [Errors](/docs/resources/errors).

To compare a model change, execute the same states against original and revised definitions. [Compare revised rules](/docs/guides/revise-and-replay) provides a client script; no stored receipt history is required.
