Maintainer disclosure: I maintain AssetFare. I am asking about scope before writing code.
The Payment Setup section currently tells an OpenClaw user to have a funded USDC wallet on Base or Solana. Would you accept an optional read-only funding companion for the narrower case where the agent has spendable funds on another supported chain or asset, but lacks USDC on the Base or Solana payment wallet selected for an Otto call?
Proposed boundary:
- Run only when the user already knows the source chain, asset, target payment rail, and intended amount.
- Send AssetFare only that route tuple and amount. Do not send wallet addresses, balances, private keys, signatures, x402 payment headers, or Otto request data.
- Return an unranked quote candidate with expected and minimum receive, itemized fees, ETA, expiry, and server_signing=false / server_submission=false.
- Never select a route, prepare an action, start a session, sign, submit, or automatically top up a wallet.
- If the wallet is empty everywhere, or the user already has enough USDC on an accepted Otto rail, omit the companion entirely.
- Keep the existing Otto x402 flow unchanged; this would only be a planning step before it.
If that boundary fits, would you prefer a short optional funding note in Payment Setup or a separate companion skill that stops after the quote?
Public contract and exact custody boundary: https://assetfare.dev/agents/
No AssetFare quote POST, wallet authentication, preparation, signing, submission, or transaction was performed while preparing this scope question.
If you have one concrete route and amount to evaluate, the structured read-only pilot form is: https://github.com/assetfare/assetfare-mcp/issues/new?template=assetfare-pilot.yml. It requests no wallet or secret data.
Maintainer disclosure: I maintain AssetFare. I am asking about scope before writing code.
The Payment Setup section currently tells an OpenClaw user to have a funded USDC wallet on Base or Solana. Would you accept an optional read-only funding companion for the narrower case where the agent has spendable funds on another supported chain or asset, but lacks USDC on the Base or Solana payment wallet selected for an Otto call?
Proposed boundary:
If that boundary fits, would you prefer a short optional funding note in Payment Setup or a separate companion skill that stops after the quote?
Public contract and exact custody boundary: https://assetfare.dev/agents/
No AssetFare quote POST, wallet authentication, preparation, signing, submission, or transaction was performed while preparing this scope question.
If you have one concrete route and amount to evaluate, the structured read-only pilot form is: https://github.com/assetfare/assetfare-mcp/issues/new?template=assetfare-pilot.yml. It requests no wallet or secret data.