---
title: "read: market twin"
description: "Reads one market twin, and the date to read it as of to The answer gives the twin: the model family and template it was instanced from, the participants placed on the chain, the level of every stock as of the date, the simulations run on it in order, and the strategy whose armed plays are its interventions"
section: reference
address: /reference/read/market_twin
contract: 0476e35e6e275db5
---

# read: market twin

Reads one market twin, and the date to read it as of to The answer gives the twin: the model family and template it was instanced from, the participants placed on the chain, the level of every stock as of the date, the simulations run on it in order, and the strategy whose armed plays are its interventions

[figure: The caller sends MarketTwinInput to /v1/read/market_twin. The platform returns a card whose body is MarketTwin.]

<span class="op-method">POST</span><span class="op-path">/v1/read/market_twin</span>

Read the twin of a market. The call needs the brand rung under a token with the read grant, and it is served by either, by the size bound.

The route takes [MarketTwinInput](/concepts/markettwininput) and returns a card whose body is [MarketTwin](/concepts/markettwin).



## Request body
The request body is [MarketTwinInput](/concepts/markettwininput).



| field | type | required | note |
|---|---|---|---|
| `twin` | `id` | yes |  |
| `as_of` | `time` | no |  |



## Response
The route returns a card whose body is [MarketTwin](/concepts/markettwin). 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 brand 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 MarketTwinInput allows. The build validates it against the schema of MarketTwinInput.

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





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




```typescript
import { client } from "@scale/sdk";
const answer = await client.read.market_twin({
    "twin": "…"
  });
// answer.body is a MarketTwin. answer.foot holds the basis, the scope and the time.
```




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




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




</details>

## MCP tool
The MCP tool `si.read.market_twin` takes the same input and returns the same card. The tool only reads data. An MCP host that renders cards draws this card from `ui://scale-intelligence/cards/MarketTwin`. The [tool's page](/reference/tools/si-read-market_twin) describes it.
