Tan invokes Venkatesh Rao’s framing — “you need to be above the API line; if Uber came out, like if you’re an Uber driver, you’re below the API line, you should be fighting to be above the API line” — and then rejects its permanence: “I actually think AI erases the API line.” His example is a YC-funded API company that “released a bug report endpoint that is not for humans to use, it’s for agents who use their software to use,” backed by an LLM that answers in the moment: “that’s a good bug, we filed it, we’re going to fix it next week, but also like try this workaround.” What he cannot stop thinking about is the shape it implies for companies generally: “instead of being below the API line and having to do what the API tells you to do, this can be a back and forth.”
He grounds the principle in manufacturing rather than software. Japanese cars overtook American ones in the 1980s because of the Toyota production system, which held that “if you are the person doing the work on the line, you should be allowed to change the line, because you are the person with the most amount of cont[ext] to be able to improve your own working situation” (the captions render it “contacts”) — a bottom-up method from a hierarchical culture that bought, in the interviewer’s words, “arguably a 40-year generational run because of process power.”
The design consequence is that an agent-facing surface should be built to argue, not merely to accept. This extends The gains come from redesigning work around AI, not bolting AI onto human workflows past internal workflow into the interface between companies, and it gives a concrete mechanism to Humans should supervise agent loops from a leveraged point, not sit inside every one: the leverage comes from the endpoint carrying enough context to resolve a case itself instead of escalating it. Anyone designing for ai-native-product-architecture should ask whether their API’s error paths assume a human will read them.
(Attribution note: the transcript came from auto-generated captions and the company’s name could not be reliably resolved, so it is deliberately not asserted here.)