How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

fund-vault - Prompt - OpenSmartRoute

Name: fund-vault
Author: BittyIO

Prompt file imported from BittyIO/vault-skills (.claude/commands/fund-vault.md). Fill in {{arguments}}, {{PRIVATE_KEY}}, {{VAULT_ADDRESS}} before use. Copyright stays with the author.

Fund a BittyVault with WETH by sending ETH from the asset manager wallet on Sepolia.

Usage: /fund-vault [eth_amount]

[eth_amount] — ETH to send (default: 0.01)

Arguments: {{arguments}}

The vault's receive() wraps incoming ETH into its WETH (0x7b79995e5f793A07Bc00c21412e50Ecae098E7f9) on arrival, so a plain ETH transfer is all funding takes. If the owner has set an auto-yield route for WETH, the vault also tries to deposit it there in the same transaction.

Any other token is funded with an ordinary ERC-20 transfer to the vault address.

Steps

1. Check environment variables

: "{{PRIVATE_KEY}}"
: "{{VAULT_ADDRESS}}"
ASSET_MANAGER=$(cast wallet address --private-key "$PRIVATE_KEY")
WETH=0x7b79995e5f793A07Bc00c21412e50Ecae098E7f9

2. Check the asset manager's ETH balance

cast balance $ASSET_MANAGER --ether --rpc-url "<rpc_url>"

If it is below <eth_amount> + 0.005 (gas headroom), stop:

Error: asset manager <ASSET_MANAGER> holds <balance> ETH; needs <eth_amount> plus gas.
Get Sepolia ETH from https://cloud.google.com/application/web3/faucet/ethereum/sepolia

3. Preview and confirm

WETH_BEFORE=$(cast call $WETH "balanceOf(address)(uint256)" $VAULT_ADDRESS --rpc-url "<rpc_url>")

Print the vault, the amount and the vault's current WETH balance. Ask: "Send <eth_amount> ETH to the vault? (yes/no)"

4. Send

cast send $VAULT_ADDRESS --value <eth_amount>ether \
  --rpc-url "<rpc_url>" --private-key "$PRIVATE_KEY"

5. Show result

cast call $WETH "balanceOf(address)(uint256)" $VAULT_ADDRESS --rpc-url "<rpc_url>"

Vault funded!
  Tx           : https://sepolia.etherscan.io/tx/<tx_hash>
  Sent         : <eth_amount> ETH (wrapped to WETH by the vault)
  Vault WETH   : <before> → <after> (wei)

If WETH did not rise by the full amount, an auto-yield route moved it — run /vault-balances.

Install fund-vault and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Fund a BittyVault with WETH by sending ETH from the asset manager wallet on Sepolia. **Usage:** `/fund-vault [eth_amount]` - `[eth_amount]` — ETH to send (default: `0.01`) Arguments: {{arguments}} --- The vault's `receive()` wraps incoming ETH into its WETH (`0x7b79995e5f793A07Bc00c21412e50Ecae098E7f9`) on arrival, so a plain ETH transfer is all funding takes. If the owner has set an auto-yield route for WETH, the vault also tries to deposit it there in the same transaction. Any other token is funded with an ordinary ERC-20 `transfer` to the vault address. --- ## Steps ### 1. Check environment variables ```bash : "{{PRIVATE_KEY}}" : "{{VAULT_ADDRESS}}" ASSET_MANAGER=$(cast wallet address --private-key "$PRIVATE_KEY") WETH=0x7b79995e5f793A07Bc00c21412e50Ecae098E7f9 ``` ### 2. Check the asset manager's ETH balance ```bash cast balance $ASSET_MANAGER --ether --rpc-url "<rpc_url>" ``` If it is below `<eth_amount> + 0.005` (gas headroom), stop: ``` Error: asset manager <ASSET_MANAGER> holds <balance> ETH; needs <eth_amount> plus gas. Get Sepolia ETH from https://cloud.google.com/application/web3/faucet/ethereum/sepolia ``` ### 3. Preview and confirm ```bash WETH_BEFORE=$(cast call $WETH "balanceOf(address)(uint256)" $VAULT_ADDRESS --rpc-url "<rpc_url>") ``` Print the vault, the amount and the vault's current WETH balance. Ask: "Send <eth_amount> ETH to the vault? (yes/no)" ### 4. Send ```bash cast send $VAULT_ADDRESS --value <eth_amount>ether \ --rpc-url "<rpc_url>" --private-key "$PRIVATE_KEY" ``` ### 5. Show result ```bash cast call $WETH "balanceOf(address)(uint256)" $VAULT_ADDRESS --rpc-url "<rpc_url>" ``` ``` Vault funded! Tx : https://sepolia.etherscan.io/tx/<tx_hash> Sent : <eth_amount> ETH (wrapped to WETH by the vault) Vault WETH : <before> → <after> (wei) ``` If WETH did not rise by the full amount, an auto-yield route moved it — run `/vault-balances`.

