Blog
Field notes from the gateway.
Engineering decisions, model evaluations, and the occasional opinionated essay.
Why we built ByteSpike
Every team we know is gluing two or three model providers together with bash scripts. We got tired of it. So we built one gateway, one key, and one billing surface — and we made it Anthropic-compatible because that's the API we actually like writing.
6 minThe Anthropic-protocol bet
We picked the Anthropic Messages API as our default protocol. Here's why we think tool_use, cache_control, and thinking are the API surface most worth keeping pristine — and how we shim everything else without losing fidelity.
4 min