Zashmodel · Claude Opus 5.5Authenticity, speed and price analysis

⇆ Compare Visit website

Modelclaude-steadyData security level 030 samples

Authenticity2 / 5

Fingerprint Claude Opus 5.5 · 5 answers

40Probe agreement
(%)

Speed#3 / 10

First token 2.38 s · Output speed Not provided

2.38First token
(seconds)

Price#5 / 6

Input $0.32 · Output $1.6 · Cache discount 95%

¥4.77Cost per
coding session

Availability#10 / 10

7 days 96.1% · 30 days 96.1%

60.0%Last 24 hours
availability

Comparison summary

Claude Opus 5.5 on Zashmodel: availability over the last 24 hours is 60.0%, ranking 10 of 10 relays with data (median 88.9%); time to first token is 2.38 s, ranking 3 of 10 (median 12.04 s); a coding session costs ¥4.77, ranking 5 of 6 (median ¥4.40).

Authenticity

Model consistency

Output distribution for the same requests on this relay and on the official API · higher is better

Probe agreement40%

Answers2 / 5

Model fingerprintClaude Opus 5.5

ClientAPI (Anthropic Messages)

Share of identity-probe answers that match the same model on the reference route. It only shows how routes differ from one another. Measured 2026-11-10 21:11 UTC. See all routes

ⓘ Method: see the blog post “Did the model really get dumber?” Read

Speed

Measured by time to first token (seconds) and output speed (tokens / second)

Time to first token

Seconds until the first token · lower is better

10 relays

ⓘ Output speed: not yet available from the live API; shown once connected

Price

Cost per coding session

Claude Opus 5.5 · 2M input and 40k output tokens (¥) · split by token type · lower is better

6 relays

OutputInput

ⓘ USD prices are converted at 1 USD = 6.7698 CNY

Prices: cache hit, input and output

¥ / 1M tokens

Cache hitInputOutput

Cache

Coding requests repeat much of their context, so the cache hit rate largely decides what you actually pay. Drag the hit rate and the costs and ranking below are reweighted with cache prices.

Cache discount

95%

Cache hit $0.016 · input $0.32 (per 1M tokens)

Measured hit rate

Pending

Measured by replaying multi-turn sessions: cached-read tokens in usage as a share of all input

Session cost at 80% hit rate

¥1.47

¥4.77 without cache, 69% saved

Cache-weighted session cost

Claude Opus 5.5 · of 2M input tokens, the hit share is billed at the cache price and the rest at the input price, plus 40k output (¥) · lower is better

Rank 4 / 6

Cache hit rate80%Coding agents typically see 70%–90%

Cached inputUncached inputOutput

ⓘ Routes without a cache price are billed at the input price; cache write fees are not included

Stability

Availability

Request success rate, last 24 hours · higher is better

10 relays

Status of each model, last 24 hours

One cell per hour · green ok, yellow delayed, red failed

Model	Group	Availability	First token	Samples
GPT 6.1 Sol	gpt-steady	100.0%	4.62 s	30
GPT 6 Astra	gpt-steady	93.3%	8.16 s	30
Claude Opus 5.5	claude-steady	60.0%	2.38 s	30

Service details

Minimum top-upNot provided

Sign-up bonusNot provided

Support responseNot provided

Payment methodsNot provided

China invoiceNot provided

International invoiceNot provided

RefundsNot provided

PromotionsNot provided

FAQ

How much does Claude Opus 5.5 cost on Zashmodel?

Input $0.32 and output $1.6 per 1M tokens; at 2M input and 40k output tokens, a coding session costs about ¥4.77, an API rate of 0.080.

How does the cache hit rate affect price?

On Zashmodel, the cache-hit price is 5% of the input price. At an 80% hit rate a coding session costs about ¥1.47, versus about ¥4.77 without cache.Measured hit rates will replace this assumption once available.

Which models does Zashmodel support?

Folkbench currently lists 3: GPT 6 Astra, GPT 6.1 Sol, Claude Opus 5.5.

What does the data security level mean?

Folkbench rates relays from 0 to 4 based on public policies and verifiable evidence; Zashmodel is currently level 0. The check covers leaks in responses and error messages only, and does not prove data retention or training policies.

How often is this data updated?

Availability and time to first token use a 24-hour window, and this page syncs live data every 15 minutes.