Tresor now supports prompt caching across multiple providers and models, including GLM 5.2 and Kimi K2.6. If your workflow sends the same large context over and over, you no longer have to pay full price every time.

That matters a lot for agentic coding. Coding agents tend to resend the same repository map, instructions, diffs, and tool state on every turn. With caching on supported routes, that repeated context becomes much cheaper, which makes confidential coding workflows far more competitive on price.

Big context, smaller bills

• Reuse repeated context - Large prompts, repo summaries, and long instructions can be treated as cached input instead of billed like brand-new input every turn.

• Run longer coding loops - Refactor, test, fix, and retry cycles become much easier to justify when the shared context is cheaper to carry forward.

• Keep model choice open - You can get the pricing benefit on more than one route, instead of tying your workflow to a single model or provider.

Better economics for private agents

Private workflows usually need more context, not less. Prompt caching helps you keep that context inside Tresor's sealed environment without turning every follow-up into a full-price request.

Privacy: Cached context keeps the same zero-access, sealed-environment path as the rest of the Tresor API.

If you're building coding agents, background automations, or long multi-step analysis flows, this is one of the most practical API upgrades yet.