kyc_proof_challenge
Step one of using Crystal from an agent (owner, 17/11/2026: the API, the MCP and the CLI need the KYC for Crystal too). Crystal runs only for a wallet whose identity check (KYC) is approved, and only when the caller proves it holds that wallet. This challenge of its own, scope kyc, says the wallet is yours so Vurto may use its KYC for the analyses that require it, valid 10 minutes to sign; it moves no funds, approves no payment and authorizes no destination. chainId is any network check_info lists (it picks the family; on EVM, the typed data domain). Returns { nonce, message, expiresAt, buildId (kyc-proof-), typedData (EVM) | proofTransaction (Solana) }. Sign it with prepare_signing, then call kyc_proof. The KYC itself is done once by the person on the site; this only proves the wallet.
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": {
"wallet": "<wallet>",
"chainId": "<chainId>"
},
"name": "kyc_proof_challenge"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wallet | Yes | The wallet to prove: the receiver of the invoice, or the payer of the batch. | |
| chainId | Yes | EVM: integer from GET /v1/chains (1, 10, 56, 100, 137, 8453, 42161, 43114, 130). Solana: string from GET /v1/svm/chains ("solana-mainnet"). |