Call x402 Endpoint logo

Built-in action X402 wallet

Call an x402 pay-per-use API endpoint. Payment is handled automatically using your connected wallet — no manual steps needed.

This action can require a wallet connector, gas, token movement, or an external side effect. Test with simulation or a controlled amount before using it in a live workflow.

At a Glance

FieldValue
Action IDcall-x402-endpoint
CategoryX402
Connectorwallet
Requires gasNo
Funds movementNone declared
Tagsx402, payment, api, pay-per-call

Payload Schema

FieldTypeRequiredDescription
endpointIdstringYesThe ID of the x402 endpoint to call (from the endpoint registry)
maxPricestringNoOptional override for maximum allowed price (in token's smallest unit). If not specified, uses the endpoint's default max price.

Result Schema

FieldTypeRequiredDescription
statusstringYesWhether the request succeeded or failed
statusCodenumberNoHTTP status code from the response
resourceobjectNoThe fetched resource data (parsed JSON response from the endpoint). Access nested fields with {{nodeId.result.resource.fieldName}}
paymentDetailsobjectNoPayment transaction details
requestDetailsobjectNoDetails of the request that was made
responseHeadersobjectNoResponse headers from the resource server
errorstringNoError message if failed

Examples

json
{ "type": "call-x402-endpoint", "payload": { "endpointId": "x402_abc123" }, "children": [], "connector": { "type": "wallet", "id": "conn_wallet" }}

Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.

Ask a question... ⌘I