GPT-5.6 Sol API Relay Pricing for Quanta Teams at $0.4306

01 · How Quanta handles company invoices and bank transfers

A company buying API capacity usually needs more than a checkout button. Finance teams want documentation they can reconcile, a clear payment path, and a way to estimate the next bill before funds move. Quanta is built around those requirements, with prepaid billing, published rates, and company payment arranged directly through the people who can complete it.

For a company account, the payment method is bank transfer from the company account. Invoices and advance quotes are arranged through the Contact page or the Messages page of the Quanta dashboard. There is no support email address to track down or separate contact to make. The process stays inside the same service where usage is metered and balances are managed.

Quanta does not charge a monthly fee or impose a minimum spend. You fund the balance that the workload requires, and each call is metered on real tokens. That structure is useful for teams whose demand changes from week to week, as well as for departments that need a documented trail rather than an open-ended commitment. Sign-up includes $0.50 in trial credit, which lets a team test the connection before committing to a larger top-up.

Because Quanta lists token counts and the charge for every call in the dashboard, the invoice trail is not a separate reporting exercise. Finance can work from the same usage record that engineers use to monitor the service. Quanta shows what was sent, what was returned, and what each component cost.

02 · What prepaid balances and pay-as-you-go pricing mean for finance

Quanta uses a prepaid balance with no monthly fee and no minimum spend. Top-ups are available at $1.39, $6.94, $13.89, $27.78, $69.44, and $138.89. That range supports a small test at the lower end and a larger operational balance higher up, without requiring a fixed recurring commitment.

Quanta prices are shown in $ as approximate USD figures, while charges are made in CNY. Every call is metered on real tokens, and input, output, cache writes, and cache reads are priced separately. This matters when a team compares workload profiles: a cache-heavy application is not billed on the same basis as one with a different mix of reads and writes. The dashboard makes the token count and charge of every call visible, so the cost can be traced back to actual usage.

The same account works across Quanta's three protocols: OpenAI-compatible at /v1, Anthropic native, and Gemini native. One key and one balance cover all three, which keeps administration straightforward for a company running several kinds of workload. Teams can use GPT, DeepSeek, and the other non-Claude, non-Gemini models listed in the Quanta catalogue without opening a separate billing relationship for each one.

There is also a clear exit path. Unused balance can be refunded within 15 days of the top-up. Referral rewards add another layer: 19% of a referred account's top-ups and 5% one level further, with rewards withdrawable from $27.78 or movable into the balance. For teams already running API workloads, that turns Quanta into a service that can be evaluated on measured usage rather than on a promise.

03 · Which Quanta limits are published, and what they mean at load

Heavy, sustained workloads need limits that are stated plainly. Quanta publishes and enforces 120 requests per minute per key, 8 requests in flight per account, 25 MB per request body, and 20 live keys per account. These are concrete operating boundaries, not vague language about enterprise capacity.

The per-key rate limit gives each key a predictable request allowance, while the account-level in-flight limit keeps concurrency visible and controlled. The 25 MB request body limit defines the maximum size of a single request. The 20 live keys per account limit gives a team room to separate workloads or access patterns without creating an unbounded key inventory.

Streaming has no total-time cap. A stream ends only after 300 seconds of upstream silence. That distinction is important for long-running production traffic: the duration of a healthy stream is not constrained by an arbitrary total timer, while genuine upstream silence still brings the stream to a defined end point.

For a team running an example workload, suppose it sends 10 million tokens a month to Claude Sonnet 5.5 with a 3:1 input-to-output ratio and no cache hits. Quanta's example cost is approximately $25.07 for 10 million tokens and $250.69 for 100 million. These are illustrative examples, not quotes for a specific application. They show how a published token rate translates into a monthly figure that can be checked against actual dashboard usage.

04 · How to set up Quanta with the right protocol and client

