---
title: "session: cache"
description: "nothing, or a call to forget to what the app holds from earlier answers, by call and date, and when each expires"
section: reference
address: /reference/session/cache
contract: 0476e35e6e275db5
---

# session: cache

nothing, or a call to forget to what the app holds from earlier answers, by call and date, and when each expires

[figure: The caller sends CacheInput to /v1/session/cache. The platform returns a card whose body is CacheView.]

<span class="op-method">POST</span><span class="op-path">/v1/session/cache</span>

From the local server's own. The call needs the user rung under a token with the read grant, and it is served by the installed app.

The route takes [CacheInput](/concepts/cacheinput) and returns a card whose body is [CacheView](/concepts/cacheview).



## Request body
The request body is [CacheInput](/concepts/cacheinput).



| field | type | required | note |
|---|---|---|---|
| `forget` | `text` | no | the call name and its input hash |



## Response
The route returns a card whose body is [CacheView](/concepts/cacheview). 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 user rung and a token with the read grant. The desktop app serves this route.

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

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





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




```typescript
import { client } from "@scale/sdk";
const answer = await client.session.cache({});
// answer.body is a CacheView. answer.foot holds the basis, the scope and the time.
```




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




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




</details>

## MCP tool
The MCP tool `si.session.cache` 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/CacheView`. The [tool's page](/reference/tools/si-session-cache) describes it.
