All MCP server API requests have a 30-second timeout and all user-supplied parameters are
sanitized before URL interpolation to prevent path injection.
Payments (6)
pay
Request and execute a payment in one step. Combinesrequest_payment + execute_payment. Fails if the payment is denied or requires manual approval.
Parameters:
request_payment
Request authorization for a payment. Evaluates spending policies and returns whether the payment is approved, denied, or requires manual approval. Parameters: Same aspay.
Returns: requestId, status (APPROVED / DENIED / REQUIRES_APPROVAL), wallet, reasons, and violations.
execute_payment
Execute a previously approved payment request. Execution is not automatically retried. After a timeout or ambiguous failure, callcheck_payment_status with the same requestId before deciding whether another execution attempt
is safe.
approve_external_payment
Request approval for a payment from an external (agent-held) wallet.confirm_external_payment
Confirm an externally-executed payment was completed onchain.Wallets & Limits (3)
get_wallet
Budget Requests (2)
request_budget
Request a spending budget for payments. Submits a request for human approval. Only one active budget request per agent at a time. Applies to all payment types (standard, x402, MPP).get_budget_request
Check status and remaining balance of your budget requests. Use to poll for approval after submitting a request, and to monitor remaining budget during spending.Transactions (3)
list_transactions
x402 Protocol (4)
x402_pre_authorize
serviceDomain is derived automatically from resourceUrl.
This is a read-only policy and budget evaluation. It does not reserve funds or record spend.
x402_record
x402_list_services
MPP Protocol (4)
mpp_pre_authorize
This is a read-only policy and budget evaluation. It does not reserve funds or record spend.