Does APIYI Support Cache Billing?

​

Short Answer

Yes. APIYI’s Claude, OpenAI, Gemini, DeepSeek, Qwen, and Grok channels all support cache billing: cache-related request parameters are forwarded upstream as-is, cache-hit fields come back to you untouched, and the billing dashboard lists cached usage as separate line items at the official discount rates — no middleware-specific adaptation needed in your code. Claude and OpenAI cache hits are stable and reliable (both have dedicated guides on this site — linked below). DeepSeek, Qwen, and Grok work well too. Gemini’s implicit caching is supported, but its hit rate is mediocre — don’t build your cost budget around Gemini caching.

​

The Three Channels at a Glance

​

Channel Notes

​

OpenAI: fully automatic, zero effort

Keep a stable prefix of at least 1024 tokens and hits happen automatically — the matched portion bills at 10% of the input price, with no write fee, so the 2nd request is already pure savings. How to write requests that hit and how to use prompt_cache_key: see the OpenAI Prompt Caching Billing Guide.

​

Claude: manual markers, biggest savings

Add cache_control to the content blocks you want cached; hits bill at 0.1× (writes cost 1.25× / 2×). Essential for Claude Code, Cline, Cursor, and other heavy workloads. Note it only works in the Anthropic native format (/v1/messages) — calling Claude through the OpenAI-compatible format gets no cache discount. See the Claude Prompt Caching Billing Guide.

​

Gemini: supported, but keep expectations low

APIYI auto-enables implicit context caching for the Gemini native format, and hits bill at Google’s official discount. In practice, however, Gemini’s cache hit rate is clearly below Claude / OpenAI (upstream implicit caching behavior is not controllable). Our advice:

• Treat the cache discount as a nice-to-have bonus — estimate costs at the uncached price
• For cache-sensitive workloads with long, frequent prefixes, prefer the OpenAI or Claude channels

​

Other Channels: DeepSeek / Qwen / Grok

Caching on these channels is fully automatic (no markers needed), works normally through APIYI, and performs well in practice: Raising hit rates works the same way as with OpenAI: stable content first, volatile content last — keep timestamps and random IDs out of the start of the prompt. The “stable prefix” playbook in the OpenAI Cache Billing Guide applies directly.

​

How to Confirm a Hit

Check the cache fields in the response usage: A value above 0 means a hit. In the dashboard call logs, cached usage appears as separate discounted line items you can verify directly.

​

Things to Watch

• Caches are isolated per model: switching models (even within the same series) shares nothing
• For vendors not listed above (Kimi, etc.), go by the cache fields actually returned in your call logs
• Official mechanism details: platform.openai.com/docs/guides/prompt-caching, docs.claude.com/en/docs/build-with-claude/prompt-caching, ai.google.dev/gemini-api/docs/caching, api-docs.deepseek.com/quick_start/pricing, docs.x.ai/developers/advanced-api-usage/prompt-caching

​

Related Docs

​

Contact Us