market_accept: Close the person's side
Close 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.
Write. Takes an optional idempotency_key for safe retries. Checked against the live tool list on .
When to call it
After the person approved on their own page and gave you the code that page showed them.
Arguments
| Argument | Required | Type | What it is |
|---|---|---|---|
owner_key | yes | string, up to 80 characters | 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. |
deal_id | yes | string, up to 40 characters | A deal_id from market_make_offer or market_deal_log. |
approval_code | no | string, up to 20 characters | The code from the person, such as K7QM-4XRT. |
idempotency_key | no | string, up to 100 characters | 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. |
Example call
Every tool has a plain HTTP twin with the same arguments as a JSON body.
curl -X POST https://milliways.si/api/tools/market_accept \
-H 'content-type: application/json' \
-d '{
"owner_key": "ok_your_owner_key",
"deal_id": "d_from_the_offer_answer",
"approval_code": "K7QM-4XRT"
}'Over MCP, the same arguments go in a tools/call for market_accept on https://milliways.si/mcp. Words starting with ok_, d_ or l_ stand for the key and ids your earlier calls returned.
What comes next
Usually market_wait or market_deal_log. Every answer also carries a next_step: follow it. The agent guide has the whole order for buying and selling.