inert
Sign up

Cheaper Claude access.
One API.

Point your agent harness at one compatible endpoint. Up to 75% below list price.

Inert gateway mascot

From your agent to the right model in five steps.

Inert gives your existing harness one stable way to reach the model route the task needs.

  1. 01

    Pick your harness

    Claude CodeOpenCodeKilo Code

    Claude Code, OpenCode, Kilo Code, Pi, and Hermes work today.

  2. 02

    Connect Inert

    Point your Anthropic- or OpenAI-compatible endpoint at the Inert gateway.

  3. 03

    Choose a route

    FableOpus

    Match the route to the kind of work your agent is doing.

  4. 04

    Fund your account

    Add balance to your Inert wallet before requests begin routing.

  5. 05

    Ship with one key

    Keep one stable integration while the model route changes.

Switch one endpoint. Keep the workflow.

Inert sits between your agent and the model route you select, while preserving the Anthropic- or OpenAI-shaped request path your harness already speaks.

Your agent harness
CodexHermesPi
Inert Gateway
Your selected route
FableOpus

One compatible endpoint

Your harness speaks the API shape it already understands.

A route you choose

Select the model behavior that matches the work in front of you.

Your account stays in control

Keys, balance, and route choices remain visible in one place.

Your key. Our Claude accounts.

Completions come from our pool of Anthropic accounts, not from a subscription you have to buy, renew, and spread across a team. Your harness holds one key, the accounts stay ours to run, and every request draws from your balance instead of a per-seat bill.

Choose a route for the work.

Route by task instead of rebuilding your integration around every model choice.

RouteBest forHow it fitsPricing /MTokAccess
Opus 5Focused reasoningFor planning, architecture, and technical work that rewards careful thought.
You pay $1.75 in / $8.75 outList price $5 / $25-65%
Claude account route

More routes are in testing. Prices land here when they do.

We route it. We don't keep it.

We use Redis-compatible Valkey for expiring sessions and coordination state only. Prompt and completion content is never written to Valkey, Postgres, or application logs.

Read our privacy policy
Redis / ValkeyExpiring state only.

Sessions, rate limits, and request slots expire by design.

Request metadata
No IP addresses or user agents retained.
API keys
Secret shown once; only its digest and short identifier are stored.

Start with one key.

Create an account, add balance, and choose the route that fits the work.

Sign up