◉CLAUDE LABJP
●WATERMARK — Since 11/16, text from Opus 4.6, Sonnet 4.5 and other models carries a watermark; non-default temperature and similar settings may drop it●CC 2.1.325 — Claude Code is still on 2.1.325 (11/13), with no newer release yet●SONNET 4.5 — Retires on the Claude API on 11/30, 13 days left. Sweep model IDs in code and saved settings in one pass●AUTOMATION — A user reports recurring AI jobs set up without run counts or a spending cap, burning through a weekly allowance●CONNECTOR — If connectors vanish only in new sessions, compare the /mcp list against an older session first●NEW — Cowork Feels Worse? Run the Same Request in Three Fresh Sessions●WATERMARK — Since 11/16, text from Opus 4.6, Sonnet 4.5 and other models carries a watermark; non-default temperature and similar settings may drop it●CC 2.1.325 — Claude Code is still on 2.1.325 (11/13), with no newer release yet●SONNET 4.5 — Retires on the Claude API on 11/30, 13 days left. Sweep model IDs in code and saved settings in one pass●AUTOMATION — A user reports recurring AI jobs set up without run counts or a spending cap, burning through a weekly allowance●CONNECTOR — If connectors vanish only in new sessions, compare the /mcp list against an older session first●NEW — Cowork Feels Worse? Run the Same Request in Three Fresh Sessions
Articles/API & SDK
⬡ API & SDK/2026-06-21Advanced

Reserving Priority Capacity for User Traffic with service_tier

If you pay for Priority Tier but your user-facing responses still slow down at peak, the culprit is often your own background jobs eating the priority pool. Here is how to read service_tier, prove the contention, and isolate background work.

Claude API147service_tierPriority Tiercost optimization12production111

✦ Premium Article

A while after I started paying for Priority Tier, I noticed something odd. During the late-afternoon hours when user questions spike, the same prompt against the same model would respond noticeably slower than usual. Nothing in my code had changed. Yet only at peak, I was waiting.

It took a detour to find the cause. In short, the automated jobs I run in the background were competing for the very same priority pool as my user-facing requests. I had not understood how the service_tier request parameter actually behaves, and that gap surfaced directly as latency. As an indie developer running the scheduled work for the four Dolice Labs sites and the question-answering traffic through a single API key, this kind of contention is very easy to create.

What actually slows down user responses at peak

Priority Tier is a commitment that reserves a per-minute throughput of input and output tokens. Within that reserved range, your requests are served preferentially even under load, and latency stays consistent. The catch is that the pool is not infinite — it is exactly as large as you committed to.

The default value of service_tier is auto. An auto request uses the priority pool if there is room, and falls back to the standard pool otherwise. That sounds smart, but here is the trap: your background jobs also try to consume the priority pool as auto unless you say otherwise.

In my case, the afternoon peak was exactly when "more user questions" and "the article-generation batch I had scheduled for the evening" overlapped. The background jobs filled the priority pool first, pushing the user-facing requests out into the standard pool. That is why they slowed down.

What service_tier decides — auto versus standard_only

Here are the values service_tier can take and what each one means.

ValueBehaviorGood fit for
auto (default)Use the priority pool if available, otherwise fall back to standardUser-facing synchronous requests where latency matters
standard_onlyNever use the priority pool; always serve from standardBackground and scheduled jobs that can tolerate some delay

The key is to read standard_only as "do not let this consume the priority pool" rather than "make this slow." When the standard pool has room, a standard_only request still comes back quickly. The goal is not to slow anything down — it is to keep your finite, committed priority capacity free for the traffic you actually want to protect.

For work that is fine to return asynchronously within 24 hours, the first choice is the Batch tier (roughly 50% cheaper) instead. I cover that in the Claude API Messages Batches async processing guide. This article is about the middle ground that cannot go to Batch: work you want to receive synchronously, but do not want to prioritize as highly as user traffic.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦Diagnose why only your user-facing Claude API responses slow down at peak by understanding how service_tier auto and standard_only behave
✦Log usage.service_tier on every call so you can verify after the fact whether each request was served by the priority pool or the standard pool
✦Pin nightly automated jobs to standard_only and keep the priority capacity you pay for reserved for user-facing traffic
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

⬡ API & SDK2026-05-24
Archiving Claude API Responses to Cloudflare R2: An Implementation Memo for Audit, Replay, and Incident Analysis
An implementation memo on persisting Claude API requests and responses into Cloudflare R2 so you can audit, replay, and triage production incidents — covering Workers waitUntil patterns, PII masking, and a D1 metadata index for fast lookups.
⬡ API & SDK2026-05-14
6 Traps I Hit Building In-App AI Chat with Claude API — A Record of Getting to Production
Six real design mistakes I encountered shipping Claude API in-app chat to production — covering context management, streaming error detection, guardrails, session persistence, model versioning, and cost monitoring. Includes working TypeScript code.
⬡ API & SDK2026-05-12
Combining Haiku 4.5, Streaming, and Prompt Caching to Cut Costs in a Personal App — An Implementation Record
A hands-on record of combining Claude Haiku 4.5, streaming, and prompt caching to improve both cost and response speed in a personal iOS/Android app — including the mistakes made along the way.