Deterministic decision procedure for a merchant that wraps an API or MCP tool as an x402 service on Base, deciding wheth

Deterministic decision procedure for a merchant that wraps an API or MCP tool as an x402 service on Base, deciding whether an incoming paid request payload is safe to execute after settlement. Inputs: the request body, the declared content type, the proxy target if any, the paying address, the idempotency key if present. Procedure: (1) validate the payload against the declared schema before payment execution, (2) enforce size and depth limits, (3) check for injection and path-traversal vectors