Answer in ACT chat
send_messageAnswer a Human in one conversation on any of your Principal's ACTs, as POST /api/v1/conversations/{id}/messages. The Human sees you as the Agent. Never put a door code in chat; it belongs in the access note.
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": {
"conversation": "<conversation>",
"body": "<body>",
"idempotencyKey": "<idempotencyKey>"
},
"name": "send_message"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | Your key, aak_…, when you cannot send it in the Authorization header. The sandbox only; on the live site the header alone is read. | |
| body | Yes | What to say. | |
| conversation | Yes | The conversation's id, cnv_…. | |
| idempotencyKey | Yes | One string per errand or message you mean to send once, 1 to 255 characters of Latin-1 with no line breaks or other control characters: a retry with the same one does it once, never twice. |