Anthropic shipped Claude Sonnet 5 on June 30 at $2/$10 per million tokens, closing most of the capability gap to Opus 4.8 at a third of the price — while Fable 5 spent 19 days pulled from the market under US export controls before returning July 1 with a stricter cybersecurity classifier. What actually changed, what the benchmark table hides, and which tier real workloads should run on now.
Api
-
Claude Sonnet 5 and Fable 5: The New Generation, Priced and Positioned -
Claude Fable 5 vs Opus: A Realistic Look at Whether You Need the Mythos-Class Model Anthropic just released Claude Fable 5, the first public Mythos-class model, at double the price of Opus 4.8. A realistic breakdown of where the capability gap actually shows up, where it does not, the safety-routing wrinkle, and a decision framework for when to pay for Fable versus staying on Opus or Sonnet.
-
Buf: The Modern Protobuf Toolchain Replace protoc with Buf for schema linting, breaking change detection, remote code generation, and a registry for your Protobuf APIs.
-
API Rate Limiting Patterns: Algorithms, Redis Implementations, and Client Communication A deep dive into rate limiting algorithms — token bucket, sliding window log, sliding window counter, fixed window, and leaky bucket — with production Redis implementations, distributed rate limiting, and how to communicate limits to clients.
-
OWASP API Security Top 10: A Practical Guide to Securing Your APIs A deep-dive into the OWASP API Security Top 10—covering broken object-level authorization, excessive data exposure, mass assignment, and every other critical API vulnerability with real attack examples and defensive code patterns.
-
OpenAPI and Swagger: Designing and Documenting APIs Contract-First Learn how to design and document APIs contract-first using the OpenAPI Specification — covering document structure, schemas, security, code generation, and the full tooling ecosystem from Swagger UI to Prism mock servers.
-
REST API Design Principles A well-designed API is intuitive to use and hard to misuse. The principles that hold up under real traffic: resource modeling, the idempotency contract behind HTTP methods, status codes that tell the truth, a real error format (RFC 9457), offset vs cursor pagination honestly, versioning strategies and why most are wrong, idempotency keys, and treating the spec as the contract.