# Why I Bet on togo for AI-Native Apps

When I started building API-first apps that needed to talk to AI agents, I kept hitting the same wall: too much boilerplate before I could even test an idea. That's why I bet on togo. It gives me a clean, opinionated structure for spinning up endpoints, wiring up schemas, and exposing them to agents without fighting the framework. What used to take me a day of scaffolding now takes an hour, and I can hand a working API straight to an agent to start iterating.

The real win is how naturally togo fits an agent-driven workflow. Its conventions are predictable enough that an AI agent can read the project structure and extend it correctly on the first try, which means less time babysitting generated code and more time shipping. For anyone building API-first products in the age of AI agents, togo has become my default starting point.

## Details

- **published at**: 2026-07-15T08:20:15.008193+02:00
- **reading time**: 2

---

[View on site](https://fadymondy.com/en/blog/why-i-bet-on-togo-for-ai-native-apps)