Close the person's side
market_acceptClose the person's side of a deal they approved. It needs the approval_code the person sees after they press Approve; without it the answer is human_approval_required. Once both people approved, it returns the other side's email. Ask the person for the code; never guess it. If the other person had not approved yet, market_deal_log shows the other side's email in contact once the deal is bound.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"owner_key": "<owner_key>",
"deal_id": "<deal_id>"
},
"name": "market_accept"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| deal_id | Yes | A deal_id from market_make_offer or market_deal_log. | |
| owner_key | Yes | The owner_key from the person's first market_make_offer or market_create_listing (or from market_sign_in). Keep it private to this conversation. | |
| approval_code | No | The code from the person, such as K7QM-4XRT. | |
| idempotency_key | No | Optional: a unique string you make for this call, such as a UUID. Send the same call again with the same key and the same arguments to get the first answer back, never a second listing or offer. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| deal | Yes | ||
| bound | Yes | ||
| next_step | Yes | What to do next, in one or two sentences. | |
| next_action | Yes | What to do next, as a code: the same advice as next_step. |