> For the complete documentation index, see [llms.txt](https://docs.revenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revenium.io/instrument-your-agents/job-type-economics.md).

# Job Type Economics

Tell Revenium what one unit of work is worth for a job type, how the work was done before AI, and what each job achieved, so ROI is measured in your terms.

Cost alone does not tell you whether an agent pays for itself. You also need to know what a unit of its work is worth, and what the same work cost before AI took it on. Job type economics records both for each job type, so the ROI dashboard can set every job's AI cost against the value it produced and against the old way of doing the work.

A job type is the `type` you give a job when you [report outcomes](https://docs.revenium.io/instrument-your-agents/agent-outcomes.md), for example `support-ticket` or `invoice-review`. Job type names are not case-sensitive.

You can set all of this in the app from the ROI dashboard with **New job type** or **Edit job type**. The API does the same thing, which suits teams that keep these figures in code or in a finance system.

### <i class="fa-list">:list:</i> The Four Parts

| Part                | What it records                                                                                                                                                                                | Calls                                                                                                                                                |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Economics**       | The unit of work, the metrics you track for it, and optionally its value per unit and overhead per unit.                                                                                       | [Get](https://revenium.readme.io/reference/get_job_type_economics), [create or replace](https://revenium.readme.io/reference/put_job_type_economics) |
| **Baselines**       | How the work was done before AI: cost, minutes and quality per unit, and an hourly rate. Each baseline is a new version with an `effectiveFrom` date. Earlier versions are kept, never edited. | [List](https://revenium.readme.io/reference/list_job_type_baselines), [add a version](https://revenium.readme.io/reference/create_job_type_baseline) |
| **Per-job metrics** | Values for one job that arrive after it ends, such as a quality score from a later review.                                                                                                     | [Add](https://revenium.readme.io/reference/append_job_outcome_metrics)                                                                               |
| **Period facts**    | Values you only know for a whole period, broken down by one of the dimensions you declared, such as tickets closed per region per month.                                                       | [Add](https://revenium.readme.io/reference/append_job_type_period_facts)                                                                             |

Each metric is declared once in the economics with a `resolution`. A `PER_JOB` metric is reported against a single job. A `PERIOD` metric is reported for a date range. Revenium rejects a value for a metric the job type has not declared.

### <i class="fa-code">:code:</i> Before You Call the API

Every call takes your team id as the `teamId` query parameter. Reading needs a read-only or full-access key. Writing needs a full-access (`rev_sk_`) key. See [API Key Permissions](https://docs.revenium.io/integrations/api-key-permissions.md).

In the economics, the `unitMetricKey` must name one of your metrics, and that metric must be a `COUNT`. Amounts are in US dollars only for now. A `PERCENT` metric value is a fraction between 0 and 1.

### <i class="fa-circle-info">:circle-info:</i> Good to Know

* **Values are added, never overwritten.** Per-job metrics and period facts build a history. To correct a value you have already sent, send it again with a `reason`. Revenium refuses a correction that has no reason.
* **Declare the job type first.** Baselines, per-job metrics and period facts are refused until the job type has economics.
* **The job outcome value has its own call.** Report a job's money value with the [outcome call](https://docs.revenium.io/instrument-your-agents/agent-outcomes.md), not as a metric.

### <i class="fa-link">:link:</i> Related

* [AI Outcomes](https://docs.revenium.io/instrument-your-agents/agent-outcomes.md): report how each job ended.
* [Analyze ROI & Unit Economics](https://docs.revenium.io/track-and-control-costs/analyze-roi-and-unit-economics.md): where these figures appear.


---

# 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://docs.revenium.io/instrument-your-agents/job-type-economics.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.
