Payout pre-flight: screen a whole recipient list before a batch payment ($0.050)
screen_payout_recipient_listBefore payroll, bounty / grant / contributor payouts, airdrops or refunds: up to 200 recipients (optionally with amounts) in ONE call. Per row: format, checksum, network, token-contract / burn addresses, pasted tx hashes or keys, OFAC SDN exact match. Whole list: duplicates (paid twice), look-alike pairs (address poisoning or typos), look-alikes of addresses you trust. Returns the rows to pay, the rows to hold and totals. PAID: $0.050 per call or 50 prepaid credits, no account. Pay with x402 over MCP (USDC on Base), or with a credits key bought by a plain USDC transfer (credits_quote / credits_claim, then header Authorization: Bearer ssk_...). An unpaid call returns the payment terms and charges nothing; bad input is rejected before any payment; failed work is never charged. Same data as GET /v1/payout-check.
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": {
"recipients": "<recipients>"
},
"name": "screen_payout_recipient_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| known | No | Optional: up to 50 addresses you already trust (comma-separated); rows that imitate one of them are held. | |
| network | No | Network you will pay on (base, ethereum, arbitrum, tron, solana, bitcoin, ...). Every row is checked against it. Omit to check formats only. | |
| recipients | Yes | Up to 200 recipients: "address" or "address:amount", separated by commas or new lines (CSV "address,amount" lines and a JSON array of {address, amount} also work). Amounts are plain decimals in any unit. |