AnyResponses bets on /responses as default API shape

This is less a launch than a thesis on where LLM infrastructure is heading: the real battleground is shifting from model APIs to higher-level contracts app teams can actually build against.

• –The pitch is credible because it targets the ugliest problem in production AI stacks: every provider still exposes slightly different request, tool, and event shapes.
• –AnyResponses is effectively betting that portability matters more than vendor purity, using model-prefix routing and an Open Responses-compatible surface to reduce adapter churn.
• –The project looks early but serious, with a dedicated site, hosted gateway, multi-provider support, and published acceptance-test claims around text, streaming, tool calls, and multimodal input.
• –If `/responses`-style contracts spread, gateways and OSS compatibility layers like this could become the default abstraction developers code to, even if providers never fully converge underneath.