Live data from Hacker News

Function calling and other API updates

openai.com

71–80 of 174 posts

Re: Function calling and other API updates

#71

Earlier quoted context omitted.

- The API is extremely cheap - There are plenty of open source tools built on top if it (example list: https://github.com/heartly/awesome-writing-tools ) While I wish this work was open, they are both the best and cheapest option out there... by a mile.

This is exactly my problem. They are doing quite well, and closing the door behind them. Open AI isn't your friend and reserves the right to screw you down the line.

Oh, I 100% agree. I just haven't seen another model come close. I'd love to hear someone tell me why.

Re: Function calling and other API updates

#72

Earlier quoted context omitted.

I see this statement a lot and have no idea how people come to this conclusion. I have a beefy 16k$ workstation with 2 4090s and I could barely run the LLAMA 65B model at a very slow pace. Let us say we do have the model weights to GPT-4 and GPT3.5, me as the average consumer I don't know how this helps me in any way. I need to shell at least 25k (possibly much more for GPT-4) before I can run these models for even i…

An "average" person is not someone who knows how to call an API. Perhaps only on HN

"AI" as we know it is hardly 6 months old now, just wait a while and it'll be grandma accessible.

Re: Function calling and other API updates

#76
Interesting to see this plugin-adjacent functionality landing in the chat API.

It seems like there is no way to provide in context examples of calling functions, since they are now no longer just "assistant"-authored chat turns with text, but rather a distinct kind of output.

This can make it hard to demonstrate how to use functions effectively. I haven't played with this feature yet; maybe the model will somehow be able to leverage in context chat turn examples and use those to inform its function call outputs?

Re: Function calling and other API updates

#77

Interesting to see this plugin-adjacent functionality landing in the chat API. It seems like there is no way to provide in context examples of calling functions, since they are now no longer just "assistant"-authored chat turns with text, but rather a distinct kind of output. This can make it hard to demonstrate how to use functions effectively. I haven't played with this feature yet; maybe the model will somehow be…

https://platform.openai.com/docs/guides/gpt/function-calling

they also have a notebook with more examples:

https://github.com/openai/openai-cookbook/blob/main/examples...

Re: Function calling and other API updates

#78

OpenAI continues to impress. Function calls will make working with JSON much easier, a current pain point. Dropping the price of embeddings and increasing context length means searching through your own content should become faster and more accurate. > $0.0015 per 1K input tokens and $0.002 per 1K output tokens, which equates to roughly 700 pages per dollar. This is such an incredible steal, especially when you consi…

> This is such an incredible steal, especially when you consider that no open source option comes close to GPT3.5.

Orca comes close or is better.

Good explainer here: https://www.youtube.com/watch?v=Dt_UNg7Mchg

Re: Function calling and other API updates

#79
post #77

Interesting to see this plugin-adjacent functionality landing in the chat API. It seems like there is no way to provide in context examples of calling functions, since they are now no longer just "assistant"-authored chat turns with text, but rather a distinct kind of output. This can make it hard to demonstrate how to use functions effectively. I haven't played with this feature yet; maybe the model will somehow be…

https://platform.openai.com/docs/guides/gpt/function-calling they also have a notebook with more examples: https://github.com/openai/openai-cookbook/blob/main/examples...

I have read both of these but I did not notice any in-context examples, meaning prompts fed to the model showing it how to call a function and response to a user query, rather than docstrings telling it how to call a function.

Re: Function calling and other API updates

#80

This seems like a direct result of Plugins not hitting PMF -- rather than give API developers access to Plugins, give them the underpinnings to build Plugin-like experiences. Love it!

I've forgotten what pmf means from the last time someone used it and someone else explained it.

(Can we please all lighten up on the acronyms a touch?)

Post reply on HN