Gateway for AI Agents

Gateway is the best swaps engine for native BTC. It supports a growing set of assets and chains — run gateway-cli routes --json to see what is available.

The Gateway CLI makes that engine available to any AI agent that can run a shell command. No SDK to bind, no language to match, no service to host. A Python agent, a TypeScript agent, a shell script, or a scheduled job can all call the same interface and get structured output back.

What your agents can do

Who this is for

Why the CLI is a good agent tool

Agents call tools and read structured output. The Gateway CLI is built around that interface. None of this is an AI feature — it is good CLI design, which turns out to be most of what an agent needs.

gateway-cli quote --src BTC --dst USDC:base --amount 100USD --json

The agent loop

An agentic swap follows a consistent pattern: discover what is possible, get a quote, decide, then settle.

npm install -g @gobob/gateway-cli
gateway-cli --help

gateway-cli routes --json

gateway-cli quote \
  --src BTC \
  --dst USDC:base \
  --amount 100USD \
  --json

gateway-cli swap \
  --src BTC \
  --dst USDC:base \
  --amount 100USD \
  --unsigned \
  --json

# Returns an order ID immediately
gateway-cli swap \
  --src BTC \
  --dst USDC:base \
  --amount 100USD \
  --no-wait \
  --json

gateway-cli status <order-id> --json

gateway-cli orders <address> --json

Expose Gateway to a model

Wrapping the CLI in a tool takes a few lines. Here is a minimal Python example:

import subprocess, json

def gateway_swap(src: str, dst: str, amount: str) -> dict:
    """Swap native BTC and EVM tokens via BOB Gateway. Returns an unsigned tx for your signer to approve."""
    out = subprocess.run(
        ["gateway-cli", "swap", "--src", src, "--dst", dst,
         "--amount", amount, "--unsigned", "--json"],
        capture_output=True, text=True, check=True,
    )
    return json.loads(out.stdout)

Give the model that function plus matching quote and status tools and the loop runs itself. The agent quotes, reasons about the result, requests an unsigned swap, your signer approves, and the agent tracks settlement to completion. "Swap $100 of BTC to USDC on Base" becomes a sequence of tool calls with a signature you control in the middle.

Example: the Gateway starter bot

The gateway-starter-bot is a minimal, educational example of a trading bot built entirely on the Gateway CLI. It's a single bash script that demonstrates the full agent loop in a real strategy.

The bot executes a "buy the dip" round-trip:

1. BTC to X — swap BTC → USDT on Ethereum.
2. Watch — poll the reverse quote (USDT → BTC) until BTC gets cheaper.
3. Buy the dip — swap USDT → BTC, ending with more sats than it started with.

The interesting part: there is no external price feed. The gateway quote is the price signal. The bot sold a known number of satoshis; it buys back the moment the gateway would return more sats than were sold (by a configurable threshold). Fees and slippage are already priced into the quote — one tool, one source of truth.

The entire strategy is gateway-cli ... --json piped through jq. Read dip-bot.sh top to bottom — that's the whole thing.

# Safe to run — quotes only, no real swaps
./dip-bot.sh --dry-run

Example dry-run output:

! DRY RUN — no real swaps will be executed. Quotes only.
▸ Trade size 100USD | dip threshold 500bps | poll 60s | max wait 3600s
▸ Onramp: 100USD of BTC -> USDT on Ethereum
✓ Sold 0.00094000 BTC (94000 sats), now holding USDT
▸ Will buy back when a quote returns >= 0.00098700 BTC (98700 sats)
▸ No dip yet: quote 0.00094100 BTC < target 0.00098700 BTC. Waiting 60s…
✓ Dip detected: quote returns 0.00098750 BTC (>= target)
▸ Summary:
  sold:   0.00094000 BTC (94000 sats)
  bought: 0.00098750 BTC (98750 sats)
  net:    +0.00004750 BTC (4750 sats)

BOB Gateway integration paths

The CLI is the fastest path into BOB Gateway, not the only one. The same engine is available through multiple surfaces:

Gateway has already powered experiments like a Bitcoin yield bot built on Coinbase AgentKit. Frameworks evolve fast — the engine underneath does not. Whether an agent reaches Gateway through a CLI, an MCP server, or next year's framework, it is calling the same swaps engine for native BTC. Build the Bitcoin layer once and let the toolchains find it.

Try it

Set your keys and run a quote to verify the setup:

export BITCOIN_PRIVATE_KEY=...
export EVM_PRIVATE_KEY=...

# Or stay in unsigned mode — no keys required for quoting
gateway-cli quote --src BTC --dst USDC:base --amount 100USD --json