glibsonoran

Just FYI, The "v1" endpoint would be associated with using the OpenAI API object and the corresponding menu item for a local app like Ollama would be: `Local app (URL)`....

Re: other misc parameters. I thought about that last night and added a *Parameter_name* field the user can enter along with the *User_json*. So I'm just going to leave it...

I'm thinking I'd like to add a simple node that takes a 'JSON' (really it's a python dict in this case) and can parse out all the key value pairs...

Regarding handling any parameter: Yes, I could add a button to have the user indicate if the parameter value is a JSON, then just pass plain text if it was...

Hmm, I don't see where you specify the data type, so it must be determining that by examining the value. Like if it starts with a "{" it's a json?...

That's a pretty good method, so he provides the output in all available formats that are valid for the input value. What is this typically handling output from? I haven't...

Regarding using chat.completions.parse() vs chat.completions.create() for Structured outputs: I wouldn't be surprised if they have code that parses your JSON and then constructs a prompt to describe it to the...

Hmm, I have a node that extracts Exif & XMP from jpeg's (and maybe .raw's) and ComfyUI meta data from .png's: *Exif_Wrangler*. But it doesn't produce output in JSON format...

So I've got my prototypes up now with the JSON parsing node. I think I have to change the name of that first field in additional parameters to Parameter Type,...

And here it handles a list of dictionaries: