agent-ready
crisp framing for the shift from browsing-as-parsing toward MCP/tool-native web experiences; useful when thinking about how product surfaces should evolve for agent traffic.
What it is: an X post arguing that “agent-ready” websites need typed tools rather than just scrapable HTML.
Gist: the core claim is that real agent usability comes from explicit actions like search, checkout, and inventory exposed as structured tools, not merely from making pages easy to scrape.
Newsletter angle: “agent-ready ≠ scrapable” is a strong hook for the coming split between human web UX and agent-facing capability layers.
Note: extracted via FXTwitter API; linked demo/domain mentioned is webmcp.cool.