> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kovrex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Reporting what an answer cost

> Reporting version, model, tokens, time and cost with an answer: where it goes, the fields and limits, and what Kovrex does with a bad report.

Your specialist may tell Kovrex what each answer cost it: which version made it, which model, how many tokens went in and out, how long it took, and what it cost. Kovrex keeps the figures so that prices and tests of new versions can be based on real runs. **Nothing here is shown to the assistant or to the person.** Kovrex removes the extension, its key in metadata and its address in a list of `extensions`, from everything it passes on: the answer, each streamed event, a status check, and the person's record. Reporting is optional, and an answer is carried the same whether you report or not.

## How to report

Put an object under `https://kovrex.ai/ext/run/v1` in the `metadata` of the answer: the task or message you send whole, the final `statusUpdate` of a stream, or the task you post to a return address when you deliver a result (\[[Long-running tasks](https://docs.kovrex.ai/specialists/long-running.md)]\(/specialists/long-running)). Kovrex also finds it in the metadata of a status message, an artifact, or a part, and removes it from all of them. Only the exact key above, at the top level of a metadata map, is read; another spelling, or the key inside another extension's value, is passed on like any other metadata and not recorded. Report once, on the last event. If you report again for the same answer, the later report replaces the earlier one **whole**: a field the later report leaves out is left empty, not kept from the first.

```json theme={null}
{ "jsonrpc": "2.0", "id": "…", "result": { "task": {
    "id": "meridian-task-812", "contextId": "meridian-conversation-77",
    "status": { "state": "TASK_STATE_COMPLETED" },
    "artifacts": [ { "artifactId": "answer", "parts": [ { "text": "…" } ] } ],
    "metadata": {
      "https://kovrex.ai/ext/run/v1": {
        "version": "3f9c2e1",
        "model": "claude-opus-5-5",
        "input_tokens": 5300,
        "output_tokens": 1840,
        "duration_ms": 41000,
        "cost_usd": 0.0449,
        "parts": [
          { "name": "stem", "input_tokens": 1700, "output_tokens": 600, "duration_ms": 14000 }
        ]
      } } } } }
```

| Field | Type and limit |
| - | - |
| `version` | Text, up to 100 characters. The version of your specialist that made the answer, such as a commit. |
| `model` | Text, up to 200 characters. Several models: list them in the one string. |
| `input_tokens`, `output_tokens` | Whole numbers from 0 to 1,000,000,000,000. |
| `duration_ms` | A whole number from 0 to 1,000,000,000,000: the time taken for the whole answer. |
| `cost_usd` | A number from 0 to 1,000,000, in US dollars. Kept to six decimal places. |
| `parts` | Up to 16 entries, each with a `name` (text, up to 64 characters) and any of `input_tokens`, `output_tokens` and `duration_ms`, as above. For example one entry for each lens of a review. |

**Numbers only, never content.** The report holds figures and short labels. Do not put text from the conversation, a prompt, or a person's details in it.

## What happens to a report that is wrong

Your event must still be valid JSON, with numbers in an ordinary range: a number like `1e999`, or nesting deeper than the parser allows, makes the whole event invalid and Kovrex refuses it as it would any other invalid event. Within that, a wrong or oversized report never breaks a conversation:

* A field of the wrong type or out of range is dropped, and the rest is kept. Text over its limit is cut, and entries of `parts` beyond the sixteenth are dropped.
* A field Kovrex does not know is ignored.
* A report that is not an object, is larger than 16 KB, or has no usable field is not kept at all.
* In every case the extension is removed from what goes on, and the answer arrives as it would have.

## Try it

Echo, the stand-in specialist, reports for the words **`metrics`** (a whole or streamed answer), **`long metrics`** (a deferred answer, reported on the delivered result), **`bad metrics`** (figures of the wrong types) and **`huge metrics`** (a report far over the size limit). Kovrex records the first two and drops the last two; the answer arrives each time, without any of it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.