Claude models, accounts, and 9Router

Claude is Anthropic’s model family; Claude Code is a coding client. In a 9Router setup, the client, requested model, and provider connection are separate choices. A client called Claude Code can be configured to send requests through a gateway, but that alone does not prove that Anthropic’s Claude answered.

If you want the terminal configuration, go to Claude Code setup. This page helps you decide which Claude access path to use and how to verify it.

Identify the account that pays for the request

A Claude consumer subscription, an Anthropic API account, and credits at another model provider are different billing relationships. Do not assume that paying for one funds the others. Check the provider’s current account permissions and supported gateway use before connecting it.

In 9Router, add a provider connection using the method supported by your installed version. For an API connection, use a key issued by that provider. Keep that upstream credential in the router. The key used by a client to call 9Router is a different credential and should not be confused with the provider key.

Layer	Example role	Where to inspect
Client	Claude Code sends a task	Client settings and session
Router	Maps the requested name to a route	9Router model or combo configuration
Provider	Authenticates and runs inference	Provider dashboard, request logs, billing

Select a model your connection can actually serve

Read the models exposed by your running router rather than copying a model name from an old screenshot. Providers may use different identifiers for the same model family. A model name in a generic catalog is not proof that your account has access.

Begin with one explicit model. Check a short text response, then test the capabilities your workflow needs: streaming, tools, image input, or longer context. A plain chat response establishes much less than a successful coding session that reads a file, proposes an edit, and returns a valid tool result.

Do not publish a private repository or use a large agent task as the first connectivity test. A small, disposable fixture makes errors easier to understand and keeps repeated requests inexpensive.

What changes when you add fallback?

A fallback can switch the provider or model used after a qualifying failure. If your requirement is specifically Claude, keep the fallback choices within the models you intend to use. A combo that falls back to another family can keep a request running while changing its behavior.

Record the configured route and inspect the router’s logs after a request. Check the provider’s usage record when attribution matters. The model’s prose saying “I am Claude” is not reliable identity evidence. Neither is a client window titled Claude Code.

Read fallback configuration for a controlled check. Repeat a small tool task after enabling a backup; similar text output does not guarantee equivalent tool calling.

Why are cached tokens missing from the dashboard?

Missing cache statistics do not by themselves prove a cache miss. In upstream issue #5114, a user reports absent cached-token counts on a Claude Code route through Kiro. That report is evidence of a reporting question, not proof that every such request is uncached or incorrectly billed.

Compare the usage fields returned by the provider with what the router displays. If a field is absent upstream, a dashboard cannot reliably reconstruct it. If the provider returns it and the router drops it, capture a redacted reproduction with the affected versions. Avoid calculating savings from a blank field.

Is Claude free through 9Router?

9Router’s software being free does not make Claude inference universally free. Access, limits, and charges depend on the account and provider serving the request. Free allowances can expire or exclude models. Review that provider’s terms and usage page, and set a budget there when available.

For a hosted access option, read OpenRouter with 9Router. For the actual terminal setup, continue to the Claude Code guide.