Charge the saved card
purchase_executeCharges the saved card of the customer immediately for a purchase they have explicitly agreed to in this conversation. Only call it after they have confirmed the exact item and amount in words - this tool moves real money right away. A refused or unchecked domain ending carries reason and a plain reason_text: unsupported or price_unavailable mean we do not sell that ending right now; lookup_failed or cap_reached mean it was NOT checked, so search again, and never tell the customer we do not sell it.
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": {
"kind": "<kind>",
"item": "<item>",
"consent_confirmed": "<consent_confirmed>",
"consent_item": "<consent_item>",
"consent_amount_cents": "<consent_amount_cents>",
"consent_statement": "<consent_statement>"
},
"name": "purchase_execute"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| item | Yes | The exact thing being bought; for kind='domain', the full domain name. | |
| kind | Yes | What is being bought. Only 'domain' is available in chat today. | |
| consent_item | Yes | The item the customer agreed to buy, as they understood it. If it does not match what is being charged, the charge is REFUSED. | |
| consent_confirmed | Yes | Pass 'user_confirmed' ONLY after the customer has explicitly agreed to this exact purchase and amount in the conversation. Do not set it on your own initiative. | |
| consent_statement | Yes | The customer's own words agreeing to this purchase, relayed verbatim. Must mention the item or the price. Do not invent it — if the customer has not explicitly agreed to this amount, do not call this tool. | |
| consent_amount_cents | Yes | The exact amount in cents the customer agreed to pay. If it does not match the real server-side price, the charge is REFUSED and nothing happens. |