I played with building out a graphql mesh [0] of a few different APIs as I was curious to see if I could build one schema (and subsets of it) and have GPT interface over that. Turns out, it did a pretty good job if you can provide it the right portions of the schema it needs.

It also helped out when I was struggling to reconcile with how large of JSON payloads I was getting. The REST endpoints are just killing the prompt size, but having the model choose the fields it needed from GraphQL really helped out there.

Put it down for a while until I can get access to the plugin fine-tuned version of chatgpt and see if there's still a need or if it is additive still.

[0] https://github.com/Urigo/graphql-mesh/

Yeah we just need to keep something trained for the latest APIs

Or at least latest popular x versions of APIs just in case

Won't structure also be correlated with domain model?

With literally just about any diagramming tool - Vizio, dia, xfig, PowerPoint, etc. Frankly those are not particularly consistent or careful - they’re not that good. The text positioning and alignment is inconsistent and careless, bleeding into the boxes in places, the arrows don’t even meet the boxes in a consistent way. I’m not trying to shit on it (I’ve done my fair share of mediocre diagrams) - but it’s not professional level or particularly careful work (it’s a jpeg to boot) and looks done by hand (without even bothering to use alignment affordances.)

It looks like https://www.diagrams.net/

Given that GPT is a trademark of OpenAI, I'd be careful about naming any product or service with "GPT" in the name, even if it depends on it.