---
title: "economics: benchmarks"
description: "a driver, and a population or a buyer profile to the benchmarks that apply, each with its interval, population, period, source and what its rights allow"
section: reference
address: /reference/economics/benchmarks
contract: 0476e35e6e275db5
---

# economics: benchmarks

a driver, and a population or a buyer profile to the benchmarks that apply, each with its interval, population, period, source and what its rights allow

[figure: The caller sends BenchmarksInput to /v1/economics/benchmarks. The platform returns a card whose body is [Benchmark].]

<span class="op-method">POST</span><span class="op-path">/v1/economics/benchmarks</span>

Si.economics.benchmarks. The call needs the tenant rung under a token with the read grant, and it is served by either, by the size bound.

The route takes [BenchmarksInput](/concepts/benchmarksinput) and returns a card whose body is [Benchmark](/concepts/benchmark).



## Request body
The request body is [BenchmarksInput](/concepts/benchmarksinput).



| field | type | required | note |
|---|---|---|---|
| `driver` | [KindOfMeasure](/concepts/kindofmeasure) | yes |  |
| `kind_of_buyer` | `text` | no |  |



## Response
The route returns a card whose body is [Benchmark](/concepts/benchmark). Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true.

## Headers


| header | required | meaning |
|---|---|---|
| `Scale-Scope` | yes | the scope the call runs in: tenant/<id>, then /brand/<id>, then /strategy/<id> |
| `Scale-As-True-On` | no | the date the facts must have been true on; defaults to now |
| `Scale-As-Known-On` | no | the date the facts must have been known on; defaults to now |
| `Scale-Key` | no | for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing |



A caller needs the tenant rung and a token with the read grant. The platform or the desktop app serves this route.

## Example
The example sends the smallest body that BenchmarksInput allows. The build validates it against the schema of BenchmarksInput.

<details class="wire"><summary>Example</summary>





```sh
curl -X POST https://api.scaleintelligence.co/v1/economics/benchmarks \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "driver": "…" }'
```




```typescript
import { client } from "@scale/sdk";
const answer = await client.economics.benchmarks({
    "driver": "…"
  });
// answer.body is a [Benchmark]. answer.foot holds the basis, the scope and the time.
```




```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/economics/benchmarks",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "driver": "…"
    }).json()
```




```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/economics/benchmarks")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&BenchmarksInput { /* the fields of the page */ }).send().await?.json().await?;
```




</details>

## MCP tool
The MCP tool `si.economics.benchmarks` takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from `ui://scale-intelligence/cards/Benchmark`. The [tool's page](/reference/tools/si-economics-benchmarks) describes it.
