x-spotzee-client-type header tells Spotzee what kind of client made a request. The header is optional, opaque, and reserved for two things.
- Rate-limit policy. Once the per-key sliding-window rate limits ship (see Rate limits), MCP and agent traffic gets a doubled budget so parallel tool calls don’t run out of headroom mid-task.
- Telemetry. Spotzee uses the value to break traffic down by client type internally, which informs SDK roadmaps and capacity planning.
x-spotzee-client-type is accepted on every request today (no error if absent or unknown), but the rate-limit policy that would honour it is rolling out behind a feature flag. Including the header now is forward-compatible. Once enforcement ships, the documented values take effect automatically.Recognised values
Send one of these. Anything else is bucketed asunknown.
When to set it
- MCP server
- CLI tool
- Custom integration (your own backend)
- Official SDK
Always set
x-spotzee-client-type: mcp. Once the per-key rate limits ship, this is the only way an agent driving many parallel calls keeps up with its own fan-out.Reference
- Rate-limit policy and the MCP boost: see Rate limits
- Authentication: see Authentication