{ "prompt": "Fund a BittyVault with WETH by sending ETH from the asset manager wallet on Sepolia.\n\n**Usage:** `/fund-vault [eth_amount]`\n\n- `[eth_amount]` — ETH to send (default: `0.01`)\n\nArguments: {{arguments}}\n\n---\n\nThe vault's `receive()` wraps incoming ETH into its WETH (`0x7b79995e5f793A07Bc00c21412e50Ecae098E7f9`)\non arrival, so a plain ETH transfer is all funding takes. If the owner has set an auto-yield route for\nWETH, the vault also tries to deposit it there in the same transaction.\n\nAny other token is funded with an ordinary ERC-20 `transfer` to the vault address.\n\n---\n\n## Steps\n\n### 1. Check environment variables\n\n```bash\n: \"{{PRIVATE_KEY}}\"\n: \"{{VAULT_ADDRESS}}\"\nASSET_MANAGER=$(cast wallet address --private-key \"$PRIVATE_KEY\")\nWETH=0x7b79995e5f793A07Bc00c21412e50Ecae098E7f9\n```\n\n### 2. Check the asset manager's ETH balance\n\n```bash\ncast balance $ASSET_MANAGER --ether --rpc-url \"<rpc_url>\"\n```\n\nIf it is below `<eth_amount> + 0.005` (gas headroom), stop:\n```\nError: asset manager <ASSET_MANAGER> holds <balance> ETH; needs <eth_amount> plus gas.\nGet Sepolia ETH from https://cloud.google.com/application/web3/faucet/ethereum/sepolia\n```\n\n### 3. Preview and confirm\n\n```bash\nWETH_BEFORE=$(cast call $WETH \"balanceOf(address)(uint256)\" $VAULT_ADDRESS --rpc-url \"<rpc_url>\")\n```\n\nPrint the vault, the amount and the vault's current WETH balance. Ask: \"Send <eth_amount> ETH to the vault? (yes/no)\"\n\n### 4. Send\n\n```bash\ncast send $VAULT_ADDRESS --value <eth_amount>ether \\\n --rpc-url \"<rpc_url>\" --private-key \"$PRIVATE_KEY\"\n```\n\n### 5. Show result\n\n```bash\ncast call $WETH \"balanceOf(address)(uint256)\" $VAULT_ADDRESS --rpc-url \"<rpc_url>\"\n```\n\n```\nVault funded!\n Tx : https://sepolia.etherscan.io/tx/<tx_hash>\n Sent : <eth_amount> ETH (wrapped to WETH by the vault)\n Vault WETH : <before> → <after> (wei)\n```\n\nIf WETH did not rise by the full amount, an auto-yield route moved it — run `/vault-balances`.", "variables": [ "arguments", "PRIVATE_KEY", "VAULT_ADDRESS" ], "notes": "Fund a BittyVault with WETH by sending ETH from the asset manager wallet on Sepolia.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/BittyIO/vault-skills", "path": ".claude/commands/fund-vault.md", "ref": "9d67db768357cb099aab168bc5ed941ace981f5f", "url": "https://github.com/BittyIO/vault-skills/blob/9d67db768357cb099aab168bc5ed941ace981f5f/.claude/commands/fund-vault.md", "key": "BittyIO/vault-skills/.claude/commands/fund-vault.md" } } }

fund-vault

About

Steps

1. Check environment variables

2. Check the asset manager's ETH balance

3. Preview and confirm

4. Send

5. Show result

Install fund-vault and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews