Teapot Router / 418
418 — I'm a teapot.
On April Fools' Day 1998, RFC 2324 introduced the Hyper Text Coffee Pot Control Protocol. One of its rules outlived the joke: ask a teapot to brew coffee, and it must answer with status 418 — I'm a teapot.
Then tea got its own RFC
In 2014, RFC 7168 extended the protocol to teapots that brew tea. Which is to say: us. We carry model traffic for GPT and Claude Code — hot, precious, and definitely not coffee.
Why we named a gateway after it
418 is the internet's most honest status code: it refuses to pretend to be something it isn't. That is how we run routing too — enterprise-grade paths, failover and audit trails, and plain answers about what a relay can and cannot do. Also, our logo really is a flattened 418.
Try it yourself
This endpoint is production-grade and brews nothing:
curl -i https://teapotrouter.com/api/brewYou will get
HTTP/2 418
x-teapot: short-and-stout
{"error": {"message": "I'm a teapot", "type": "teapot_error", "code": 418}}