Sends a token the client holds to another address. This endpoint builds, signs, and submits a transaction to an RPC gateway.
Important: A 200 response only confirms that the transaction was received by the RPC gateway — it does not mean the transaction is confirmed on-chain.
Client API Key or Client Session Token
A unique key to ensure the request is processed only once. If the same key is sent with an identical body, a 409 is returned. If the same key is sent with a different body, a 422 is returned.
Request body for sending assets.
The MPC share for the relevant curve.
The blockchain network. Accepts a CAIP-2 chain ID or a friendly name
such as ethereum, solana, polygon, base, sepolia, etc.
The recipient's address.
Token contract address (ERC-20), mint address (SPL), or a shorthand
like NATIVE, USDC, or USDT.
The amount of tokens to send (e.g. "0.1" is 0.1 of the token).
The RPC node provider URL that the transaction will be submitted through. Not required for Solana or Solana Devnet.
Hex string of the nonce to set on the transaction (e.g. "0x01").
Must include the 0x prefix and a leading zero for single digits.
Optional metadata string for the transaction.
Set to false to opt out of gas sponsorship for Account Abstraction
clients. Defaults to true when omitted.
The data value from a presign response. Omit for standard
(non-presigned) signing.