Gateway · CLI · Dashboard
The hosted control plane for multi-model agent completions.
Not a single-vendor chat wrapper. A gateway you run workloads through—metered usage, a real dashboard, and a CLI that behaves like infrastructure.
Quick start
The site ships the CLI under /cli/*; install.sh is generated at build time with your public URL. See the full Install page for details.
curl -fsSL "http://localhost:3000/install.sh" | sh
Sign in on the web, create an API token, run the CLI, then use /connect inside the session for your gateway URL and token (OpenCode-style flow).
agentwhipIn the full-screen session, run /connect (wizard or /connect <url> <token>). For scripts: agentwhip login and agentwhip chat -m "Hello".
What is AgentWhip?
AgentWhip is a managed gateway and account layer for running LLM completions across providers you choose. You get consistent authentication, usage visibility, and subscription-backed entitlements—whether you are prototyping in the terminal or wiring a small service.
Built for how you ship
Everything here exists to reduce glue code: one place for tokens, quotas, and receipts.
One gateway, many models
Send completions through a single HTTP API and CLI surface. Swap models as your workload changes—without re-plumbing auth and quotas per vendor.
CLI that fits your flow
Install with a single command, authenticate with a dashboard token, and stream results in the terminal—built for automation and daily driver use.
Dashboard you actually open
Usage history, subscription status, and API tokens in one place. Know where you stand before you ship the next release or run the next job.
Sign in you already use
GitHub and Google OAuth—no new password to forget. Session-backed access to the dashboard; personal tokens for the CLI and CI.
Usage that matches the invoice
Metered completions tied to your plan window—so finance and engineering read the same numbers. No surprise line items from opaque token math.
Subscription-backed access
Hosted checkout, renewals, and policy pages in plain language. Cancel or upgrade from billing when your needs change.
Clarity by default
Provider credentials stay on the server. Your browser never sees API keys for upstream models—only your session and the tokens you explicitly create for tools and automation.
Ready when you are