3 ms·
Huh? You have to use your api key and pay for the service. Requests you make to the service providers are made on your own buck, you are supposed to track user
by TZubiri 3y ago
Huh? You have to use your api key and pay for the service.
Requests you make to the service providers are made on your own buck, you are supposed to track user stuff on your end. It would make no difference chatgpt wise who the user is, that's not part of the abstraction provided.
Not a user auth SaaS, an LLM SaaS.
- michaelt 3y agoPresumably oezi wants to do that complicated three-party OAuth stuff. Like when you use an online PDF editor with Google Drive integration - paying for the storage etc is between Google and the user, the files belong to the user's Google Drive account, but the PDF editor gets read/write access to them.
- oezi 3y agoYes, exactly. Many existing APIs are hard/impossible to connect to unless you are the user.
- cjonas 3y agoI think the disconnect is that he's talking about building plugins/"gpts" inside of chat GPT while others are thinking about using the API to build something from scratch?
- kristjansson 3y agoThat's my read. And he's totally right! Plugins/GPTs aren't a good platform or product, partly for some of the technical reasons he mentioned, but really because they're basically a tech demo for the real product (the tool API).
- oezi 3y agoMany interesting API usages must be bound to the user and must be payed based on usage so must be tied to the user. OpenAI doesn't provide ways to monetize GPTs so it is hard to justify spending on behalf of the user.