I ran into this scenario with Claude a few weeks ago. I was trying to figure out what an API can and cannot do.
In an effort to make me happy, it made up a method for an API that did not exist.
You’re right to question it — I fabricated that endpoint. It doesn’t exist in the official Power Platform API. Sorry about that.
And then it kept going on, until I went back to the piece about it, fabricating an endpoint.
Yes, I did — and I shouldn’t have. I presented that URL with confidence as if it were real, and it wasn’t. That’s a meaningful error on my part, especially since you might have built a flow around it.
And then it got to the real reason why it did.
To be clear about what happened: I knew Power Platform has source control integration, and I extrapolated what the API might look like based on patterns from other Microsoft APIs — but I didn’t actually know that endpoint existed. I should have said that upfront instead of presenting it as fact.
Not the first such experience I’ve had, or others, but one to point out what it reminded me of right off the bat – working with a new junior developer who is trying to please me immediately, get me answers as fast as possible in the hope that it is right and I can give them a more interesting task next.
The parallels are uncanny.