The problem is larger than the monthly bill
Using several AI products usually means several browser tabs, billing pages, histories, interfaces, and sets of controls. A task that begins in one product may need a different model later. Moving it then becomes a small migration: copy the useful context, reattach files, explain the task again, and learn which controls the next interface exposes. API work adds provider accounts, keys, balances, model names, and incompatible request formats. Coding agents add another configuration layer. None of these steps is individually difficult, but together they turn model choice into account administration. Capriole AI brings the common parts into one workspace. You can chat with a supported model, change models inside the conversation, work with files or web search, and keep the thread in the same interface. The product handles the protocol and context differences behind that switch.What one USD 8 membership replaces
Capriole maintains current supported models from OpenAI, Anthropic, Google, xAI, Z.AI, and Moonshot AI inside the same workspace, including the flagship set named above.
The browser and API have different usage models. Premium browser chat has no per-message token balance for the user to manage. API requests are metered because programmatic workloads can grow far beyond normal chat use.
The plan suits someone who chats every day and also needs occasional or moderate API or coding-agent access. The two allowances stay clear: browser chat is unlimited under Premium, while automated work uses the visible charged-token balance.
One conversation, different model strengths
Different model families are useful for different parts of the same task. A thread may start with research, move into careful writing, and end with code or structured analysis. Separate products make the user carry the context between them. Capriole lets the conversation stay in one workspace while the selected model changes. The visible action is a model choice. Underneath it, message formats, context limits, reasoning controls, files, tools, streaming events, token accounting, and errors may all need different handling. Capriole maintains that adaptation as part of the product, so changing the selected model does not make the user rebuild the thread or integration. Capriole also provides latest-model aliases for supported API and agent workflows. They allow a configuration to follow Capriole’s recommended current model for a provider family without requiring the user to update every exact model identifier immediately.The same account can leave the browser
Eligible paid access unlocks Capriole’s public API as well as browser chat. The API quickstart covers the first request, while maintained guides support six coding agents: Codex, Claude Code, Kilo Code, GitHub Copilot CLI, OpenCode, and OpenClaw. This does not make every coding agent identical. Each client still has its own capabilities and expectations. The benefit is that supported clients can use one Capriole account and compatible API paths instead of requiring a separate model-provider setup for each family.Choose where chat history lives
Not every conversation deserves the same storage policy.
Local history survives a refresh until that browser’s site data is cleared. No Storage history is lost when the page refreshes or the user leaves, and enabling it first asks for confirmation before deleting existing server and local chat history.
All three modes still send each request through Capriole and the selected model service. They control chat-history persistence; they do not promise zero operational records or replace the selected provider’s data policy. Read the chat storage guide before using sensitive or regulated data.