<p>Interesting observation from the guys at Y Combinator: if you ask an AI agent to do something with a database right now, it will most likely choose Supabase. Why? Good documentation, popularity among developers, convenient API.</p>
<p>But the main idea goes deeper - agents are becoming consumers. If you are building a product for developers, you need to think not only about people but also about what the agent will choose.</p>
<p>My personal observation: I don’t like MCP, the protocol seems crooked. Where there is an API, I prefer to ask the agent to read the documentation and write code for direct interaction. And this works everywhere - from reading email and calendar to deployment.</p>
<p>Recent example: I’m helping to organize an event, tickets through Eventbrite. At first, I struggled with their complex interface for recurring events. Then I asked the agent - is there an API? It turned out, there’s a great API. Now I’ve completely ditched the website - analytics, tickets, everything through the API.</p>
<p>Conclusion: if you are building a product, it might be time to think not about how to make a convenient website for users, but how to create a convenient interface for models.</p>
<p>▶️ Video: <a href="https://youtu.be/Q8wVMdwhlh4?si=xSsy5tanQ8xADTD3">https://youtu.be/Q8wVMdwhlh4?si=xSsy5tanQ8xADTD3</a></p>;
<p>#ai #development #yc #api</p>
<p><a href="https://t.me/+OvImEUmA7W5mYTRi">————————— Мысли Рвачева —————————</a></p>