---
title: "work: run procedure"
description: "the procedure and its inputs to a task"
section: reference
address: /reference/work/run_procedure
contract: 0476e35e6e275db5
---

# work: run procedure

the procedure and its inputs to a task

[figure: The caller sends RunProcedureInput to /v1/work/run_procedure. The platform returns a card whose body is Task.]

<span class="op-method">POST</span><span class="op-path">/v1/work/run_procedure</span><span class="op-note">a task, 202</span>

Follow a named procedure. The call needs the strategy rung under a token with the work grant, and it is served by either, by the size bound.

The route takes [RunProcedureInput](/concepts/runprocedureinput) and returns a card whose body is [Task](/concepts/task).



## Request body
The request body is [RunProcedureInput](/concepts/runprocedureinput).



| field | type | required | note |
|---|---|---|---|
| `procedure` | [NamedProcedure](/concepts/namedprocedure) | yes |  |
| `inputs` | `json` | no |  |



## Response
The route returns a card whose body is [Task](/concepts/task). 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. This route runs as a long step and returns a task with status 202. `POST /v1/work/status` returns the task's progress, and `POST /v1/work/cancel` stops the task.

## 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 strategy rung and a token with the work grant. The platform or the desktop app serves this route.

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

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





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




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




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




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




</details>

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