Payments Actions
Platform-mode money actions. Every payment is signed in 0xGasless KMS, checked against the project’s spending policy, and settled gaslessly by the facilitator — the agent wallet holds only stablecoin, never AVAX.
Amounts are in atomic units: USDC and XSGD both have 6 decimals, so
"1000000" = 1.00.
x402_pay
Section titled “x402_pay”Pay a recipient address directly.
| Argument | Type | Description |
|---|---|---|
to | string | Recipient EVM address. |
value | string | Amount in atomic units ("1000000" = 1.00). |
tokenSymbol | string | Optional. USDC (default) or XSGD. |
pay_api
Section titled “pay_api”Fetch a URL and, if it answers 402 Payment Required, automatically pay and
retry — the whole x402 handshake in one action.
| Argument | Type | Description |
|---|---|---|
url | string | The URL to fetch. |
maxValue | string | Required. Hard cap in atomic units. If the API asks for more, the call refuses to pay. |
The mandatory maxValue is the guardrail: the LLM can never be talked into an
unbounded payment by a malicious endpoint.
smart_transfer
Section titled “smart_transfer”Transfer USDC/XSGD to an address in human units ("1.5" = 1.5 USDC). In
platform mode this routes through the same policy-checked x402 rail; in
self-custody mode it sends an ERC-4337 gasless transaction.
get_spend_status
Section titled “get_spend_status”Read the agent’s own limits: per-transaction cap, daily cap, and remaining budget for today. Agents can check this before committing to paid work.
get_agent_wallet
Section titled “get_agent_wallet”The agent’s address, chain, status, and token balances — used to answer “what’s your address?” so you can fund it.
Where the policy lives
Section titled “Where the policy lives”Caps are set per project (and per agent) in the Dashboard — the server enforces them on every signature, so a compromised prompt cannot exceed them.