Assess Counterparty and Job
assess_counterparty_and_jobSingle pre-flight check before locking funds in escrow.
Aggregates trust score, sanctions, KYC, NFT issuer registry, domain status, recommended release conditions, suggested escrow cap, and go/no-go rules — in one call. Run this before create_escrow_vault or hire_and_pay.
Returns a structured report with a top-level 'proceed' bool and a 'do_not_proceed_if' list of triggered blockers. If proceed is False, do not lock funds.
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": {
"worker_address": "<worker_address>"
},
"name": "assess_counterparty_and_job"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| network | No | 'mainnet' (default), 'testnet', or 'auto' (tries mainnet then testnet if not found). Testnet wallets pass proceed:true even with low scores. | auto |
| job_type | No | Natural-language description of the work — e.g. 'software development', 'gig tickets', 'W3C credential', 'invoice payment'. Used to recommend release conditions. | general |
| amount_xrp | No | How much XRP you plan to lock in escrow. Used to check whether the counterparty's KYC level allows it. | |
| worker_address | Yes | The XRPL wallet address of the counterparty you are considering hiring or paying. | |
| nft_issuer_query | No | If the job involves an NFT proof, pass the issuer name or wallet address to check the registry. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||