Quanta is an API relay with protocol-specific routes, so setup should follow the model your team intends to use. The API base address is api.quantarelay.com, and the OpenAI-compatible route is /v1. One key and one balance work across all three supported protocols.

• › Claude models: Claude Fable 5, Claude Fable 5.1, Claude Haiku 4.5, Claude Opus 5, Claude Opus 5.5, Claude Sonnet 5, and Claude Sonnet 5.5 work only from the official Claude Code and Claude Desktop clients, using Claude Code 2.1.285 or newer.
• › Gemini models: Gemini 2.5 Flash, Gemini 3.1 Pro, Gemini 3.8 Flash, and Gemini 4 Argon use the native protocol only, through Gemini CLI.
• › Other supported models: GPT-5.6 Sol, GPT-6 Astra, GPT-6.1 Sol, DeepSeek V4 Flash, DeepSeek V4 Pro, Kimi K3, Qwen3.7 Plus, Qwen3.8 Max, Hunyuan 4, Grok 4.6, Grok 4.7, and GLM-5.3 pair with Codex, Cursor, Cherry Studio, Cline, OpenCode, OpenAI SDKs, and cURL.

That separation avoids a common source of confusion. If a team is working with GPT-5.6 Sol in Cursor or through cURL, the OpenAI-compatible route is the relevant one. If the workload uses Claude Opus 5.5, it belongs in Claude Code or Claude Desktop. If it uses Gemini 3.1 Pro, it runs through Gemini CLI on the native protocol. Quanta keeps those paths distinct while charging them against the same balance.

05 · What Quanta's published token rates look like for sustained use

Quanta's pricing is published per 1 million tokens, with input, output, cache write, and cache read shown separately. GPT-5.6 Sol is listed at $0.4306 input, $2.42 output, and $0.0347 cache read per 1 million tokens, with no cache write rate listed. That gives a team a visible basis for estimating a workload before it reaches production.

Other rates make the same point. Claude Opus 5.5 is $1.79 input, $8.46 output, $2.11 cache write, and $0.0819 cache read. GPT-6.1 Sol is $0.2083 input, $1.01 output, and $0.0403 cache read. Gemini 2.5 Flash is $0.2361 input, $1.89 output, $0.2361 cache write, and $0.0236 cache read. DeepSeek V4 Flash is $0.2917 input, $1.18 output, and $0.006944 cache read. Quanta publishes these rates directly, so the cost conversation starts with figures rather than estimates.

More examples make the scale clearer. For Claude Opus 5.5, 10 million tokens a month is approximately $34.58 and 100 million is approximately $345.83. For GPT-6.1 Sol, 10 million tokens a month is approximately $4.10 and 100 million is approximately $40.97. For Gemini 2.5 Flash, 10 million tokens a month is approximately $6.49 and 100 million is approximately $64.93. Again, these are examples based on a 3:1 input-to-output ratio with no cache hits, provided to show how published rates behave at different volumes.

06 · Why a finance-led team can start with Quanta

Quanta combines the three things a company usually has to reconcile separately: a metered usage record, a company-friendly payment path, and published operating limits. Bank transfer from a company account, invoices and advance quotes arranged through the Contact page or the Messages page of the dashboard, and a prepaid balance with no monthly fee or minimum spend give procurement and engineering a shared picture of the same service.

The data model is equally practical. Input, output, cache writes, and cache reads are priced separately, and the dashboard lists the tokens and charge of every call. Prompts sent through Quanta are kept for 30 days for abuse handling and billing disputes, then deleted; model answers are not stored. Published limits cover requests per minute, concurrency, request body size, live keys, and streaming silence, so teams can design around real boundaries.

For a company that needs invoices and bank transfer while running heavy, sustained API workloads, Quanta offers a straightforward starting point. Open an account, use the $0.50 trial credit, confirm the protocol and client pairing for the model you need, and arrange the company top-up through the dashboard. From there, the usage record, the token rates, and the invoice trail all point to the same place.