AnvilHub

The workspace

Models & providers

Anvil talks to 35 providers with your own keys. Connect as many as you like, switch models mid-session, and let it route or fail over automatically.

Anvil doesn't run models for you and doesn't resell anyone's API. It speaks to 35 providers — Anthropic, OpenAI, Google, xAI, AWS Bedrock, Azure, local Ollama and LM Studio, and more — using your credentials, from your machine. Nothing is proxied through a Culpur server, and a key you add is sent to the provider, never to us.

Connecting a provider

Add one in the terminal:

anvil login

Pick a provider and either paste an API key or use an OAuth sign-in where the provider supports it (Anthropic and xAI, for example, open a browser popup and light up the moment you're signed in). Local servers like Ollama and LM Studio are detected automatically; Bedrock and Azure take their usual endpoint and region details.

You can connect as many as you like, and you need at least one — Anvil can't run without a model.

[!NOTE] A key you enter is stored machine-bound and encrypted in your vault, and it's never shown back to you after you enter it. Anvil holds it to call the provider; it doesn't display or export it.

Switching models, live

The model you're on is the active model for the session, and you can change it on the fly:

/model                 # list what's available and pick
/model claude-opus-5-5 # switch provider + model mid-session

Switching with /model swaps the provider, the routing, and the identity together — you're never left half-changed between two providers mid-turn.

Routing and failover

Beyond a single active model, Anvil can decide per task which model to use, and recover when one is unavailable:

  • Routing rules send different kinds of work to different models — a cheap local model for quick edits, a frontier model for hard reasoning.
  • Failover moves to a backup when a provider errors or rate-limits, so a session keeps going instead of stalling.
  • Effort dials how much reasoning a model spends on a task.

These live under the routing.rules and related settings — editable in the terminal with /config and /route, or on AnvilHub in the Configuration settings pane.

Doing it on AnvilHub

Everything above has a graphical home. The Providers settings pane shows a card per provider — sign in with OAuth, paste a key (sent once, never shown again), detect a local server, add a search engine. The Configuration pane holds the default model, effort, and routing rules. See Doing it in AnvilHub.

Where to next