---
title: "act: change plan"
description: "the plan kind to the change as a proposal, and the provider's own page for payment"
section: reference
address: /reference/act/change_plan
contract: 0476e35e6e275db5
---

# act: change plan

the plan kind to the change as a proposal, and the provider's own page for payment

[figure: The caller sends ChangePlanInput to /v1/act/change_plan. The platform returns a card whose body is PlanChange.]

<span class="op-method">POST</span><span class="op-path">/v1/act/change_plan</span>

Change the plan. The call needs the tenant rung under a token with the admin grant, and it is served by the platform.

The route takes [ChangePlanInput](/concepts/changeplaninput) and returns a card whose body is [PlanChange](/concepts/planchange).



## Request body
The request body is [ChangePlanInput](/concepts/changeplaninput).



| field | type | required | note |
|---|---|---|---|
| `plan_kind` | `one of trial \| paid \| internal` | yes |  |



## Response
The route returns a card whose body is [PlanChange](/concepts/planchange). 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 admin grant. The platform serves this route.

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

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





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




```typescript
import { client } from "@scale/sdk";
const answer = await client.act.change_plan({
    "plan_kind": "trial"
  });
// answer.body is a PlanChange. answer.foot holds the basis, the scope and the time.
```




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




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




</details>

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