Compaction in the Claude API: let Claude summarise as long agents run
Server-side compaction at a token threshold or on demand: parameters, the compaction block, counting usage.iterations, prompt caching and risks.
Building with the Claude API: prompt caching, batches, tool use, errors, cost control. · 16 articles
Server-side compaction at a token threshold or on demand: parameters, the compaction block, counting usage.iterations, prompt caching and risks.
Attaching skills in the Messages API: code execution tool, container.skills, pre-built pptx/xlsx/docx/pdf skills, /v1/skills uploads, output files.
Enabling streaming, SDK helpers, the SSE event order, delta types (text, tool JSON, thinking) and handling overloaded errors mid-stream.
Enabling citations for text, PDF and custom documents: citation formats, token costs, versus prompt-based citations, and the structured outputs limitation.
Server-side web search: tool versions, dynamic filtering, max_uses, domain filters, $10 per 1,000 searches, errors and injection risk.
Three Claude API beta features: load tools on demand, let code call tools and filter data, teach usage by example. How to enable and when.
clear_tool_uses and clear_thinking strategies, trigger/keep/clear_at_least parameters, prompt caching interaction and the memory tool.
Automatic vs explicit breakpoints, write/read pricing, 5-minute and 1-hour TTLs, what invalidates the cache and why caches never hit.
Manual extended thinking is rejected from Claude 4.7 on. How to migrate to adaptive thinking, pick an effort level and avoid cost traps.
Which errors to retry, how RPM/ITPM/OTPM work, why cache reads don't count toward ITPM, and the spend-cap 429 trap.
Groups often advertise Claude keys/endpoints at 50–80% off. Before plugging one into a project, understand the data, model-quality and terms risks.
Classify 10,000 tickets, summarize a document archive, run evals… submit once as a batch, collect later, pay half.
Same models, two completely different billing models. Pick wrong and you either overpay or hit limits right when you need them.
Keys leaked on GitHub or in client-side JavaScript get scraped and abused within minutes. A short checklist to avoid being the victim.
“Only return JSON” prompts still leak prose sometimes. Define a schema as a tool and force the call — clean, parseable data.
The same agent loop, tools, permissions and hooks as Claude Code — called from your code, with custom tools written in Python.
Try another keyword or clear the topic filter.
Follow binhAI via RSS (Feedly, Inoreader, Slack…) to get new articles as soon as they’re published.