Unknown providerLLMactive

Claude Haiku 3.5 API Pricing

2 available providers and 1 live price sources tracked, including 1 official provider.

Data snapshot:

Official input / 1M$0.80
Lowest input / 1M$0.0414
Maximum input gap94.8%Not a service-quality measure
Comparable providers21 live

Claude Haiku 3.5 provider prices and multipliers

Input and output multipliers are each calculated as provider price ÷ official baseline; 1.00× equals the official price.

Providers: 2From, within billing group: $0.0414Lowest observed: $0.0414Lowest input multiplier: 0.0517×
Official input baseline$0.80Official output baseline$4.00Price multipliers do not measure stability, rate limits, refunds, or service quality.
Claude Haiku 3.5 provider price and evidence comparison
Provider / operatorInput / 1M tokensOutput / 1M tokensvs officialPrice evidencePublic operating historyAPI docsRefund policyPayment / invoice
Anthropicunknown$0.80$4.00
In 1.00×Out 1.00×
Official price sourcePlatform pageObserved: UnknownView docsNot providedvisa · mastercardunknown
PoloAPIunknown$0.0414$0.0414
In 0.0517×Out 0.0103×
Live API pricePlatform pageObserved: UnknownView docsNot providedalipay · wechatunknown

Platform-submitted information or domain verification does not mean the price was independently checked and is not a ComputeUnion guarantee of pricing, availability, refunds, compliance, invoices, or service quality.

External capability references

Only source results safely mapped to the official model name are shown.

No safely matched external result is available; adjacent model scores are not substituted.

FAQ

How is Claude Haiku 3.5 API priced?

Input and output tokens are billed separately. The current recorded official baseline is $0.8000 input / $4.0000 output per 1M tokens.

Which provider is cheapest for Claude Haiku 3.5?

The lowest recorded input price is $0.0414/1M tokens from PoloAPI; verify provider terms and the observation date before production use.

How do official and relay prices differ?

Official and relay channels can differ in price, latency, limits, and service terms; evaluate them separately for production traffic.