Earlier quoted context omitted.
The website is the API though. HTML is one of the few RESTful systems people still use today, build semantics into the page and humans and LLMs can understand how to use it. A11y specs and APIs are just a way of presenting those semantics differently, often for those who can't see the page, whether visually impaired or in this case an LLM. At least in my view, we should expect anything claimed to be artificial intell…
I think you are confusing two things. - the semantics of a form and a button and the resulting http POST/GET - and what the page actually does! So I can have two pages - both with html forms - what they actually do on submission might be completely different - one buys a potted plant the other submits a tax return. ie the meaning of the action is in the non-semantic elements - the free text, the images, the context.…
I would hope those two buttons and forms include labels, description text, indicators for required fields, etc. All of that should live in the HTML and includes attributes as needed for a11y. LLMs can use that, they don't need yet another API to describe it.