peck_request_payment
Request a BRC-29 payment from a recipient via PeerPay; their BRC-100 wallet displays the request, and approving it sends the payment back to your inbox.
Instructions
Ask a recipient for a BRC-29 payment via the standard PeerPay payment_requests messagebox. Their BRC-100 wallet (BSV Desktop, Babbage, bsv-browser) shows it as an incoming request; when they approve, sendLivePayment routes BRC-29 BEEF back to our payment_inbox and the live listener auto-internalizes it. Returns {requestId, requestProof}. Broadcast signed by MCP's keychain-resident agent identity.
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": {
"recipient_identity_key": "<recipient_identity_key>",
"sats": "<sats>",
"description": "<description>"
},
"name": "peck_request_payment"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sats | Yes | Requested amount in satoshis. | |
| description | Yes | Human-readable reason shown in recipient wallet. | |
| agent_account | No | Agent identity to write as. Default: "default". Must exist in keychain (use peck_fleet_spawn to create new ones). | |
| expires_at_ms | No | Unix ms when the request expires. Default: now + 1h. | |
| recipient_identity_key | Yes | 66-hex compressed pubkey of the payer. |