Crypto support ticket triage for exchange / wallet helpdesks (situation, priority, bilingual reply) ($0.040)
triage_crypto_support_ticketFor the helpdesk bots and agents of crypto exchanges, wallets and projects: one customer ticket in Chinese or English -> which of 21 common situations it is (deposit not credited, wrong network, missing memo / tag, stuck tx, bridge delay, tokens not showing, fake support DMs, address poisoning, leaked seed phrase, approval drain, phishing site, "fund recovery" scam, hacked account, no gas, ...), priority P0-P3, an honest recoverability call, the networks / coins / amounts / TxIDs / addresses found and what to ask for next, a ready reply in Chinese AND English, the internal note, a pre-filled escalation ticket and the red lines. A seed phrase or private key the customer pasted is caught and redacted (P0). Rule-based, no model. $0.04 a ticket. PAID: $0.040 per call or 40 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/support-ticket-triage.
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": {
"ticket": "<ticket>"
},
"name": "triage_crypto_support_ticket"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Which reply language is primary (both are always returned). auto = the ticket's language. | |
| ticket | Yes | The customer's support message (Chinese or English, max 2500 characters). "text" and "message" are accepted as aliases. | |
| platform_name | No | Optional: your exchange / wallet / project name, filled into the reply (max 60 characters). | |
| official_domains | No | Optional: your official domains, comma-separated (max 10). Look-alikes in the ticket are flagged and the first one fills [official URL]. | |
| official_addresses | No | Optional: your official contract / deposit addresses, comma-separated (max 20). Look-alike addresses in the ticket are flagged. | |
| supported_networks | No | Optional: networks your platform accepts deposits on, comma-separated (ethereum, tron, bsc, arbitrum, optimism, base, polygon, solana, avalanche, ton, bitcoin, xrp; ERC20 / TRC20 / BEP20 work too). Decides the wrong-network reply automatically. |