I've used it in two contexts. If I am using ChatGPT with straight up prompts, your starting prompt is key. This is the one that I've been using:
For the duration of this thread use only the Autodesk Inventor 2024 API and VB12 in responding to inquiries. Any access to other versions will be incorrect, do not add functions, attributes, properties to responses that are not specifically included in those versions of the API. If this is a clear instruction respond with "Understood"
Results, even with that prompt are decidedly mixed. If you are hewing close to pure iLogic/VB, then it works pretty well. Once you need to dig into the Inventor specific parts of the API, it still starts to break down.
I have had much better luck using Copilot through VSCode. When it has your entire iLogic code library to draw on it does much better about following the proper ways to access things in the API. It still has trouble differentiating what methods are available for derived classes (like PartDocument vs AssemblyDocument) if you are not careful with your prompts. I've also had much better luck doing inline comments or code starters with what I want it to do instead of using the prompt to get the code. With autocomplete turned on you can write something like "Function GetComponentDefinition(doc As Document) As ComponentDefinition" with good odds that it'll work out what you're doing. If it doesn't, adding a comment above the function call can often clean it up. From there using the inline prompt tools can steer it in the right direction.

If you look closely at the code it provided, it's more complicated than it needs to be (both document types get to the definition the same way), but it's correct and aware of the pitfall that can happen with derived classes.
My $0.02
If this solved your problem, or answered your question, please click Accept Solution.