sap_x402_settle
InactiveTool of SAP MCP Server
Settle served x402 calls through SDK X402Registry.settle. Must be called by the agent owner wallet. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval.
Parameters schema
{
"type": "object",
"properties": {
"nonce": {
"type": "string",
"description": "Optional escrow nonce as a decimal string. Defaults to 0."
},
"commitment": {
"type": "string",
"description": "Optional processed|confirmed|finalized commitment"
},
"maxRetries": {
"type": "number",
"description": "Optional RPC retry limit"
},
"serviceData": {
"type": "string",
"description": "Service data to hash into the settlement proof"
},
"computeUnits": {
"type": "number",
"description": "Optional compute-unit limit"
},
"callsToSettle": {
"type": "number",
"description": "Number of calls to settle"
},
"skipPreflight": {
"type": "boolean",
"description": "Optional skip preflight flag"
},
"depositorWallet": {
"type": "string",
"description": "Depositor wallet public key (base58)"
},
"priorityFeeMicroLamports": {
"type": "number",
"description": "Optional priority fee in microlamports per compute unit"
}
}
}No endpoints wrapped at confidence ≥ 0.50.
Parent server
SAP MCP Server
https://github.com/OOBE-PROTOCOL/sap-mcp
2/7 registries