x402 Trust Layer Pipeline (trust-v2)

Use this endpoint when you need a single orchestrated call that runs the full x402 trust stack — guard, escrow, mandate diff, KYM, compliance, and dispute checks — rather than calling individual trust microservices separately. Best when you need a combined allowed/denied decision with a human-readable summary after x402 payment settlement.

• Payment not settled — x402 payment must succeed before trust pipeline executes
• Invalid HTTP method — only GET, HEAD, or DELETE are accepted as input method values
• Missing required 'type' field set to 'http' — will reject with schema validation error
• Mandate not found or expired — trust check fails with allowed: false
• Seller not in certified network — compliance block returns allowed: false
• Dispute active on account — orchestration halts and returns allowed: false