Having built a relatively standard, not particularly complex Stripe integration with 3DSecure, there is no way I'd trust code written by an AI for it. Hell, I set up code review sessions just to walk through the code and discuss. Transactionality, idempotency, what happens if a customer drops out of the flow at the 3DSecure prompt, how do you re-engage them, what happens if they want to continue, etc. It's hard both in terms of having a detailed understanding of the technology components, and in terms of understanding the UX requirements, customer support requirements, etc.

Taking a payment with Stripe is a 5 minute job. Taking thousands of payments a day, without ever double charging someone, and without ever losing an order, while optimising the UX and allowing a customer support team to provide good service, that's a huge task. (Also no criticism of Stripe, having looked at Braintree circa 2019 I expect it would be significantly harder with them).

One change I expect to see over the next few years in API documentation is a series of complicated examples. This isn't for people to review, but for coding assistants to use as to inform RAG or something similar.