Skip to main content
You can transfer SOL and any SPL token from your agent’s wallet to any Solana address. The API handles transaction signing, fee calculation, and on-chain confirmation.

​
Transfer SOL

Omit the mint field to send native SOL: 
curl -X POST https://api.useknot.xyz/wallets/me/actions/transfer \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "RecipientSolanaAddress...",
    "amount": 0.5
  }'

​
Transfer SPL tokens

Include the mint field to send an SPL token. You can identify the token by its common symbol or its full mint address: 
curl -X POST https://api.useknot.xyz/wallets/me/actions/transfer \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "RecipientSolanaAddress...",
    "amount": 100,
    "mint": "USDC"
  }'

​
Request parameters

​
to
string
required
Recipient’s Solana address.
​
amount
number
required
Amount to transfer.
​
mint
string
Token symbol (e.g., USDC, BONK) or the token’s mint address. Omit this field for a native SOL transfer.

​
Response

{
  "status": true,
  "data": {
    "signature": "5UfgJ3vN...",
    "explorerUrl": "https://solscan.io/tx/5UfgJ3vN...",
    "amount": "100 USDC",
    "amountSent": 98.9,
    "fee": 1.1,
    "feeMode": "deducted",
    "recipient": "RecipientSolanaAddress..."
  }
}

​
Response fields

​
data
object

​
Fee structure

Knot charges a small fee on every transfer to cover infrastructure costs:
Fee typeAmount
Percentage fee1% of transfer amount
Flat fee$0.10 equivalent (covers signing costs)

​
Fee modes

The fee handling depends on your wallet’s available balance:
If the wallet holds more than the transfer amount, the fee is added on top. The recipient receives exactly the amount you specified.
Check the feeMode field in the response to see which method was applied:
  • added — fee was charged on top; recipient got the full amount
  • deducted — fee was taken from the transfer; recipient got less

​
Policy constraints

Transfers are subject to your agent’s spending limits. If a transfer exceeds the configured limit, the request will be rejected with a 403 error. Review your policy settings to adjust spending limits.

​
Error scenarios

The wallet does not have enough SOL or tokens to cover the transfer amount plus fees. Top up your wallet before retrying.
The to address is not a valid Solana public key. Verify the address and retry.
The value provided in mint is not a recognized symbol and does not match a known mint address. Use the full mint address instead.
The transfer amount exceeds the limit defined in your agent’s policy. A 403 error is returned. Adjust the policy or reduce the transfer amount.
Use idempotency keys on transfer requests to prevent duplicate transactions in case of network failures. See Idempotency for details.