Agent Privacy API

When an agent moves tokens on Solana, the transaction graph shows who paid whom. Anyone can trace the funding source to the destination. The Agent Privacy API (/agents/v1) breaks that link. It serves two agent needs: private on-chain swaps and encrypted inference. The main Solrouter SDK covers encrypted chat and research. One agent type swaps tokens privately. The other has no API key and pays per inference call with x402, a pay-per-request HTTP standard. The Solrouter backend and a swap worker run the swaps. The TEE (trusted execution environment, a hardware-isolated enclave) does not. Only the x402 inference endpoint on this page uses the encrypted TEE path.

Feature status

Execution modes

Pick a mode by one question: does your agent keep a funded wallet with Solrouter, or sign each operation on the fly? The API supports both.

# Provision a managed wallet for this agent
curl -X POST "https://api.solrouter.com/agents/v1/wallets" \
  -H "Authorization: Bearer sk_solrouter_..." \
  -H "Content-Type: application/json" \
  -d '{}'
# -> { "walletId": "...", "umbraAddress": "...", "network": "mainnet", "fundingHint": "..." }

# Fund umbraAddress, then run a swap from the managed wallet
curl -X POST "https://api.solrouter.com/agents/v1/wallets/WALLET_ID/swap" \
  -H "Authorization: Bearer sk_solrouter_..." \
  -H "Content-Type: application/json" \
  -d '{
    "fromMint": "So11111111111111111111111111111111111111112",
    "toMint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "amount": "10000000",
    "destinationPubkey": "YOUR_FRESH_DESTINATION_ADDRESS"
  }'
# -> { "sessionId": "...", "status": "running", "estimatedSeconds": 70 }

# 1. Create the session
curl -X POST "https://api.solrouter.com/agents/v1/swaps/oneshot" \
  -H "Content-Type: application/json" \
  -d '{
    "payerPubkey": "YOUR_AGENT_WALLET_PUBKEY",
    "fromMint": "So11111111111111111111111111111111111111112",
    "toMint": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "amount": "10000000",
    "destinationPubkey": "FRESH_DESTINATION_ADDRESS"
  }'
# -> { "sessionId": "...", "ephemeralPubkey": "...", "fundingTx": "<base64>", "expectedSeconds": 75, ... }

# 2. Sign fundingTx with your wallet and broadcast it.
# 3. Submit the confirmed signature:
curl -X POST "https://api.solrouter.com/agents/v1/swaps/oneshot/SESSION_ID/execute" \
  -H "Content-Type: application/json" \
  -d '{"fundingTxSig": "..."}'

# 4. Poll until state is settled
curl "https://api.solrouter.com/agents/v1/sessions/SESSION_ID"

What Solrouter stores per session: from_mint, to_mint, amount_base_units, destination_pubkey, payer_user_id, ephemeral_pubkey, the wrapped ephemeral key, final_tx_sig, and actual_out. Solrouter's backend can read every column. Retention period: not published.

Discovery endpoints

So your agent does not hardcode URLs, the API publishes its own configuration. A2A-compatible agents (the Agent-to-Agent interop protocol) and x402-aware runtimes read these endpoints to self-configure at runtime.

The manifest is served by the API host: https://api.solrouter.com/.well-known/x402.

x402 encrypted inference

Not every agent has an API key, and account creation is friction. For those cases Solrouter exposes a pay-per-call encrypted inference endpoint. Your agent pays in USDC on Solana mainnet, with no account and no key management. x402 is the standard. The live manifest advertises Coinbase (api.cdp.coinbase.com/x402) as the facilitator. The manifest shows X402_FACILITATOR_URL when set, or a built-in default when not. It does not show which facilitator settles payments. pay.sh is a catalog that lists the endpoint.

• Endpoint: POST /api/v1/x402/chat/completions
• Pricing: $0.005 per call, settled via x402 USDC on Solana mainnet
• Encryption: Arcium-encrypted prompt in, encrypted response out. The same TEE path as the SDK.
• Discovery: /.well-known/x402. Any x402-aware runtime can auto-discover pricing and payment instructions.

# x402 paywalled encrypted inference. No API key needed.
# `encryptedPrompt` MUST be an Arcium ciphertext produced client-side.
# Use encrypt(message, baseUrl) and packageForTEE(encryptedData) from @solrouter/sdk.
# `model` is required.
curl -X POST "https://api.solrouter.com/api/v1/x402/chat/completions" \
  -H "Content-Type: application/json" \
  -d '{"encryptedPrompt": "<base64 Arcium ciphertext>", "model": "gpt-oss:20b"}'

Call the endpoint without payment and the server replies 402 Payment Required with the price, the network, and the payTo address. An x402-aware runtime signs a USDC payment payload with the agent's wallet key and retries with the X-PAYMENT header. Solrouter's server sends that payload to its facilitator to verify and settle the transfer, then returns 200. The agent never talks to the facilitator.