API keys
Create keys in the dashboard, set budgets, and connect apps without exposing service provider keys.
An AI API gateway without extra infrastructure
Keys, shared balance, routes, Web Chat, pricing, and documents live in one dashboard. You see the settings that matter: model, multiplier, status, and connection.
One shared balance
One shared balance shows the purchased token volume. Different models spend it through their own multipliers, and only successful requests are charged.
Web Chat without extra storage
Web Chat history stays in the user browser. The server stores billing metadata only.
Models connected to one working gateway
The dashboard catalog shows current models, context, output limits, and route availability before work starts.
Claude
Claude
For Claude Code, Anthropic Messages API, and long-context work.
claude-opus-4.8Code
Claude Code
For IDE agents, coding sessions, and Anthropic-compatible workflows.
claude-code-readyAPI
Messages API
For server requests, streaming, tool use, and long context in Anthropic format.
/v1/messagesChat
Web Chat
For local browser conversations with active catalog model selection and context control.
browser-localKeys
Key budgets
For limiting spend per API key without exposing service keys.
budget-controlSafe
Privacy
For transparent usage: prompt and response text are not stored on the server.
no-text-storageFrom signup to first request in a few steps
No long setup path: choose a shared balance, issue a key, then connect your app.
Choose a balance
Choose one shared token package for models in the active catalog.
Issue a key
Set a key budget, save the prefix, and connect it in your app or SDK.
Set the Base URL
Use ready guides for Claude Code, Anthropic SDK, Cursor, and server apps.
$ pluswstore models list --available
claude-opus-4.8 context 1M route healthy
claude-sonnet-4.6 context 1M route healthy
claude-haiku-4.5 context 200K route healthy
$ send request --key app
The dashboard feels like a control center, not a link list
Shared balance, keys, models, Web Chat, availability, and multipliers live in one interface.
API keys
Creation, reveal, budgets, statuses, and usage history.
Web Chat
Local history, model selection, and context control.
Availability
Readable route states without internal provider names.
Usage settled
A package shows the token volume purchased. Actual charges depend on the model, token type, and active route coefficient.
Clear pricing without extra math
A package shows the token volume purchased. Actual charges depend on the model, token type, and active route coefficient.
Examples, not the full catalog
The dashboard lets you choose another shared-balance volume. These cards show entry options so the price level is clear fast.
Claude Start
Entry shared-balance package for first requests and tests.
~$0.37 2M tokens- Claude Opus
- Claude Sonnet
- Claude Haiku
AI balanceCore
One shared balance for active catalog models, with different usage multipliers.
~$0.37 2M tokens- Claude Code
- Messages API
- Long context
Working volume
More Claude tokens for regular development and team usage.
from ~$4.99 35M tokens- Team usage
- More volume
- Same controls
Payment-provider commission is paid on top when the checkout provider displays it.
Honest privacy, without vague promises
A request is sent to the selected model to produce a response. PLUSWSTORE does not store prompt or response text. Billing keeps technical fields: model, token counts, cost, status, key, and timestamp.
- Prompt and response text are not stored
- Service keys are not exposed to apps
- Payment webhooks credit balances only after confirmation
- RU/EN UI and legal pages are available from the homepage
Short answers before starting
Inspired by fast FAQ flows: answer payment, setup, storage, and limit questions before users enter the dashboard.
01Is this a subscription?
No. You buy a token package and spend balance only on successful requests.
02Do I need to change SDKs?
Usually no. Change the Base URL and key; Claude/Anthropic-compatible apps keep the same workflow.
03Where is Web Chat stored?
Web Chat history stays in the user browser. The server stores billing metadata only.
04What about payment fees?
If the checkout provider displays a fee, it is paid on top. The selected package is credited to the balance.
05What if a route is temporarily unavailable?
Route availability is visible in the dashboard. Only successful requests are charged.
06Can users start small?
Yes. The homepage shows entry packages, while the dashboard offers other shared-balance volumes.
Run the first API request without building your own infrastructure
Open the dashboard, choose a package, and create an API key. The rest is already assembled in one product.