---
title: "act: bind buyer"
description: "the kind, an offering or a segment, the weight, the mode to the binding, and the preview of the kind's members"
section: reference
address: /reference/act/bind_buyer
contract: 0476e35e6e275db5
---

# act: bind buyer

the kind, an offering or a segment, the weight, the mode to the binding, and the preview of the kind's members

[figure: The caller sends BindBuyerInput to /v1/act/bind_buyer. The platform returns a card whose body is BindBuyerAnswer.]

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

Bind a buyer profile. The call needs the brand rung under a token with the act grant, and it is served by the platform.

The route takes [BindBuyerInput](/concepts/bindbuyerinput) and returns a card whose body is [BindBuyerAnswer](/concepts/bindbuyeranswer).



## Request body
The request body is [BindBuyerInput](/concepts/bindbuyerinput).



| field | type | required | note |
|---|---|---|---|
| `kind_of_buyer` | `id` | yes |  |
| `bindings` | [Binding](/concepts/binding) | yes |  |
| `ladder` | `text` | no | the ladder the kind climbs, by its name, where the binding changes it; the ladder must be kept and ready |



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

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

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





```sh
curl -X POST https://api.scaleintelligence.co/v1/act/bind_buyer \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "kind_of_buyer": "…", "bindings": [] }'
```




```typescript
import { client } from "@scale/sdk";
const answer = await client.act.bind_buyer({
    "kind_of_buyer": "…",
    "bindings": []
  });
// answer.body is a BindBuyerAnswer. answer.foot holds the basis, the scope and the time.
```




```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/bind_buyer",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "kind_of_buyer": "…",
      "bindings": []
    }).json()
```




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




</details>

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