| It’s a great forcing function for: * Simplicity of input knobs - way too many APIs are unapproachable with the number and complexity of inputs * Complete documentation - if you don’t document a parameter or endpoint, expect an AI agent is never going to use it (or at least use it the way you want it to) especially in multi-agentic systems where your tool needs to be chosen by the LLM * Clear, descriptive API outputs so that an agentic system knows if and how to include in its final output * No overloading of endpoint functionality - one endpoint, one purpose * Handle errors and retries gracefully These are not rocket science guidelines but API design had shifted to be too user “unfriendly” and lacked empathy for users. It’s ironic that user empathy needs to increase again now with agent users :) P.S. this topic is near and dear to me heart since I just designed and implemented an agent friendly API at Tako. Check out the docs here - docs.trytako.com and the API playground (trytako.com/playground) [requires login for free custom queries] we built to showcase how easy the API is to use. Feedback and discussion welcome! |
I mean — maybe in some glorious alternate timeline, but not ours, I guess?