◉CLAUDE LABJP
●MODEL — Claude Fable 5.1 and Claude Mythos 5.1 landed on September 1. They are the same underlying model; only the strength of the safeguards differs●PRICING — Per-token rates hold at $10/$50 per MTok. What changed is cache reads, cut 75% to $0.25 per MTok●COST — How much that saves depends on your workload: roughly 25% for typical use, up to about 45% for context-heavy agentic work. Worth measuring your own split before quoting a number●BENCH — Terminal-Bench-Science 0.1 climbs from 24.7% on Fable 5 to 52.6%. Anthropic also states a standard error of 3.5-4.5 points, which is worth remembering before reading small gaps as real●SAFEGUARDS — Sharper cyber safeguards cut interventions in Claude Code sessions by roughly 60% on average. Finding vulnerabilities is now allowed; developing exploits still is not●API — New API accounts created from today can no longer edit prior context while preserving Claude's thinking transcript. It is an anti-distillation measure, and existing accounts are unaffected for now●MODEL — Claude Fable 5.1 and Claude Mythos 5.1 landed on September 1. They are the same underlying model; only the strength of the safeguards differs●PRICING — Per-token rates hold at $10/$50 per MTok. What changed is cache reads, cut 75% to $0.25 per MTok●COST — How much that saves depends on your workload: roughly 25% for typical use, up to about 45% for context-heavy agentic work. Worth measuring your own split before quoting a number●BENCH — Terminal-Bench-Science 0.1 climbs from 24.7% on Fable 5 to 52.6%. Anthropic also states a standard error of 3.5-4.5 points, which is worth remembering before reading small gaps as real●SAFEGUARDS — Sharper cyber safeguards cut interventions in Claude Code sessions by roughly 60% on average. Finding vulnerabilities is now allowed; developing exploits still is not●API — New API accounts created from today can no longer edit prior context while preserving Claude's thinking transcript. It is an anti-distillation measure, and existing accounts are unaffected for now
TAG

JSON

4 articles
← Back to all tags
Related:
troubleshooting2structured-output2Claude API1streaming1tool use1claude-api1prefill1production1claude-code1cicd1github-actions1automation1
⬡ API & SDK/2026-05-28Intermediate

Why JSON.parse Fails on Claude API Streaming tool_use Arguments — and How to Fix It

When you stream a Claude API response with tool_use, calling JSON.parse on each input_json_delta throws SyntaxError. Here is the correct way to assemble partial_json fragments, plus disconnect handling.

⬡ API & SDK/2026-05-10Advanced

Bulletproof JSON Output with Claude API Prefill: A Four-Layer Defense Pattern from Indie SaaS

How I went from late-night JSON parse failures to a 99.98% parse success rate across thousands of monthly Claude API requests, and what a 1,081-sample truncation benchmark revealed about the repair code I had originally published here.

⟐ Claude Code/2026-04-25Intermediate

Automating CI/CD Pipelines with Claude Code's --print and --output-format json

A practical guide to using Claude Code's --print flag and --output-format json in CI/CD pipelines. Covers automated code review in GitHub Actions, PR comment generation, and test failure analysis — with working code throughout.

⬡ API & SDK/2026-04-16Intermediate

Claude API JSON Output Fails: 5 Root Causes and Fixes

Fix Claude API JSON parsing errors with these 5 common root causes: markdown code block wrapping, truncated output, injected commentary, Unicode escaping, and streaming parse failures. Includes copy-paste ready Python utility code.