Subscriptions and keys

Two ways to reach a model. Both stay on your machine, and every agent picks its own.

By subscription

You already pay for one of these. Sign in once, and it is the vendor’s own agent that runs underneath BytNode-AI, on your account, with its usual limits and no extra token.

VendorPlan
ClaudeClaude Pro or Max
OpenAIChatGPT Plus, Pro or Business
GeminiA Google account
GitHub CopilotCopilot Pro, Pro+ or Business
GrokSuperGrok or X Premium
MistralA Mistral AI Studio account

Se connecter opens the vendor’s sign-in page in your browser (for Claude and Copilot, a terminal window too); the state refreshes by itself. An agent that is not on your machine shows Installer instead: one click installs it under ~/.bytnode-ai/agents/. One already installed globally is detected.

What “dressed by BytNode-AI” means

The vendor’s agent runs as a subprocess, one session per conversation, and BytNode-AI hands it everything an agent needs: BytNode as an MCP server, the profession’s skills in its working folder, the BytNode-AI prompt, and the exchange and finance tools through a local MCP server. Its tools are its own; its permission requests get our buttons.

By key

An OpenRouter key (it starts with sk-or-, from openrouter.ai/keys) gives every vendor in the OpenRouter catalogue, billed per use. The agent then runs BytNode-AI’s own loop, with all the tools described in this documentation. The key is verified when you paste it, stored in your browser, and sent only with your own requests.

The same model is served by several providers with very different latencies, so requests ask OpenRouter to sort by latency. Four environment variables adjust this, on the server side:

VariableDefaultEffect
OPENROUTER_PROVIDER_SORTlatencylatency, throughput or price.
OPENROUTER_IGNORE_PROVIDERSparasailProviders to avoid; empty means none.
OPENROUTER_PROVIDER_ORDERAn explicit order; overrides the sort.
OPENROUTER_ALLOW_FALLBACKS10 forbids any other provider, at the risk of a failed request.

Both at once

The two coexist. Each agent chooses its access when you create it, and you can have a Claude agent next to an OpenRouter one. The BytNode key is the same in both cases.