Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.spotzee.com/llms.txt

Use this file to discover all available pages before exploring further.

Every request can carry an x-spotzee-client-type header that tells Spotzee what kind of client made the call. The header is optional, opaque, and used for two things:
  1. Rate-limit tuning — mcp clients get double the base read and write budget so parallel tool calls don’t run out of headroom mid-task.
  2. Telemetry — Spotzee uses the value to break down traffic by client type internally, which informs SDK roadmaps and capacity planning.
x-spotzee-client-type: mcp

​
Recognised values

Send one of these. Anything else is ignored at the rate-limit layer and bucketed as unknown in telemetry.
ValueUse for
mcpMCP servers and agent runtimes that fan out parallel tool calls
mobileNative iOS or Android apps using the official mobile SDKs
sdk-jsThe official JavaScript SDK — set automatically; you don’t need to set it yourself
sdk-androidThe official Android SDK — set automatically
sdk-iosThe official iOS SDK — set automatically
cliCommand-line tools (deploy scripts, one-off backfills, your own CLI)
unknownDefault when omitted — no rate-limit boost

​
When to set it

Always set x-spotzee-client-type: mcp. The rate-limit boost is the only way an agent driving many parallel calls keeps up with its own fan-out. See Rate limits for the exact multipliers.

​
Verifying it’s applied

Check the response headers. The applied rate-limit tier is echoed in X-RateLimit-Tier, and the resulting limit is in X-RateLimit-Limit: 
HTTP/1.1 200 OK
X-RateLimit-Limit: 8000
X-RateLimit-Remaining: 7999
X-RateLimit-Reset: 10
X-RateLimit-Tier: starter
An MCP client on the Starter plan should see X-RateLimit-Limit higher than the unboosted Starter ceiling — that’s how you confirm the header took effect.

​
Reference