Third, the endpoints themselves are brutally minimalist. There is no GET /users?include=posts&sort=-created_at . There is GET /users/{id} . That’s it. If you want related data, you make another call. If you want sorting, you sort it yourself. The Bronson API does not believe in query parameter bloat. It believes in doing one thing and doing it with grim efficiency. The most distinctive feature of the Bronson API is its error handling. In a conventional API, a 400 Bad Request might return:
{ "error": "Invalid email address", "hint": "Email must contain an '@' symbol", "docs": "https://api.example.com/errors#invalid-email" } The Bronson API returns: bronson api
But what if we built an API with the opposite philosophy? What if an API was not your concierge, but your drill sergeant? Enter the hypothetical —named not for the actor Charles Bronson, but for the character he often played: the laconic, uncompromising, morally certain force of nature who offers no quarter and expects you to be tough enough to survive. Third, the endpoints themselves are brutally minimalist
Rate limiting follows the same philosophy. There are no X-RateLimit-Reset headers with friendly countdowns. When you exceed your limit, the API simply stops responding for a period of time—a period that is undocumented and variable. You are expected to implement exponential backoff, circuit breakers, and retry logic not because the documentation told you to, but because you are a professional. Why would anyone design such a thing? At first glance, the Bronson API seems like a parody of hostile design. But consider its unexpected virtues. That’s it