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 differsPRICING — Per-token rates hold at $10/$50 per MTok. What changed is cache reads, cut 75% to $0.25 per MTokCOST — 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 numberBENCH — 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 realSAFEGUARDS — Sharper cyber safeguards cut interventions in Claude Code sessions by roughly 60% on average. Finding vulnerabilities is now allowed; developing exploits still is notAPI — 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 nowMODEL — 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 differsPRICING — Per-token rates hold at $10/$50 per MTok. What changed is cache reads, cut 75% to $0.25 per MTokCOST — 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 numberBENCH — 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 realSAFEGUARDS — Sharper cyber safeguards cut interventions in Claude Code sessions by roughly 60% on average. Finding vulnerabilities is now allowed; developing exploits still is notAPI — 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

async processing

3 articles
Back to all tags
Related:
Claude API2Cloudflare Queues1Dead-Letter Queue1Production1Message Batches1Cost Optimization1Large-Scale Requests1Messages Batches API1batch processing1cost optimization1production1API1
API & SDK/2026-05-31Advanced

Isolating Poison Messages in a Claude Async Pipeline: A Dead-Letter Queue Implementation Note

How one broken input can stall an entire batch — and how to isolate these 'poison messages' with a Cloudflare Queues dead-letter queue. Covers classifying Claude API failures and safe redrive, all from production experience.

API & SDK/2026-04-11Intermediate

Running Claude's Message Batches Overnight — What the 50% Discount Actually Covers

What I learned running Claude API Message Batches for real: what the 50% discount covers, the custom_id character restriction, and designing around the 24-hour window and 29-day retention.

API & SDK/2026-04-02Advanced

Claude API Messages Batches: Cutting Production Costs by Up to 50% with Async Processing

Field notes from running the Claude API Messages Batches API in production. Polling design, composite custom_id keys, the 29-day result expiry trap, and the real cost numbers from three months of nightly batches.